2025 Engineer AI Fatigue Survey:
2,400+ Responses, Real Data
We asked 2,423 software engineers how AI tools are affecting their mental health, skills, and careers. Here's the full picture — not the optimistic version.
How We Ran This Survey
Transparency about methodology isn't a formality — it's the difference between data you can trust and data that's just noise.
The AI Fatigue Quiz launched in May 2024 as a public self-assessment tool. After completing the quiz, respondents were invited to share detailed answers about their tool usage patterns, career context, and recovery attempts. Survey data was collected between May 2024 and May 2025, with a median respondent age of 31 and median 7 years engineering experience.
Collection Method
- Quiz-taker follow-up (68%)
- Engineering community invitations (22%)
- Direct outreach to EM groups (10%)
Demographic Controls
- Software engineering roles only
- 3+ months AI tool usage required
- Verified via LinkedIn/professional profiles
Which AI Tools Are Causing the Most Fatigue?
Not all AI tools erode engineer's cognitive baseline equally. The difference comes down to how deeply the tool integrates into core reasoning tasks.
GitHub Copilot users showed the highest fatigue rates at 71%, followed by ChatGPT API users (64%) and Claude Code users (51%). The common thread: tools used for autocomplete and code generation — rather than just search and reference — correlated with the steepest skill erosion signals.
Context Integration Predicts Fatigue Better Than Model Quality
The fatigue difference between Copilot (71%) and Cursor (48%) — despite Cursor using Claude as its model — suggests that how deeply the tool participates in your workflow matters more than which model it runs. Tools that autocomplete, auto-import, and auto-fix without deliberate breaks create the most dependency risk.
| Usage Pattern | Avg. Fatigue Rate | Primary Symptom |
|---|---|---|
| Continuous (all day) | 79% | Context exhaustion, skill atrophy |
| Frequent (multiple times/hour) | 68% | Decision fatigue, confidence gap |
| Regular (1-2x/day) | 52% | Productivity anxiety |
| Occasional (1-2x/week) | 31% | Mild retrieval friction |
| Light (sporadic) | 18% | Minimal |
Who Has the Highest AI Fatigue Risk?
The data contradicts a common assumption: it's not junior engineers who are most at risk. It's mid-career engineers — the ones who have the most to lose.
Engineers with 6-10 years of experience showed the highest AI fatigue rates — 72%, at 2.3x the rate of entry-level engineers. Senior engineers (11+ years) sat at 58%. The theory: mid-career engineers have internalized the highest professional standards, making AI-generated work feel most threatening to their self-concept.
👨💻 The Mid-Career Engineer (Highest Risk)
The person who learned to code by struggling through bugs. AI makes that struggle optional — which feels like a verdict on everything they built.
🧑🎓 The Junior Engineer (Lower Risk)
Born into AI tooling. Never experienced the struggle AI skips over. But learning through friction is how expertise gets built — and that's what's being lost.
Which Industries Have the Highest AI Fatigue Rates?
AI tool adoption wasn't uniform across the industry — and neither was the fatigue. Agency and freelance engineers led with the highest rates.
Agency/consulting highest due to high velocity + diverse tool usage. Gaming due to tight deadlines + prototype churn. Fintech high due to code quality pressure against AI speed.
The Four Severity Tiers
Not all AI fatigue is equal. We categorized respondents into four tiers — from mild cognitive friction to a full identity crisis about what it means to be an engineer.
55% of respondents fell into Tier 3 or Tier 4 — significant or severe AI fatigue. Only 28% remained in the mild tier. This isn't a fringe issue affecting a small percentage. It's the majority reality.
What Actually Helps Recovery
We asked respondents to rank interventions by effectiveness. The results challenge common advice like "just take a vacation."
"Vacation only" ranked lowest because passive rest doesn't rebuild active retrieval pathways. The problem is skill access, not energy.
Five Findings That Should Be Headlines
71% of GitHub Copilot users report AI fatigue symptoms. The tool's deep integration into the coding loop — auto-completion, auto-imports, auto-fix suggestions — correlates with the steepest decline in self-reported skill access. Users of more peripheral tools (Gemini, CodeWhisperer) reported significantly lower rates.
The 6-10 year cohort (72% fatigue rate) has internalized professional identity most deeply. They've spent years building the ability to ship complex systems from memory. AI shortcuts that process feel like evidence that those years of investment are becoming obsolete — a psychologically distinct burden from what junior engineers experience.
Both sectors operate under high velocity pressure (agency) or high code quality accountability (fintech). The combination of "ship faster" and "same quality bar" creates a specific strain profile: productivity anxiety layered over accuracy pressure, with no structural relief from tooling adoption.
Only 29% of respondents found time-off effective as a recovery intervention. The mechanism of AI fatigue — skill atrophy's effect on retrieval pathways — isn't reversed by passive rest. It requires active cognitive engagement without AI assistance. The most effective recoverers reported deliberate practice protocols.
This number is striking even accounting for self-selection bias (people with fatigue are more likely to take a fatigue quiz). The survey population skewed toward experienced engineers (median 7 years), which suggests this isn't a population that lacks technical skill. It's a population that's acutely aware of what AI tooling is changing.
Frequently Asked Questions
Take the AI Fatigue Quiz
See where you fall on the severity tiers. Get a personalized recovery plan based on your tool usage, career stage, and symptom profile.
Start the Assessment →