ADHD and IT Career: Real Advantages and Challenges

ADHD and an IT career are an over-represented combination, and once you’ve worked in tech for a few years you stop being surprised. Half the standup is people who got diagnosed at 32, the other half is people who probably should and haven’t gotten around to it. I write this as a founder with ADHD who has shipped code, run sprints, and watched both myself and my colleagues burn out in interesting ways. This article is the peer-to-peer version of what I wish someone had told me at 25: why tech keeps pulling us in, what actually plays to our strengths, where the job quietly chews us up (Jira, standups, code review), and a few strategies that have held up for me and the ADHD developers I’ve worked with. No “10 hacks”. Just what I’ve seen work.

Why so many ADHD adults end up in tech

A few patterns repeat. Tech rewards rapid problem solving — a bug shows up, you chase it, you ship a fix, you get a small dopamine hit, repeat. That feedback loop is closer to a videogame than to most jobs. Hyperfocus is monetizable: a six-hour deep dive into a Postgres query plan is billable; the same intensity applied to organizing your closet isn’t. The hierarchy is flatter than in finance or law — the senior engineer with green hair and AirPods in is a normal sight. Remote work cuts out the office sensory overload. And the field changes fast enough that novelty seekers are functional, not weird.

CHADD and ADDA both note that adults with ADHD frequently gravitate toward careers where autonomy, variety, and intellectual stimulation are baked in. Tech ticks all three. The integration paper by Wiklund, Yu, Tucker and Marino (2017) on ADHD and entrepreneurship found that hyperactivity symptoms can have a positive effect in entrepreneurial contexts, mediated mainly by sensation-seeking. Same logic applies in product engineering teams that move fast.

It doesn’t mean tech is “easy” if you have ADHD. It means the friction is in different places than you’d expect.

The real advantages: where ADHD actually pays

Let’s name them concretely, not as inspirational slogans.

Pattern matching as debugging. A lot of ADHD brains run associative search by default. That’s a liability when you’re trying to follow a linear meeting agenda; it’s a superpower when you’re staring at a stack trace and three repos and you suddenly feel where the bug is. Senior engineers describe it as “intuition”. For us it’s often just our normal cognitive style finally finding a problem shaped like itself.
Hyperfocus on hard, novel problems. The review by Ashinoff and Abu-Akel (2021) proposes an operational definition of hyperfocus around four criteria: intense engagement, sustained attention, reduced perception of off-task stimuli, and improved performance. When you get a green-field architecture problem at 2 PM and look up to find it’s 8 PM and you’ve shipped something good, that’s the upside.
Non-linear creativity. Refactoring, naming, designing APIs, writing dev tooling — anything that needs jumping between layers of abstraction tends to suit an ADHD brain better than a strictly sequential one.
Novelty seeking as career insurance. Tech changes stack every 3-5 years. Wanting to learn the new thing isn’t a quirk; it’s how you stay employable. People who can’t tolerate change are the ones who get stranded on legacy COBOL teams, not us.
Less hierarchical environments. Performance is more visible. If your code works and you ship, a lot of soft-skill politics gets softened. Not all of it. But more than in most industries.

These are real. They’re also half the picture. The other half is what makes us quit, freelance, or burn out around year 7.

The real challenges: where the job grinds us down

Jira, standups, and meeting overhead

Modern engineering culture has bolted on a lot of process. Daily standups, sprint planning, retros, refinement, OKR reviews. Each one individually reasonable. Together they fragment the day into pieces too small to do deep work in.

For ADHD brains the cost is amplified. The classic Mark, Gudith and Klocke (2008) study on interrupted work in knowledge workers found it takes on average about 23 minutes to return to the original level of concentration after an interruption. If your calendar has four meetings spaced across the day, you don’t have “the time between meetings” — you have very little real focus time at all. Add to that Rubinstein, Meyer and Evans (2001) on task-switching costs (mental blocks from shifting tasks can eat up to 40% of productive time in the general population — likely amplified in ADHD).

Practical implication: meetings aren’t free, and “I have a 30-min gap” usually isn’t a 30-min gap.

Code review as RSD trigger

Rejection sensitivity isn’t formal DSM-5, but it’s one of the most consistent things ADHD adults report. Code review is structurally a critique-delivery system. A pull request comment that says “why are you doing it this way?” lands very differently in an ADHD nervous system than the reviewer intended.

The reviewer means: I want to understand. Your brain hears: I am bad at my job. Then you spend two hours doomscrolling instead of replying.

Knowing this doesn’t make it stop. But naming the pattern reduces its grip a little.

Sprint time management

ADHD time perception runs on a “now / not now” axis (Barkley, 1997, on self-regulation across time). A two-week sprint is “not now” until day 9, when it suddenly becomes “now and on fire”. This is normal for an ADHD brain and disastrous for sprint metrics.

If you’ve ever picked up a “small” ticket on day 1 and burned 80% of the sprint on it because it was actually two-week-shaped — welcome.

Accelerated burnout

Tech burnout is endemic generally. For ADHD adults it tends to come faster and bite harder, because we under-rest during hyperfocus stretches and over-deplete during context-switching weeks. If you want a fuller picture, I wrote about the dynamics in ADHD burnout: why it hits faster and harder.

Context switching across tasks and repos

Modern dev work assumes you can hop between three repos, four Slack channels, two PRs, and a customer ticket. Each context switch is a small tax. Across a day, the tax compounds. The classic multitasking research (Ophir, Nass and Wagner, 2009) suggests heavy multitaskers actually do worse on cognitive control tasks than light ones — so the people who feel most heroic about juggling are usually paying for it the most.

I unpacked this trap separately in ADHD and multitasking: myth vs reality.

Async vs sync collaboration

Async (written, Slack threads, GitHub comments, Notion docs) is usually better for ADHD brains: you can answer when your attention lands. Sync (meetings, pair programming, calls) is harder because you have to perform on someone else’s clock. Most companies do a mix — and the mix usually skews more sync than is ideal for us.

What works: practical strategies for ADHD developers

These are not productivity hacks. They’re the trade-offs that have actually held up for me and the ADHD engineers I’ve worked with.

1. Protect one deep-work block per day, ruthlessly

Pick a 90-120 minute slot. Block it on the calendar. Mark yourself away on Slack. Do hyperfocus-eligible work only in that slot. Everything else (PRs, replies, tickets) goes outside it. One deep block beats four interrupted ones every time.

2. Negotiate meeting density, not just meeting count

Five meetings clustered in one morning is much cheaper than five meetings spread across the day, because you only pay the context-switch tax once. If your calendar is up to you, batch. If it isn’t, ask your manager to batch — they often will, because no one actually likes scattered calendars.

3. Treat code review as a process, not a verdict

Read the comment. Wait two hours before replying if your nervous system spiked. Reply to the technical content, not the perceived tone. Most reviewers are not attacking you; the medium just strips emotional context. This is a skill, not a personality fix.

4. Right-size sprint commitments to your actual pattern

If you know day 1-7 will be slow and day 8-10 will be the burst, don’t over-commit at planning. Take 70% of what you think you can do. The crunch will appear anyway. Future-you will not be grateful for past-you’s optimism.

5. Externalize working memory aggressively

The Hervey, Epstein and Curry (2004) meta-analysis on adult ADHD neuropsychology found deficits across attention, behavioral inhibition, and memory. Translation: trying to “remember” what you were doing across context switches is a losing strategy. Use commit messages as breadcrumbs, write a one-line “where I left off” note before any meeting, keep a brain-dump file open.

For the everyday version of this — the thoughts that vanish before you can write them down — the brain dump in DopaHop is exactly that: ten seconds, thought is out of your head, you can come back to it when you want. I built it because I needed it.

6. Choose your role for your shape, not your prestige

Not all tech jobs are equal for ADHD. Greenfield product engineering, dev tooling, and SRE incident work tend to suit hyperfocus and pattern-matching. Long change-management cycles in enterprise consulting tend to grind us down. If you’re miserable in one tech role, the answer often isn’t “leave tech” — it’s “change the shape of the work”. I wrote more about that fit in ADHD and work: structured vs free environments.

A short note on diagnosis and support

If you’re reading this and quietly recognizing yourself, the next step isn’t a self-diagnosis from a blog post. In the UK that’s a GP referral; in the US, your PCP or a psychiatrist directly. CHADD (chadd.org) and ADDA (add.org) both maintain provider directories and adult-specific resources. If you’re in crisis, the numbers worth saving are 999 (UK), 911 (US), 988 (US Suicide & Crisis Lifeline), and 116 123 (Samaritans, UK and Ireland).

A diagnosis won’t make Jira any less Jira. But it changes the explanation you have for yourself, which changes which strategies you’ll actually stick with.

Frequently asked questions

Is it true that “everyone in tech has ADHD”?

No, but the rate does seem higher than baseline, and it’s plausibly self-selection: tech rewards traits (novelty seeking, hyperfocus, pattern matching) that map onto ADHD strengths. There’s no clean prevalence number for “tech workers” specifically — most figures are anecdotal or from internal company surveys. Treat the “everyone has ADHD” line as a vibe, not a stat.

Should I disclose my ADHD diagnosis to my employer?

It depends on country, company, and manager. Legally in most places (UK, US, EU) ADHD can qualify as a disability with formal accommodations available. Practically, disclosure is most useful when you want a specific accommodation (focus time, async-first, written agendas). It’s least useful as a general “FYI”. If you’re unsure, talk to a coach or HR-trusted advisor first.

Will medication make me a better developer?

For some adults with ADHD, stimulant or non-stimulant medication meaningfully reduces the friction of getting started, sitting through meetings, and tolerating boring tasks. It doesn’t make you smarter or more creative. It also has side effects, and finding the right medication and dose takes months of titration with a psychiatrist. It’s a real tool, not a magic upgrade.

What about going freelance or starting a company?

Tempting and often viable for ADHD adults — Wiklund and colleagues (2017) document the link between ADHD traits and entrepreneurial preference. The trade-off: freelancing/founding removes the structure that exhausts you and adds the structure you have to invent yourself (taxes, sales, admin). For some of us that’s a net win; for others it just shifts the burnout location. Try a side project before quitting.

Is remote work always better for ADHD developers?

Mostly yes for sensory load and autonomy, but not always for accountability. Some ADHD brains rely on the implicit body-doubling of an office to actually start working. If full-remote feels isolating or you can’t get going, try hybrid, a co-working space, or even a regular video call with another ADHD friend doing their own work in parallel.

In short

Tech is one of the friendlier industries for an ADHD brain — but “friendlier” doesn’t mean “frictionless”. The job’s strengths (hyperfocus, novelty, pattern matching) line up with ours; the job’s modern process layer (meetings, sprints, reviews, channels) doesn’t. The win isn’t to fix yourself. It’s to engineer your work — block deep time, batch meetings, externalize memory, right-size commitments — so the parts that play to your brain get more space, and the parts that drain it get smaller.

Gentle tools, not productivity gurus. DopaHop is free on Google Play, and Hop is always there — even if you come back after a rough sprint.

This article is informational and does not replace the advice of a qualified medical or mental health professional. For diagnosis, treatment or emergencies, contact a qualified professional. In a medical emergency call 999 (UK) or 911 (US). For mental-health crisis support: 988 (US) or 116 123 (Samaritans, UK & Ireland).