AI Fatigue Self-Assessment
Your Quiz Results — What They Mean & What to Do
Deep, honest guidance for every level of AI fatigue. Find your tier below — then keep reading.
You're holding up well
Score 0–3 out of 15. You're staying grounded. Your relationship with AI tools is still in your control — and that's worth protecting intentionally.
A low score here doesn't mean AI tools aren't affecting you — it means you haven't lost the thread yet. You still think before you act. You still feel ownership over your work. You still know what you've built and why.
That's not small. In 2025, maintaining that while being surrounded by AI pressure is genuinely difficult. But here's the honest part: the engineers who felt fine at 3 on this quiz didn't feel fine at 3 six months later. The drift is gradual. It doesn't announce itself.
What this tier feels like
- You use AI tools as tools — not as a crutch or a replacement for thinking
- You can still explain most of what you've written, even if AI helped scaffold it
- Sunday evenings are mostly fine — work is work, but it doesn't loom
- You feel a sense of craft — not every day, but enough to know it's there
- You have opinions about how to solve problems, not just prompts
🗓 Your action plan — staying here
Set one deliberate no-AI hour per day
Not because AI is bad. Because conscious choice matters. Know when you're choosing to use it — don't just default to it. Even 60 minutes of unassisted thinking per day keeps the muscle alive.
Track the drift — retake this quiz in 30 days
Bookmark this page. Come back on the same day next month. If your score has moved up by 2+ points, something has shifted and it's worth paying attention to before it compounds.
Build your own AI use framework
Decide, explicitly, what you will and won't use AI for. Not a company policy — yours. "I use AI for boilerplate, documentation, and syntax. I do not use it for architecture decisions or debugging until I've spent 20 minutes on it myself." Written rules beat good intentions under deadline pressure.
Watch for the acceptance threshold creeping down
The warning sign at this tier is subtle: you start accepting AI suggestions a little faster, questioning them a little less. Not once — consistently. That's the beginning of the drift. Name it when you notice it.
⚠️ Common traps at this tier
Complacency
Feeling fine now doesn't mean the environment isn't exerting pressure. Stay conscious.
Productivity trap
If AI use is increasing your output metrics, it can be hard to notice when it starts costing you something harder to measure — ownership and craft.
Peer pressure drift
"Everyone else is using it constantly, maybe I should too." Resist the ratchet. Your sustainable pace is yours.
Ignoring early signals
A slight Sunday heaviness, one week where you accepted more AI output than felt right. Small signals. Don't wait for them to become loud.
Explore next
Some fatigue is showing
Score 4–7 out of 15. You're in the grey zone. Not burnt out — but not quite yourself either. The pace has gotten to you in places. This is the most common place for engineers to be right now.
Here's the thing about the grey zone: it's deceptively liveable. You can function. You can ship. But something's shifted — the satisfaction isn't quite what it was, the Sunday evenings are a bit heavier, the code feels slightly less yours than it used to.
Most engineers in this tier dismiss it. "It's just busy season." "I'm tired." "Everyone feels like this." Some of that is true. But some of it is a real signal — and the engineers who caught it here didn't have to claw their way back from the 12–15 range.
What this tier feels like
- You notice you sometimes accept AI output without fully reading it — especially under deadline
- Sunday evenings have gotten heavier in the last few months
- The satisfaction of problem-solving feels slightly diluted — you still feel it, but it's quieter
- You're not sure if your technical instincts are as sharp as they used to be
- You feel mild pressure — usually unspoken — to use AI tools even when your gut says to slow down
- You can still explain your work, but you've noticed yourself saying "the AI wrote part of this" more often
🗓 Your action plan — resetting before it compounds
Take one full no-AI coding session
Not to prove anything. Just to check in with yourself. Pick a real problem — something from your backlog, a side project, anything. Work it without AI for 90 minutes. Notice what that feels like. The discomfort is information.
Name what specifically has changed
Write it down. Actual sentences. "I used to feel X when I solved a hard problem. Now I feel Y." "The part that's gotten heavier is Z." Vague unease is harder to address than specific observations. Journaling here isn't navel-gazing — it's diagnostic.
Audit your AI use for one day
Keep a tally. Every time you reach for an AI tool, make a mark. Then, at the end of the day, look at each instance: Was that the right call? Was I thinking first, or did I default? This isn't about guilt — it's about making the unconscious conscious so you can choose.
Try one week of the 30-day plan
You don't need to commit to the full month. Do Week 1: Awareness. It's designed exactly for this grey-zone moment — gentle, structured, and specific enough to actually work. Many engineers in your tier have found this week alone meaningfully shifts things.
⚠️ The grey zone traps
"I'll deal with this when it gets worse"
The grey zone is precisely when it's easiest to intervene. By the time it's undeniably worse, you'll have less energy to address it.
Using output as reassurance
"I'm still shipping fast, so I'm fine." Speed is not the same thing as health. You can be depleted and still fast.
Waiting for a vacation to fix it
A week off doesn't change the conditions you return to. The reset needs to be structural, not just temporal.
Comparing up
"My colleague is at 12 on this quiz — I'm fine by comparison." Your wellbeing isn't relative to someone else's worse state.
What to read next
Real AI fatigue is present
Score 8–11 out of 15. This isn't mild. You're carrying more than you should have to. The volume, the pace, the constant context-switching — it's taken a real toll. But you're here, reading this, which matters.
Something has shifted in your relationship with your work. It might be that the satisfaction from solving problems feels distant now. It might be that you've noticed yourself explaining less and accepting more. It might be the Sunday dread that didn't used to be there.
This isn't a character flaw. This isn't weakness. This is what happens when intelligent, skilled people are asked to operate in an environment that's been redesigned around throughput — and the human cost wasn't factored in. You are not the anomaly. The environment is.
The hard part: you're probably still shipping. Which means nobody else is necessarily seeing what's happening to you. That isolation — carrying a real thing in a context where everyone looks fine — is its own weight.
What this tier tends to feel like
- The craft satisfaction — the thing that made you love this work — feels mostly gone right now
- You've accepted AI output without understanding it more times than you'd like to admit
- Sunday evenings have a persistent weight to them — a specific anxiety about AI velocity and keeping pace
- You feel like you're performing the role of a software engineer more than actually being one
- When you try to work without AI, there's anxiety — "am I still capable of this without it?"
- You might have noticed your debugging instincts have gotten rusty — you reach for AI before sitting with the problem
- The work feels hollow in a way that's hard to explain to someone who isn't experiencing it
🗓 Your action plan — real recovery
Name it — out loud or on paper
"I am experiencing AI fatigue. My relationship with my work has been affected by the volume and pressure of AI tool use. This is real and it deserves attention." Write that sentence. The act of naming it moves it from vague unease to something you can actually work with.
Read stories from engineers who've been here
You're not alone in this. The specific flavour of hollowness you're describing — the performance of engineering, the ghost authorship, the lost instincts — others have lived this and found their way back. Reading their words can break the isolation.
Reclaim one small piece of craft
Not a full detox. Not a dramatic gesture. One thing: a function you write from scratch, a bug you debug without pasting it to AI, a system you design on paper first. One experience of "I built that without a shortcut" per week. The satisfaction is still there. It needs to be woken up.
Reduce AI volume, not just AI use
At this tier, going cold-turkey tends to backfire — it's disorienting and can feel like a performance step down. Instead: reduce the density. If you're currently accepting every suggestion, aim for rejecting or rethinking 30% of them. The goal is reinstating your judgment as the gate, not eliminating the tool.
Work through the full recovery guide
The recovery guide is structured specifically for engineers at this tier — it has 7 phases, a day-by-day timeline, and specific strategies mapped to the dimensions of AI fatigue (cognitive, emotional, identity, social). It's not motivational content. It's practical.
Have the workplace conversation if needed
If part of your fatigue comes from workplace pressure to use AI constantly — tooling mandates, velocity expectations, implicit signals that slowing down is falling behind — that pressure needs to be addressed, not just managed around. The workplace guide has scripts for exactly this conversation.
⚠️ The tier 3 danger zones
Productivity as proof of fine-ness
You might be hitting all your metrics while being deeply depleted. Output is not a reliable signal of internal health at this stage.
Letting it drift to Tier 4
At 8–11, recovery is real and achievable with deliberate effort. At 12–15, it requires significantly more. This is the easier inflection point.
Isolation
Carrying this alone — assuming everyone else is fine and it's just you — intensifies it. Talk to someone who gets it, even if that's just reading a story that resonates.
Waiting for a sign that it's "real enough"
This is real enough. You don't need to wait for a breakdown or a crisis to justify taking it seriously.
Your recovery reading list
You need a real break
Score 12–15 out of 15. This isn't a slump. You're describing significant depletion — the kind that doesn't resolve with a long weekend. Please read this carefully.
What you're describing — the inability to fully explain your own work, the absent satisfaction, the specific anxiety about keeping pace with AI, the feeling of performing engineering rather than doing it — these are not mild symptoms. These are the markers of engineers who are close to a breaking point.
Please hear this: you are not broken. You are a person who has been operating under sustained, unprecedented pressure in a professional environment that has radically changed — faster than any human can reasonably adapt to — and the cost of that has accumulated in you. That's not a failing. That's physics.
But it does require real attention. Not "work less hard for a week." Real, structural recovery. And potentially — if the disconnection and anxiety are affecting your life beyond work — professional support. There is no shame in that. There is only sense.
What engineers at this tier describe
- "I paste code into the AI before I've even really looked at it. It's become my first instinct."
- "I can't remember the last time I felt proud of something I built."
- "I feel like an AI operator, not a software engineer."
- "When I try to code without AI, I feel lost. Like the skill has gone somewhere and I can't find it."
- "The Sunday dread is specific. It's about not being able to keep up with the AI pace. Like I'm always one week behind becoming obsolete."
- "A junior engineer asked me to explain part of the codebase and I had to say I wasn't sure. That's never happened before."
- "I used to love this. I genuinely don't know if I still do."
🗓 Your action plan — genuine recovery
Stop — just for a moment
If you're reading this in a work context, close your work tabs for ten minutes. This isn't a trick or a "mindfulness tip." It's a physiological intervention: your nervous system is carrying something, and it needs even a brief signal that it's allowed to pause. Breathe. You're here.
Tell one person
Not necessarily a manager. A colleague you trust, a partner, a friend who'll understand. Say some version of: "I've been running on empty with the AI stuff at work and it's really gotten to me." Out loud. The act of saying it breaks the isolation that tends to compound depletion at this level.
Take at least one real day off — actually off
Not "work from home but lighter." A full day. No Slack, no email, nothing work-adjacent. If your role makes this hard, use a sick day. You are not well. Using sick time for this is entirely appropriate. The day after that day, you will be able to think more clearly about what comes next.
Consider a professional conversation
If the disconnection from your work is accompanied by broader symptoms — sleep disruption, persistent low mood, anxiety outside of work, difficulty feeling present with the people you care about — please talk to a doctor or therapist. AI fatigue at this level can tip into clinical burnout, and that requires clinical support. This site is not a substitute for that.
Rebuild a tiny piece of something
No AI. A small personal project — something that doesn't matter, that nobody will see. A script that does something simple. A function that solves a problem you actually have. The goal isn't capability — it's reconnection. Feeling your hands on the work again. This is a seed, not a sprint.
Structural change — not just personal resilience
Recovery at this tier is not about you becoming stronger or more efficient. It's about changing the conditions. That might mean a workplace conversation about AI pressure, a team agreement about deep work time, a different role, or a different company. You can't sustain recovery if the environment that created the problem stays exactly the same.
🆘 If you're in crisis
If you're experiencing thoughts of self-harm or feeling that things are genuinely hopeless, please reach out to a crisis line. 988 (US Suicide & Crisis Lifeline), 116 123 (Samaritans UK), or text HOME to 741741 (Crisis Text Line). Your wellbeing matters infinitely more than your productivity or your code. Please reach out.
⚠️ What doesn't help at this tier
"Push through it"
Resilience advice that tells you to work harder through depletion is wrong. Rest is not weakness — it's the mechanism of recovery.
A vacation without structural change
A week away helps short-term. But if you return to exactly the same conditions, you'll be back here — usually faster than the first time.
White-knuckling it in silence
Keeping this entirely to yourself while continuing to operate at full output is the most reliable path to a complete breakdown.
Consuming more content about AI fatigue
Reading is not recovering. At some point you need to put the browser down and actually do less — or do something that reconnects you to your body and hands.
Read these — in this order if possible
Not sure where you landed?
Take the quiz and you'll be directed to your specific tier. It takes two minutes, runs entirely in your browser, and stores nothing.
Frequently asked questions about results
What does my AI fatigue quiz score actually mean?
Scores 0–3 mean you're holding up well with healthy AI habits. Scores 4–7 show some fatigue accumulating. Scores 8–11 indicate real AI fatigue requiring active intervention. Scores 12–15 suggest significant depletion that warrants a genuine break and possibly professional support.
The score is a snapshot of this moment — it can and does change, in both directions. It's diagnostic, not destiny.
Is a high score permanent? Can I actually recover?
AI fatigue is not a fixed state. Many engineers have moved from high-fatigue states back to healthy relationships with their work. Recovery requires specific, intentional action — not just "relaxing more" — but it is genuinely achievable.
The key factors: reducing AI volume (not necessarily eliminating it), reclaiming craft through unassisted practice, addressing workplace pressures, and rebuilding the sense of ownership over your work. Our recovery guide has the full framework.
I scored differently than I expected. What should I do?
If you scored lower than expected: read your tier anyway. The descriptions of what that tier feels like might still resonate, even if the score surprises you.
If you scored higher than expected: take it seriously. The questions are calibrated carefully, and high scores from engineers who feel "basically fine" often reflect the grey zone — where you can function but the drift has already started.
Can I share my specific tier results with someone?
Yes — each tier has a direct anchor link you can copy and share. No personal data is attached. The links go directly to that tier's content on this page. Use the "Copy link" button on each tier section, or just bookmark/share the anchor URL directly.
Should I show my manager my quiz results?
That depends entirely on your manager and your relationship with them. If you have a manager who is psychologically safe and genuinely interested in your wellbeing, sharing your results can be a useful starting point for a real conversation. Our workplace guide has specific scripts for how to start that conversation, including how to frame AI fatigue without it sounding like a performance concern.
If your manager is part of what's driving the pressure, it might be more productive to speak to HR or a trusted colleague first.