Developers and engineers survey

Your Contact Details

Name *

Please enter your name

Email Address *

Please enter a valid email address

Position / Job Title

Organisation

Section A: About You

1.Which of these is closest to your role? *

Senior Developer / Lead Engineer
DevOps Engineer / Platform Engineer
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 have you worked in software development? *

Please select your experience level

3.How does your team mainly work?

Agile (Scrum or Kanban)
DevOps / DevSecOps
Waterfall
A mix
Other:

4.Which sector is your organisation in?

Section B: What Gets in Your Way

5.How often do you run into each of these?

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

Challenge	1	2	3	4	5
Security tools interrupt what I am doing
I have to wait for the security team to approve something before I can carry on
Security training is generic and does not relate to what I actually build
Security problems turn up late, close to or after release
Privacy requirements (GDPR, CCPA) pull me out of the work I was doing
Resilience and failure handling get looked at too late
Compliance requirements feel like paperwork, separate from good engineering

6.Which one of these costs you the most time?

Select one

Security tools interrupting my work
Waiting on the security team for approvals
Rework when security problems are found late
Privacy requirements (GDPR, CCPA)
Resilience work left until late
Compliance work that does not feel like engineering

7.In a typical week, how many hours do you lose to security-related interruptions or rework?

Section C: How Security Works Today

8.Does your organisation do threat modelling?

Yes, regularly (every sprint or release)
Yes, for major features only
Rarely, or it depends on the team
No
Not sure

9.Who makes the security decisions in your development workflow?

Individual developers
A dedicated application security team
Security champions within the development teams
External consultants
It is shared, and nobody really owns it

10.When are security problems usually found?

During design or architecture
During development (code review)
During testing or QA
During the security review before release
After release, in production

Section D: Privacy & Resilience

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

It is part of the development workflow, with clear patterns to follow
Legal or compliance review it before release
We deal with it when a privacy problem comes up
A separate privacy or legal team handles it
There is no set approach

12.When does your team think about failure modes and resilience?

During the initial architecture or design
During development
During testing or QA
After something has failed in production
There is no set approach

Section E: What Matters to You

13.How much does each of these matter to you personally?

1 = Not at all, 2 = Slightly, 3 = Moderately, 4 = A lot, 5 = A great deal

Outcome	1	2	3	4	5
Security that fits into the way I already work
Shipping faster with fewer blockers
Being able to make security decisions without waiting on a specialist team
Privacy requirements handled as part of development, not after it
Finding problems at design time rather than after deployment
Systems designed to cope with failure from the start
Being seen as someone who brings in better ways of working
Working somewhere with a mature engineering and security culture

14.If you could fix one thing about how security, privacy or resilience works in your job, what would it be?

Section F: How You Judge New Tools

15.When your team looks at a new development tool, how much does each of these matter?

1 = Not at all, 2 = Slightly, 3 = Moderately, 4 = A lot, 5 = Essential

Factor	1	2	3	4	5
It works with the tools and workflow we already have
It is quick to set up and useful straight away
We can run it ourselves without depending on another team
The guidance it gives relates to the code I am actually writing
It helps with privacy by design
It helps with resilience and failure mode analysis
We can measure the time it saves
Other engineers we trust already use it

Section G: Influence in Your Team

16.How often do you suggest tools or ways of working to your teammates?

Weekly or more
About monthly
A few times a year
Rarely

17.What would make you push for a new tool inside your organisation?

Select all that apply

It makes me more productive
It improves quality (fewer bugs and issues)
It saves the team time
Recognition from peers or management
It matches good engineering practice
It helps the team succeed
Other:

18.Before recommending a tool, how do you prefer to try it?

Try it myself in my own workflow
A guided demonstration with a technical deep-dive
A recommendation from a colleague I trust
Published case studies and testimonials
A proof of concept with the team involved

Section H: Your View on a Different Approach

19.Imagine an approach that brought security, privacy and resilience checks into design and development, with guidance you could act on without waiting for a specialist. How far do you agree with each statement?

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

Statement	1	2	3	4	5
That would deal with the problems that slow me down most
Dealing with security at design time, not at deployment, is worth the effort
Security guidance I could act on myself would make me more productive
Privacy patterns built into development would reduce my compliance work
Thinking about resilience early would prevent some production incidents
I would try something like this in my next sprint
I would recommend it to teammates if it worked

20.What would put you off adopting something like this?

21.Is there anything else about your work we should know, including things your team has already tried?

TRUSTED PATH