Developer Advocate Champion - Needs Assessment Survey

Your Contact Details

Name *

Please enter your name

Email Address *

Please enter a valid email address

Position / Job Title

Organisation

Section A: Your Profile

1.What is your primary role? *

Senior Developer / Lead Engineer
DevOps Engineer / Platform Engineer
Application Security Champion / Security Engineer
Privacy Engineer / Data Protection Specialist
Site Reliability Engineer (SRE)
Engineering Manager
Other:

Please select your primary role

2.How many years of experience do you have in software development? *

Please select your experience level

3.What best describes your organisation's development methodology?

Agile (Scrum/Kanban)
DevOps / DevSecOps
Waterfall
Hybrid approach
Other:

4.What industry sector does your organisation operate in?

Section B: Current Workflow Challenges

5.Rate how frequently you experience each challenge:

1 = Never, 2 = Rarely, 3 = Sometimes, 4 = Often, 5 = Daily

Challenge	1	2	3	4	5
Security tools interrupt my development flow
I have to wait for AppSec team approval before proceeding
Security training is generic and not contextual to my work
Security issues are discovered late in the release cycle
Privacy requirements (GDPR/CCPA) create context-switching
Resilience concerns are addressed too late in the SDLC
Compliance requirements feel disconnected from engineering excellence

6.Which challenge has the greatest impact on your productivity?

Select one

Flow interruption from security tools
Dependency on AppSec team for approvals
Late-stage security issue discovery causing rework
Privacy compliance friction (GDPR/CCPA)
Deferred resilience considerations
Disconnect between compliance and engineering quality

7.On average, how many hours per week do you estimate you lose to security-related interruptions or rework?

Section C: Current Security Practices

8.Does your organisation currently perform threat modelling?

Yes, regularly (every sprint/release)
Yes, occasionally (major features only)
Rarely or inconsistently
No
Not sure

9.Who is primarily responsible for security decisions in your development workflow?

Individual developers
Dedicated AppSec team
Security champions within dev teams
External consultants
Shared responsibility (unclear ownership)

10.At what stage are security issues typically discovered in your SDLC?

During design/architecture phase
During development (code review)
During testing/QA
During security review (pre-release)
After deployment (production issues)

Section D: Privacy & Resilience Practices

11.How does your team currently handle privacy-by-design requirements (GDPR, CCPA)?

Integrated into development workflow with clear patterns
Addressed during legal/compliance review before release
Ad-hoc basis when privacy issues are identified
Primarily handled by a separate privacy/legal team
Not systematically addressed

12.When are failure modes and resilience patterns typically considered?

During initial architecture/design
During development
During testing/QA
Post-incident (after production failures)
Not systematically considered

Section E: Desired Outcomes & Priorities

13.Rate the importance of each outcome to you personally:

1 = Not Important, 2 = Slightly Important, 3 = Moderately Important, 4 = Very Important, 5 = Critical

Desired Outcome	1	2	3	4	5
Security that fits naturally into my development workflow
Faster release cycles with fewer blockers
Autonomous security guidance without AppSec dependency
Privacy compliance embedded in development process
Early detection of issues (during design, not deployment)
Resilient systems built from the design phase
Recognition as an early adopter of better practices
Contributing to a security-mature engineering culture

14.If you could solve only ONE problem related to security/privacy/resilience in your workflow, what would it be?

Section F: Tool Evaluation Criteria

15.Rate how important each factor is when evaluating new SDLC tools:

1 = Not Important, 2 = Slightly Important, 3 = Moderately Important, 4 = Very Important, 5 = Essential

Evaluation Factor	1	2	3	4	5
Seamless integration with existing workflow/tools
Low friction setup and immediate value
Autonomous operation without external team dependency
Contextual guidance relevant to my actual work
Support for privacy-by-design patterns
Support for resilience/failure mode analysis
Ability to quantify time savings or efficiency gains
Peer testimonials and proven adoption

Section G: Advocacy & Influence

16.How often do you recommend tools or practices to your teammates?

Frequently (weekly or more)
Regularly (monthly)
Occasionally (a few times per year)
Rarely

17.What would motivate you to advocate for a new tool within your organisation?

Select all that apply

Personal productivity improvement
Quality improvement (fewer bugs/issues)
Time savings for the team
Recognition from peers or management
Alignment with engineering best practices
Contribution to team success
Other:

18.What is your preferred way to evaluate a new tool before recommending it?

Self-service trial in my own workflow
Guided demonstration with technical deep-dive
Peer recommendation from trusted colleague
Published case studies and testimonials
Proof of concept with team involvement

Section H: Solution Fit Assessment

19.Based on what you know about Trusted Path, rate your agreement with each statement:

1 = Strongly Disagree, 2 = Disagree, 3 = Neutral, 4 = Agree, 5 = Strongly Agree

Statement	1	2	3	4	5
This solution addresses my primary workflow challenges
Integrating security into design (not deployment) is valuable
Autonomous security guidance would improve my productivity
Embedded privacy patterns would reduce my compliance burden
Early resilience thinking would prevent production incidents
I would be willing to trial this solution in my next sprint
I would recommend this to teammates if it delivers value

20.What concerns, if any, would you have about adopting this type of solution?

21.Is there anything else you would like to share about your SDLC challenges or needs?