すべてのテンプレート
Developer & Engineering

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.

登録なしでお試し可能・無料プランでも回答数無制限

ライブプレビュー
SRE/DevOps On-Call Workload & Recovery Assessment

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.

Powered by QuestionPunk

デフォルト テーマ。色とフォントは自由に変更できます。

設問の例

テンプレートの内容をプレビューできます。すべての設問は公開前に自由に編集できます。

全23問・約11分
メッセージ

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.

Q01
選択式

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
Q02
選択式

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
Q03
プルダウン

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)
Q04
プルダウン

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
Q05
プルダウン

How many of those alerts woke you from sleep?

  • 0
  • 1
  • 2–3
  • 4–5
  • 6–10
  • More than 10
Q06
オピニオンスケール

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

スケール: 1 – 7
最小:Not at all demanding最大:Extremely demanding
Q07
オピニオンスケール

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

スケール: 1 – 7
最小:Never最大:Very frequently
Q08
オピニオンスケール

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

スケール: 1 – 7
最小:Never最大:Very frequently
Q09
オピニオンスケール

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

スケール: 1 – 7
最小:Never最大:Very frequently
Q10
オピニオンスケール

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

スケール: 1 – 7
最小:Not at all disruptive最大:Extremely disruptive
Q11
プルダウン

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
Q12
選択式

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)
Q13
オピニオンスケール

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

スケール: 1 – 7
最小:Not at all effective最大:Extremely effective
Q14
オピニオンスケール

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

スケール: 1 – 7
最小:Very dissatisfied最大:Very satisfied
Q15
ランク付け

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
ドラッグして順位を付ける
Q16
オピニオンスケール

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

スケール: 1 – 7
最小:Not at all最大:To a great extent
Q17
選択式

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)
Q18
プルダウン

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
Q19
自由回答(長文)

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

Q20
AIインタビュー

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

Q21
選択式

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)
Q22
プルダウン

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
Q23
プルダウン

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
メッセージ

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!

含まれる機能

  • 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

よくあるご質問

「SRE/DevOps On-Call Workload & Recovery Assessment」テンプレートにはどのような設問が含まれていますか?

すぐに使える設問が23問含まれており、最初の設問は次のとおりです:「When was your most recent on-call rotation?」・「How often are you currently scheduled for primary on-call duty?」・「Approximately how many total hours did your most recent on-call rotation cover?」。すべての設問は上でプレビューでき、自由に編集できます。

このアンケートの回答にはどのくらい時間がかかりますか?

回答者は通常、23問を約11分で回答し終えます。

テンプレートは編集できますか?

はい。公開前であれば、すべての設問、選択肢、順序を編集できます。設問の追加や削除のほか、調査の目的に合わせた作り直しをAIエディターに依頼することもできます。

このテンプレートは無料で使えますか?

はい。エディターで開けば、すぐに編集を始められます。お試しにアカウントは不要で、無料プランでアンケートを公開できます。

公開の準備はできましたか?

このテンプレートをエディターで開いてみてください。最初の回答者が目にする前に、すべてを自由に変更できます。

関連テンプレート

似たテーマのほかの調査もご覧ください。

すべて見る