Developer Experience Survey Question Bank

	A	B	C	D
1	HOW TO USE THIS This is a question bank of developer satisfaction questions. It's designed to help answer the question "Are developers working in an environment where they can be as effective as possible?" Read through them and figure out what topics and questions are useful for your team. You don't need to use all of them, otherwise the survey gets a bit long. It's useful to mix the order of the questions in your own survey.			Join the waitlist - Developer Productivity Metrics Course live group coaching with resources, templates, and other good stuff
2	Category	Question	Response Type	Notes

3	Overall Satisfaction	I’m satisfied with the development tools at our company.	1-5 scale	Use these questions for a high-level indicator of satsifactions.
4		I'm satisfied with our tech stack.	1-5 scale
5		We follow development best practices.	1-5 scale
6	Efficiency, Focus Time	I get enough focus time.	1-5 scale	Answers to these questions can be about daily work being interrupted (lots of bugs or fires to put out) or about projects being paused and switched out too often.
7		My normal work is regularly interrupted.	1-5 scale
8		I feel like a lot of my time gets wasted.	1-5 scale
9	Production, Monitoring	When there is an outage, I feel confident that we can repair it quickly.	1-5 scale	If your team isn't responsible for supporting production workloads, you can leave these questions out.
10		I have a good understanding of what's going on in production.	1-5 scale
11		I have confidence in our alerting, monitoring, and telemetry tools.	1-5 scale
12	Deployments and Releases	I’m satisfied with the level of test coverage.	1-5 scale	These questions tend to open up the most interesting discussions, because they touch on confidence in your automated tooling, and following best practices when it comes to CI/CD. Developers usually have strong opinions here, or want to replicate something that worked well for them on a previous team. The last question about release freuquency might need some coaching about "deployments vs. releases" if your team doesn't decouple them, or doesn't have that mental model.
13		It’s easy to deploy software.	1-5 scale
14		I’m satisfied with our CI/CD tooling.	1-5 scale
15		I’m satisfied with how frequently we release software.	1-5 scale
16	Collaboration and Knowledge	Our team spends enough time learning from our mistakes.	1-5 scale	If your team is releatively new, consider adding a question about onboarding here. Onboarding highlights all the pain when information isn't easily accessible by your team.
17		I can unblock myself if I get stuck.	1-5 scale
18		Our code review process helps us release better code.	1-5 scale
19	Codebase Health	We spend enough time refactoring code.	1-5 scale	Look out for connections between these answers and the ones from the Deployments and Releases category. There is usually some correlation.
20		Our codebase is easy to contribute to.	1-5 scale
21		We have a reasonable amount of technical debt.	1-5 scale
22	Project Planning, Team Processes	My projects have clear goals.	1-5 scale	If you suspect some dissastisfaction when it comes to sprint ceremonies or your planning processes, add more specific questions to help diagnose a root cause. These questions can be answered by your cross-functional team (product management/design/data/etc) if applicable.
23		I understand how all of my projects will be used by our customers.	1-5 scale
24		Our team processes are efficient.	1-5 scale
25		Our meetings are a good use of time.	1-5 scale
26	Tradeoffs	I often have to sacrifice quality in order to hit deadlines.	1-5 scale	The answers here are often related to the Project Planning category above.
27		I feel that we have too much to do and not enough people to do it.	1-5 scale
28		We make too many tradeoffs.	1-5 scale
29	Perceived Productivity	How productive do you feel on an average day?	1-5 scale	I recommend categorising responses to these open-ended questions and looking for patterns (for example, Answer A mentioned e2e testing and sprint planning, Answer B mentioned e2e testing, CI/CD, and project planning).
30		What would reduce friction in your day-to-day work?	Long answer
31		Anything else you want to share?	Long answer
32	Follow-up	I've noticed changes based on the feedback from the last survey.	1-5 scale	Include the 2nd and every subsequent survey.
33	Read the full article here: https://lauratacho.com/blog/a-deep-dive-into-developer-experience-surveys
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100