DevOps Reliability & Incident Response Assessment

Welcome! Thank you for participating in this survey on DevOps reliability and incident response practices. This survey takes approximately 7–10 minutes. Your participation is entirely voluntary, and you may stop at any time. There are no right or wrong answers—we are interested in your honest experience and opinions. All responses are confidential and will be reported in aggregate only.

How often does your team deploy changes to production?

• Multiple times per day
• Daily
• Weekly
• Every 2 to 4 weeks
• Monthly or less

Are you currently part of an on-call rotation for production services?

• Yes
• No

In the past 30 days, approximately how many user-impacting incidents did your team handle?

• 0
• 1–2
• 3–5
• 6–10
• 11–20
• More than 20

In the past 30 days, approximately how many pages or high-priority alerts did you personally receive?

• 0
• 1–5
• 6–15
• 16–30
• 31–60
• More than 60

Rank the following on-call pain points from most to least painful.

1. Noisy or low-signal alerts
2. Runbook gaps or outdated steps
3. Slow debugging due to limited traces/logs
4. Flaky deployments or rollbacks
5. Third-party instability

In the past 90 days, how often has your team experienced cascading failures or dependent-service outages?

In the past 90 days, how often has your team experienced degraded response times or latency spikes noticeable to users?

In the past 90 days, how often has your team experienced deployment rollbacks or failed releases?

In the past 90 days, how often has your team experienced data inconsistencies or silent failures?

How confident are you that error handling is robust across your team's critical user and system paths today?

Overall, how useful are your production alerts during incidents?

Please describe the most important error-handling gap you noticed in the past 90 days. What was its impact, and how was it addressed (if at all)?

Rank the following SLA/SLO dimensions by importance to your team, from most to least important.

1. Availability (uptime %)
2. Request latency targets
3. Error rate / error budget
4. Data freshness or latency targets
5. Recovery time objective (RTO)
6. Recovery point objective (RPO)

How well does your team currently meet its primary SLA/SLO targets?

We'd like to explore your reliability and SLA experiences in a bit more depth. An AI moderator will ask you a couple of follow-up questions based on your earlier responses.

If you could trade performance or features for greater stability, what would you change first, and why?

What is your primary role?

• Software engineer (IC)
• Tech lead / Engineering manager
• SRE / DevOps / Platform engineer
• Data / ML engineer
• QA / Testing
• Architect
• Product manager
• Other

How many years of professional software experience do you have?

• 0–1
• 2–4
• 5–9
• 10–14
• 15+

Approximately how large is your company?

• 1–10
• 11–50
• 51–200
• 201–1,000
• 1,001–5,000
• 5,001+

Which industry best describes your organization?

• SaaS / B2B software
• Consumer internet
• Financial services / Fintech
• Healthcare / Life sciences
• Gaming
• Media / Entertainment
• Retail / E-commerce
• Industrial / IoT
• Government / Public sector
• Other

Where are you primarily located?

• North America
• Europe
• Asia-Pacific
• Latin America
• Middle East / Africa

What is the typical size of the team responsible for your primary service or system?

• 1–3
• 4–7
• 8–15
• 16+

Thank you for completing this survey! Your input will help prioritize the reliability outcomes that matter most to engineering teams. All results will be reported in aggregate only.