ADHD in Software Engineering: Why Sprints, Standups, and Context-Switching Hit Differently

Last reviewed: 08/10/2026

Reviewed by: Dr. Kiesa Kelly

Software engineering looks, from the outside, like it should suit an ADHD brain perfectly. Complex problems. Constant novelty. Immediate feedback from a compiler that tells you within seconds whether you were right. Puzzles, all day.

And for a lot of people it genuinely does. Then the sprint planning meeting arrives, and you are asked to put a number on how long something will take. Or you finish a two-week stretch of excellent work and realize you never updated a single ticket. Or you look at your calendar and discover the day has been sliced into fragments too small to hold a mental model in.

This post is about that gap — between the parts of the job that fit unusually well and the parts that cost far more than they appear to.

In this article, you'll learn:

• Why an interrupt-driven job is hard for a brain that struggles to regulate attention

• The five specific places engineering work and ADHD collide

• What the research on developers with ADHD actually shows, and what it does not

• Scaffolding built for engineering workflows rather than generic office work

• When systems are not enough, and when an evaluation is the more useful step

The core mismatch: focus-demanding work in an interrupt-driven job

Engineering asks for long, uninterrupted stretches of held context. Modern engineering organizations are built to interrupt you: the review request, the incident channel, the standup, the "quick question" that arrives as a direct message with no question in it.

For anyone, that costs something. Research on interrupted knowledge work found people do generally finish interrupted tasks, and finish them faster — but pay for it with measurably higher stress, frustration, time pressure, and effort [1]. The interruption itself is rarely the expensive part. The reconstruction is: rebuilding what you were doing, why, and what you had just ruled out.

Now add ADHD, which affects the regulation of attention rather than its quantity [2][3]. Re-entry after interruption is precisely an executive-function task — hold the goal, resist the more interesting new input, reconstruct the state, resume. When a large analysis of the 2022 Stack Overflow developer survey compared engineers with ADHD against neurotypical engineers, the finding that separated them most clearly was not raw ability. It was interruptions caused by waiting for answers, along with less frequent interaction outside their immediate team [4].

Misconception: if you can hyperfocus, it cannot be ADHD. Six hours lost in a debugging session is not evidence against ADHD. It is a familiar feature of it — attention that locks on hard when the material is engaging and will not deploy on demand when it is not.

Misconception: this is just what modern engineering feels like for everyone. Partly true, and worth saying plainly, because plenty of neurotypical engineers are also drowning in meetings. But the gap is measurable. In a survey of 239 developers with ADHD and 254 without, developers with ADHD had roughly 1.8 to 4.4 times the odds of reporting that they struggle more frequently — across every category of task the researchers examined, with the largest gaps in time management during design work [5]. Read those as odds ratios from self-report rather than a clinical measurement, and note that about half the ADHD group was self-identified rather than formally diagnosed. The direction is clear even with those caveats attached.

Misconception: seniority fixes it. Seniority usually makes the coding easier and the coordination harder — more meetings, more context-switching, more non-code obligations. For many people the hardest year is the one after a promotion away from hands-on work.

⚡ Key takeaway: The problem is rarely the engineering. It is the shape of the job around the engineering — interrupt-driven, prediction-heavy, and full of low-stimulation obligations.

The five collision points

1. Estimation

You are asked, routinely and in front of people, to predict how long unfamiliar work will take. That is a time-perception task, and time perception is among the domains ADHD most consistently affects. Qualitative research with software engineers who have ADHD lists task organization and estimation together among the most commonly reported struggles [6] — and the survey data puts the largest ADHD-versus-neurotypical gap in time management specifically during design work [5].

The cost compounds socially. A missed estimate is a public event that arrives with a narrative about your reliability attached, which is why estimation anxiety often outlasts the missed deadline. The underlying mechanism has more to do with internal time calibration than effort, which we cover in our post on time blindness in adults with ADHD.

2. Context-switching and re-entry

Four tickets, two review requests, and an incident thread in one afternoon is four separate reconstructions of state. Each is cheap in wall-clock time and expensive in executive load, and the depletion is cumulative — by four o'clock, the thing that fails is not your competence but your capacity to re-enter anything at all.

3. Standups and ping culture

A daily standup is a small, recurring, socially observed obligation to summarize your work. That is a working-memory and self-monitoring task disguised as a two-minute meeting, and it lands harder if you genuinely cannot remember what you did yesterday without checking. Asynchronous cultures help with the interruption cost and can worsen the tracking cost, because now the record-keeping is on you and there is no meeting forcing it.

4. The boring-but-critical work

Tests. Documentation. Ticket hygiene. The retro action item with your name on it. Low stimulation, no urgency, no immediate feedback, and nobody blocked — until suddenly somebody is. This is the exact profile of task that ADHD makes disproportionately hard, and the one most likely to be misread by others as an attitude problem rather than an activation problem.

5. On-call and sleep

On-call rotations disrupt sleep, and disrupted sleep degrades executive function, which makes every other item on this list worse the following week. Sleep problems are common in ADHD, and the relationship runs in both directions — which means a rotation that a colleague absorbs without much trouble can cost you several days of function.

⏱️ Key takeaway: Estimation, re-entry, standups, unglamorous obligations, and on-call are the five places the job reliably taxes exactly what ADHD makes expensive.

Hyperfocus: the asset that writes the feature and misses the meeting

Hyperfocus deserves its reputation and also deserves an honest accounting. It is the state in which the hard problem gets solved, the refactor lands, and six hours pass unnoticed. Teams benefit from it enormously.

It is also unreliable in a specific way: you cannot summon it for the thing that needs doing, and you cannot easily exit it for the thing that is scheduled. The same session that produced the excellent work also blew through the meeting, the meal, and the message you meant to answer. Treating hyperfocus as a straightforward superpower tends to leave people unsupported for the version of it that costs them — which is why the more useful framing is a state to be channelled and bounded rather than a gift to be celebrated.

Scaffolding that fits an engineering workflow

Generic ADHD workplace advice assumes a generic office. The general-purpose version of this — building external systems for ADHD at work — is the right foundation, and this is what it looks like translated into engineering terms:

• Estimate in ranges, and track your own multiplier. Keep a private record of estimate versus actual for a couple of months. Most people discover a fairly stable personal multiplier. Applying it is more accurate than trying harder to guess well.

• Treat the ticket tracker as external memory, not a reporting chore [10]. Write the next action into the ticket before you stop for the day — the specific next step, not a status. This turns tomorrow's re-entry from reconstruction into reading, which is the single highest-yield change on this list.

• Cap work in progress. A hard limit on open threads outperforms a better prioritization scheme, because the failure mode is not choosing badly; it is holding too many partial states at once.

• Leave a re-entry note. One line before any interruption you can see coming: what you were doing, what you had just ruled out, what is next.

• Batch and defend. Cluster meetings rather than scattering them, and protect at least one multi-hour block. Two protected blocks a week beat five fragmented days.

• Pair or body-double the tasks that will not start. Documentation and test-writing are far easier alongside someone. This supplies external activation when internal urgency is not available.

• Push for inclusive team practices. Grounded-theory research with neurodivergent software engineers concludes with a set of inclusive Agile practices for teams — the point being that some of this is properly a team design problem, not an individual coping problem [7].

🧰 Key takeaway: The highest-yield habit is writing tomorrow's first action into the ticket tonight. It converts the most expensive recurring task — re-entry — into reading.

When systems are not enough

Sometimes the scaffolding holds and the week still ends in exhaustion. That usually means one of three things is in play.

The systems keep lapsing. If you build good systems and stop using them within a month, the missing piece is the returning-to-them layer, which is what executive function coaching is designed to work on. The literature here is still developing but encouraging: reviews of adult ADHD coaching report improvements in ADHD symptoms and executive functioning, with a recent prospective study finding medium-to-large effect sizes on validated measures [8].

The cost has become emotional. Shame about the pattern, dread before standup, feedback landing far harder than intended, or a slow slide into burnout — none of these are fixed by better ticket hygiene, and therapy is the more appropriate tool. If the specific failure is the small-request freeze — the two-line email that sits for a week — we wrote about that pattern in detail in our post on ADHD, micro-demands, and the freeze response.

Nobody has ever named the pattern. Which is the next section.

When it's worth getting evaluated

Plenty of engineers work in genuinely badly designed environments and need a different team, not a diagnosis. The question becomes worth asking when the pattern is older and wider than this job: present since school rather than since this role, visible outside work as well as in it, and costly enough that you are routinely compensating with evenings and weekends.

Adult ADHD is common and frequently unrecognized, particularly in people whose academic ability carried them through school before the structure disappeared [9]. That last point matters in this field specifically — a lot of engineers were the kid who never studied and did fine, which is exactly the profile that delays recognition for decades. If that arc is familiar, our overview of why so many technical professionals are diagnosed as adults covers the wider pattern.

A decision heuristic you can apply now: if changing your team, role, or process reliably fixes it, it is a work-design problem. If the same difficulties have followed you across every job, every school, and every side project, an adult evaluation will tell you more than another system will. A structured evaluation is not just a label — it determines whether coaching, therapy, medical treatment, or formal accommodations is the right lever.

Questions worth asking any evaluator before you book:

1. Does the evaluation assess both ADHD and autism if both look plausible, or only one?

2. How does it account for masking and compensation in adults who have been managing for decades?

3. What developmental history do you gather if I have no childhood records and my parents are not available?

4. What do I actually receive at the end — specific recommendations, or a diagnostic label?

5. Is the report written so it can support workplace accommodation requests if I decide to pursue them?

For a lower-commitment first look, the ASRS and the ESQ-R are brief self-report screeners for ADHD symptoms and executive functioning; they sit within our mental health screening set. Neither diagnoses anything, but a high score is a reasonable reason to take the question seriously.

🧭 Key takeaway: If the difficulty is confined to this job, change the job. If it has followed you since school, the evaluation is the step that changes what actually helps.

Where this leaves you

The engineers who do best with ADHD in this field are generally not the ones who found the perfect tool. They are the ones who stopped treating estimation, re-entry, and unglamorous work as character tests and started treating them as predictable, engineerable failure points — with external structure, honest calibration, and support where structure runs out.

That reframe is available whether or not you ever pursue a diagnosis. And if the pattern turns out to be older than this job, knowing that changes what you do about it.

Wondering if ADHD explains the pattern?

A structured ADHD evaluation can tell you whether what you're noticing is ADHD, something else, or both — and what would actually help.

Schedule an ADHD evaluation →

Frequently Asked Questions

Why do so many programmers have ADHD?

It is not established that programmers have ADHD at higher rates than other professions — the honest answer is that we do not have good prevalence data by occupation. What we do have is a large, visible community of developers who identify with ADHD, and survey research showing that developers with ADHD report notably more difficulty than neurotypical peers across common engineering tasks. Visibility and volume of discussion are not the same as elevated prevalence.

Are people with ADHD better at coding?

The evidence supports strengths and challenges together, not a superpower. Qualitative research with software engineers who have ADHD describes real strengths — creative problem-solving, doing well on puzzle-like problems, thinking several steps ahead — alongside consistent difficulty with task organization, estimation, and sustained attention on low-stimulation work. Framing ADHD as an unqualified coding advantage tends to leave people without support for the parts that are genuinely hard.

Is software engineering a good career for someone with ADHD?

It can be an unusually good fit and an unusually costly one, sometimes in the same week. The work rewards deep problem-solving, novelty, and pattern recognition, which many people with ADHD do well. It also demands time estimation, context-switching, and steady attention to unglamorous tasks, which are the domains ADHD most reliably taxes. Fit usually depends less on the job title than on team structure and how interrupt-driven the role is.

Why can I code for six hours but not answer a two-line email?

Because ADHD affects the regulation of attention rather than the amount of it. Deeply engaging, feedback-rich work supplies its own activation; a short, low-stimulation, socially loaded task supplies none, so it needs executive effort you may not have available on demand. The size of the task is not what makes it hard — the absence of anything to hook attention is.

Why are sprint estimates so hard with ADHD?

Estimation is a time-perception task, and time perception is one of the domains ADHD most consistently affects. You are being asked to predict duration for work you have not done yet, without reliable internal calibration, and often out loud in front of colleagues. Task organization and estimation show up together as commonly reported difficulties in research with software engineers who have ADHD.

About ScienceWorks

ScienceWorks Behavioral Healthcare was founded by Dr. Kiesa Kelly, a licensed clinical psychologist with more than 20 years of experience in psychological assessment and evidence-based treatment. Our clinical team evaluates ADHD and autism in adults, including adults whose difficulties were masked for years by academic ability, and provides executive function coaching and therapy for the anxiety, burnout, and sleep problems that often travel with them.

We are a telehealth-forward practice serving Tennessee, with an in-person option at our Nashville office. Adult evaluations are scheduled around working hours where possible, and reports are written to be useful — specific recommendations rather than a label alone. Every article we publish is reviewed by a licensed clinician for accuracy before it goes live.

References

1. Mark G, Gudith D, Klocke U. The cost of interrupted work: more speed and stress. Proceedings of the SIGCHI Conference on Human Factors in Computing Systems (CHI), 2008. https://dl.acm.org/doi/10.1145/1357054.1357072

2. National Institute of Mental Health. Attention-Deficit/Hyperactivity Disorder. https://www.nimh.nih.gov/health/topics/attention-deficit-hyperactivity-disorder-adhd

3. National Institute for Health and Care Excellence. Attention deficit hyperactivity disorder: diagnosis and management (NG87). https://www.nice.org.uk/guidance/ng87

4. Liebel G, et al. Differences Between Neurodivergent and Neurotypical Software Engineers: Analyzing the 2022 Stack Overflow Survey. arXiv, 2025. https://arxiv.org/abs/2506.03840

5. Newman K, et al. "Get Me In The Groove": A Mixed Methods Study on Supporting ADHD Professional Programmers. Proceedings of the IEEE/ACM 47th International Conference on Software Engineering (ICSE), 2025. https://dl.acm.org/doi/10.1109/ICSE55347.2025.00242

6. Liebel G, Langlois N, Gama K. Challenges, Strengths, and Strategies of Software Engineers with ADHD: A Case Study. arXiv, 2023. https://arxiv.org/abs/2312.05029

7. Cognitive Dysfunction Effects in Software Engineers with ASD and ADHD: A Socio-Technical Grounded Theory. arXiv, 2024. https://arxiv.org/abs/2411.13950

8. Ahmann E, Saviet M, Otto M. Coaching for Adults With ADHD: A Prospective Study. American Journal of Lifestyle Medicine. https://journals.sagepub.com/doi/10.1177/15598276261432960

9. Centers for Disease Control and Prevention. Attention-Deficit/Hyperactivity Disorder in Adults: Morbidity and Mortality Weekly Report, 2024. https://www.cdc.gov/mmwr/volumes/73/wr/mm7340a1.htm

10. Risko EF, Gilbert SJ. Cognitive Offloading. Trends in Cognitive Sciences, 2016. https://www.sciencedirect.com/science/article/pii/S1364661316300985

Disclaimer

This article is for informational purposes only and is not a substitute for individualized clinical advice, diagnosis, or treatment. If ADHD symptoms are affecting your work, health, or wellbeing, speak with a qualified clinician about your specific situation.