모든 템플릿

SRE/DevOps On-Call Workload & Recovery Assessment

Measures on-call alert burden, interruption impact, recovery effectiveness, and compensation preferences across engineering teams to benchmark workload and identify actionable improvements to reduce burnout.

샘플 질문

템플릿에 포함된 내용을 미리 확인해 보세요. 모든 질문은 설문 공개 전에 자유롭게 수정할 수 있습니다.

질문 25개 · 약 11분
Q01
메시지

Welcome to the On-Call Workload & Recovery Assessment. This survey explores your experiences with on-call work, including alert volume, interruptions, recovery practices, and potential improvements. Your responses will be kept confidential and reported only in aggregate. There are no right or wrong answers — we are interested in your honest opinions and experiences. Participation is voluntary and you may stop at any time. Estimated time: 6–8 minutes.

Q02
객관식

When was your most recent on-call rotation?

  • Within the last week
  • Within the last 2 weeks
  • Within the last month
  • Within the last 3 months
  • More than 3 months ago
  • I have never been on-call
Q03
객관식

How often are you currently scheduled for primary on-call duty?

  • Every week
  • Every 2 weeks
  • Monthly
  • Every 6–8 weeks
  • Quarterly or less
  • Ad hoc / back-up only
  • Other
Q04
의견 척도

Overall, how demanding was your most recent on-call rotation?

척도: 17
최소:Not at all demanding최대:Extremely demanding
Q05
객관식

Which of the following practices, if any, do you use to regain focus after handling alerts? Select all that apply.

  • Take a short break
  • Write notes/to-do list before switching tasks
  • Time-block a recovery window
  • Silence non-essential notifications
  • Post-incident recap with team
  • Pomodoro or similar timed-work cadence
  • Meditation or breathing exercises
  • Caffeine
  • Switch to a different task temporarily
  • None of the above
  • Other (please specify)
Q06
의견 척도

How satisfied are you with your current alerting and paging tools overall?

척도: 17
최소:Very dissatisfied최대:Very satisfied
Q07
의견 척도

To what extent, if at all, would additional compensation improve your overall experience with on-call work?

척도: 17
최소:Not at all최대:To a great extent
Q08
장문형

What single change would most improve on-call workload or recovery for your team?

Q09
객관식

What best describes your primary role?

  • SRE / Site Reliability Engineer
  • Platform / Infrastructure Engineer
  • Backend Engineer
  • Frontend Engineer
  • Full-stack Engineer
  • Data / ML Engineer
  • QA / Testing Engineer
  • Engineering Manager / Tech Lead
  • DevOps Engineer
  • Other (please specify)
Q10
메시지

Thank you for completing this survey — your responses have been recorded and will be used to improve on-call practices. Your input is greatly appreciated!

Q11
드롭다운

Approximately how many total hours did your most recent on-call rotation cover?

  • Less than 8 hours
  • 8–24 hours
  • 25–48 hours
  • 49–72 hours
  • 73–120 hours (3–5 days)
  • 121–168 hours (5–7 days)
  • More than 168 hours (over a week)
Q12
의견 척도

During your most recent rotation, how frequently did alerts interrupt your deep work or coding sessions?

척도: 17
최소:Never최대:Very frequently
Q13
의견 척도

Overall, how effective are your current recovery practices at helping you regain focus after on-call interruptions?

척도: 17
최소:Not at all effective최대:Extremely effective
Q14
순위 매기기

Please rank the following potential improvements by how much they would improve your on-call experience (1 = highest impact).

  1. Better alert routing / noise reduction
  2. Clearer runbooks / playbooks
  3. More automation / self-healing systems
  4. Smarter scheduling / coverage distribution
  5. Focus / quiet-hours protection
  6. Faster incident tooling / UI
  7. Improved compensation and incentives
드래그하여 순위 지정
Q15
객관식

If additional compensation were offered for on-call work, which forms would you find most valuable? Select up to 3.

  • Fixed monetary stipend per rotation
  • Per-incident payment
  • Hourly pay for on-call hours
  • Additional paid time off
  • Flexible work hours / schedule adjustments
  • Professional development budget
  • Recognition or awards
  • Other (please specify)
Q16
AI 인터뷰

Based on your responses throughout this survey, please share any additional thoughts about your on-call experience, workload, or recovery practices.

Q17
드롭다운

How many years of professional experience do you have?

  • Less than 1
  • 1–2
  • 3–5
  • 6–10
  • 11–15
  • 16–20
  • More than 20
Q18
드롭다운

Approximately how many distinct alerts or pages did you receive during that rotation?

  • 0
  • 1–3
  • 4–7
  • 8–15
  • 16–30
  • 31–50
  • More than 50
Q19
의견 척도

During your most recent rotation, how frequently did alerts interrupt meetings or collaborative work?

척도: 17
최소:Never최대:Very frequently
Q20
드롭다운

If monetary compensation were provided, what would you consider a reasonable additional payment per on-call rotation?

  • Less than $50
  • $50–$100
  • $101–$200
  • $201–$350
  • $351–$500
  • $501–$750
  • $751–$1,000
  • More than $1,000
  • Not sure / prefer not to say
Q21
드롭다운

Approximately how many employees work at your organization?

  • 1–10
  • 11–50
  • 51–200
  • 201–1,000
  • 1,001–5,000
  • 5,001–10,000
  • More than 10,000
Q22
드롭다운

How many of those alerts woke you from sleep?

  • 0
  • 1
  • 2–3
  • 4–5
  • 6–10
  • More than 10
Q23
의견 척도

During your most recent rotation, how frequently did alerts interrupt your personal or family time (outside work hours)?

척도: 17
최소:Never최대:Very frequently
Q24
의견 척도

How disruptive were alert-driven context switches to your overall productivity during your most recent rotation?

척도: 17
최소:Not at all disruptive최대:Extremely disruptive
Q25
드롭다운

During work hours, how long does it typically take you to regain full focus after handling a non-trivial alert?

  • Under 2 minutes
  • 3–5 minutes
  • 6–10 minutes
  • 11–20 minutes
  • 21–30 minutes
  • More than 30 minutes

포함된 기능

  • AI 후속 질문

    정형화된 설문이 놓치는 세부 내용을, 주관식 답변에 맞춰 AI가 심층 질문으로 끌어냅니다.

  • 주의력 확인 장치

    성의 없는 답변과 저품질 응답자를 걸러내는 내장 안전장치입니다.

  • AI가 작성한 문안

    문구, 질문 순서, 분기 로직까지 AI가 연구 목표에 맞춰 작성합니다.

  • 자동 리포트

    응답이 모이면 주요 주제, 인용문, 이해하기 쉬운 요약이 자동으로 작성됩니다.

다른 서비스와 비교

다른 설문 도구의 가장 유사한 템플릿을 검토했습니다. 그 도구들이 잘하는 점과, 이 템플릿이 한발 더 나아가는 지점을 정리했습니다.

이 템플릿을 선택하는 이유

  • Includes an AI follow-up interview that probes each respondent's specific on-call experience after they've answered the structured questions, rather than stopping at fixed fields
  • Combines quantitative burden metrics (alert counts, sleep disruption, rotation hours) with opinion-scale ratings on interruption impact and recovery effectiveness, giving both scale and depth
  • Directly asks about compensation preferences and reasonable additional pay amounts, translating workload data into an actionable, negotiable outcome
  • Ends with automated reporting, so engineering leaders get a synthesized view of workload and burnout risk without manually coding open-text responses

SurveyMonkey

Employee Workload Survey Template

A general-purpose employee workload template that could be adapted for engineering on-call contexts but isn't built specifically around alert volume, page frequency, or recovery practices. It's a fielding-ready static form, useful for broad workload sentiment rather than SRE-specific operational metrics. Good starting point if a team wants quick deployment without customizing for on-call nuances.

잘하는 점

  • Fielding-ready, quick to deploy for general workload sentiment
  • Backed by SurveyMonkey's established survey logic and reporting dashboard
  • Broad applicability across departments, not just engineering

아쉬운 점

  • Not tailored to on-call specifics like alert counts, sleep interruptions, or paging tool satisfaction
  • Static question set with no adaptive follow-up to probe individual burnout drivers
  • No mechanism to convert workload complaints into compensation-preference data

설문을 공개할 준비가 되셨나요?

이 템플릿을 편집기에서 열어 보세요. 첫 응답자가 보기 전에 모든 부분을 원하는 대로 바꿀 수 있습니다.