Developer Burnout Assessment

A developer burnout assessment is a self-check that scores engineering-specific stress patterns - code review pressure, deployment anxiety, on-call fatigue, sprint overload, imposter syndrome, and disengagement - to flag early burnout before it becomes a crisis. Answer 14 questions below for an instant risk score and personalized recommendations.

Your answers stay in your browser. We don't track, store, or send them anywhere.

The assessment

0 / 14 answered
1

I dread getting comments on my pull requests.

I dread getting comments on my pull requests.
2

I find myself avoiding code review even when teammates need feedback.

I find myself avoiding code review even when teammates need feedback.
3

I feel anxious before pushing or merging to production.

I feel anxious before pushing or merging to production.
4

I avoid deploying on Fridays (or near time off) out of fear something will break.

I avoid deploying on Fridays (or near time off) out of fear something will break.
5

Being on-call drains me for days even when nothing pages.

Being on-call drains me for days even when nothing pages.
6

When I get paged, I feel a sense of dread rather than focus.

When I get paged, I feel a sense of dread rather than focus.
7

Sprint deadlines feel unrealistic and I am chronically behind.

Sprint deadlines feel unrealistic and I am chronically behind.
8

I push myself to overcommit in planning to look productive.

I push myself to overcommit in planning to look productive.
9

I feel like I'm faking it compared to my teammates.

I feel like I'm faking it compared to my teammates.
10

I doubt I deserve my role even when my work is praised.

I doubt I deserve my role even when my work is praised.
11

I work after hours or weekends just to keep up.

I work after hours or weekends just to keep up.
12

I have trouble sleeping because I'm thinking about code or work problems.

I have trouble sleeping because I'm thinking about code or work problems.
13

I no longer feel curious or excited about the technologies I use.

I no longer feel curious or excited about the technologies I use.
14

I am cynical about my company, my team, or the value of what we ship.

I am cynical about my company, my team, or the value of what we ship.

Answer all 14 questions to see your score.

More free tools for engineering teams

Reduce the structural causes of burnout: realistic capacity, predictable review, less surprise in retrospect.

Browse all tools

Sprint Velocity Calculator

Calculate sustainable sprint capacity instead of overcommitting your team into the ground.

Open tool

Engineering Team Size Calculator

Estimate the team size your scope and timeline actually require - undersizing causes burnout.

Open tool

Code Review Checklist Generator

Make code review less personal and more predictable with a shared, language-aware checklist.

Open tool

Sprint Retrospective Template Generator

Turn vague team frustration into named issues your retro can actually fix.

Open tool

Developer burnout FAQ

Common questions about burnout in software engineering.

What is developer burnout?

Developer burnout is a state of chronic physical and emotional exhaustion caused by prolonged work stress in software engineering roles. It typically shows up as cynicism toward the work, reduced productivity, deployment and code review anxiety, on-call fatigue, and a sense of imposter syndrome that no longer responds to evidence of competence. Unlike normal stress, burnout doesn't recover after a long weekend.

How is developer burnout different from regular burnout?

Engineers face a unique mix of stressors: production code can break in front of users, code review is public and identity-loaded, on-call rotations interrupt sleep, sprint pressure compresses uncertain work into fixed timeboxes, and the field changes fast enough that everyone feels behind. Generic burnout quizzes miss those specifics, which is why this assessment is calibrated for software engineers.

What are the signs of programmer burnout?

Common signs include: dread before standups or code review, avoiding deploys (especially on Fridays), staying in the office or online longer just to feel productive, cynicism about the company or product, loss of curiosity about technology you used to enjoy, sleep disruption from work thoughts, and a persistent feeling that you're faking competence regardless of evidence to the contrary.

How do I recover from software engineer burnout?

Recovery usually requires both individual and structural changes. Individually: take real time off, set hard work-hour boundaries, reduce alcohol and screen time, and talk to a therapist. Structurally: reduce on-call load, push back on scope, switch to a healthier project or team, or take a longer sabbatical. Mild burnout can resolve in weeks; severe burnout often takes months. Don't try to power through it.

Is this developer burnout assessment a medical diagnosis?

No. This is a self-assessment tool to help you reflect on burnout-related patterns specific to engineering work. It is not a clinical instrument and does not replace evaluation by a licensed doctor or mental health professional. If your results are in the High or Severe range, or if you're struggling, please talk to a professional.

Burnout-proof your delivery

When the work outpaces your team, hire an AI developer.

Elite Coders AI gives you a full-stack AI developer for $2,500 per month - so on-call rotations, sprint pressure, and code review backlogs stop pinning your team into burnout.

Visit the Elite Coders AI homepage