Skip to main content

Search...

Autism in Software Testing: Where the Advantage Is Real

Autism in software testing: for Robert, any deviation from a learned pattern sets off an alarm. An autistic tester on finding bugs without searching.

• • Updated: • 11 min read
Cover of the expert talk on 'Autism in Software Testing: Where the Advantage Is Real' with Robert and Richard Seidl.

Autism spectrum disorder is a medical diagnosis; medicine describes it on three levels: biological (genes, brain, metabolism), cognitive (information processing) and behavioral (social interaction, communication, need for routine). Robert, a software tester with autism, explains what it means for him in testing: a sharper eye for detail, analytical thinking and a memory that precisely recalls connections and earlier bugs.

Key Takeaways

  • Robert notices changes instead of filtering them out. That costs him energy, but bugs are often exactly that kind of deviation, and they jump out at him where others look past them.
  • Burnout as the trail to a diagnosis: only after his third burnout as an adult did autism emerge, in hindsight, as a possible explanation for Robert, because social interaction, surprises and quick changes cost him far more energy than they cost his colleagues.
  • Direct, unfiltered feedback is an asset in software testing: feedback that isn’t sugarcoated carries the full information, while socially cushioned feedback hides problems.
  • “Autistic people don’t search for bugs, they find them”: a common saying, and Robert confirms it for himself. He spots typos without checking every word, because an alarm goes off the moment a learned pattern is broken.
  • The few colleagues Robert works closely with know about his autism. What he explained to them is mainly the social side: direct wording, hardly any small talk, the occasional joke he doesn’t get. Without that context it reads as rejection, when, as he puts it, he simply works differently.

Autism in Software Testing: How Robert Spots Bugs

A strong eye for detail and pattern recognition let Robert find bugs without going looking for them. For him, the flip side is a lower tolerance for stress, and the few colleagues he works closely with know about his autism.

Bugs stand out to Robert faster than to others; he names that as the first of his two strengths in testing. A typo in a document catches his eye without him checking word by word. He flies through the text, and certain things simply leap out at him.

Patterns are what make this work. Language, code and XML all follow clear rules. When something departs from a pattern you have learned, an alarm goes off right away. That only works where there is experience to draw on, in a language you know well, for example.

“It’s often said that autistic people don’t search for bugs, they find them. And in testing, that often helps. And that is definitely the case for me.”

(Robert)

The way autistic people deal with change cuts both ways, too. Many people cope with change well because they filter most of it out. Someone who filters out very little notices almost every deviation. That takes energy, but bugs are usually exactly that kind of deviation, so they stand out immediately.

Autism on Three Levels

Autism is a medical diagnosis, officially called autism spectrum disorder. The word “disorder” is contested, but it is the term medicine uses. The spectrum is wide, and no two autistic people are alike.

Medicine describes autism on three levels. The first is biological: genes, mirror neurons, metabolism. Researchers assume the cause lies mainly in the genes, but so far they haven’t been able to name a specific gene.

The second level is cognitive and concerns how the brain processes information. Autistic brains pay more attention to detail and tend to work bottom-up, from the details to the big picture, rather than top-down. That is why autistic people often get lost in details.

Executive functions belong to this level as well. Adjusting to an environment that keeps changing is hard. A few slow changes are much easier to handle than fast ones.

The third level is behavior, and this is where autism is most visible: social interaction, communication and repetitive patterns. Reading other people intuitively is difficult. Communication is mainly about passing on information, less about small talk, jokes or nonverbal cues.

Why Robert’s Diagnosis Came Late

For a long time, Robert didn’t realize that he perceives the world differently. Because his autism makes it hard to put himself in someone else’s shoes, he intuitively assumed that everyone experiences things the way he does.

For Robert, the first sign was mental strain. Even as a teenager he had more problems than his friends, there was no explanation for them, and the hope that “it’ll get better with age” didn’t pan out. It got worse instead. Only after his third burnout as an adult did autism come into view as an explanation.

Only once you understand what autism is can you recognize your own differences. That nonverbal communication comes easily to others. That a conversation tires them out less. That a sudden change costs them less energy.

A specialist told Robert that the first step is a diagnosis. Only then can the right support follow, because nobody gets meaningful help for autism without one. He found out for himself how limited diagnostic capacity is: confirmation took around two years instead of two weeks. For someone who struggles with uncertainty, that is two years in limbo.

Lower Stress Tolerance Shapes the Workday

Robert’s stress tolerance is lower than his colleagues’; he sees that clearly now that he understands his autism. Surprises, quick switches and social contact all cost him more energy, and he needs more breaks.

Without those breaks, things tip over: he gets irritable and extremely nervous, and the people around him feel it too. Nobody enjoys working with someone who is on edge.

Multitasking is especially hard. Several systems at once, one customer after another without a pause, and social interaction on top of it all: that quickly hits the limit. The more topics run in parallel, the faster the energy drains.

Robert grades social interaction by how much it drains him. A scheduled one-on-one with a known agenda is quite manageable for him. Every unfamiliar person, unfamiliar topic and unplanned situation adds to the load. In one meeting his energy is gone after ten minutes; in another his battery lasts an hour and a half.

Robert’s ideal is a small, scheduled meeting with an agenda known in advance. He knows reality rarely looks like that. But it decides how quickly his battery runs down.

Deep System Knowledge Speeds Up Debugging

When analyzing a problem, it pays to know one system in depth. The more background knowledge you have stored about a system, the faster you get to the likely causes of a bug.

The cause of a bug is rarely where the bug shows up. Everyone finds the error in the obvious place. The hard ones hide somewhere else, and the clearer your picture of the dependencies, the shorter the search.

Ownership is a second lever. Instead of assuming the bug is in your own area, start by asking: is this even ours? If the cause lies elsewhere, hand the bug over. Every minute spent digging through someone else’s code is time badly spent.

Memory helps as well. An error message from years ago, long since archived, can be pulled back up when a similar problem returns.

Direct Feedback Can Be an Asset in Testing

Robert calls it a double-edged sword: in social interaction he often lacks empathy, but his feedback is, as a rule, very honest and open. Where others sugarcoat criticism, his comes through unfiltered.

The difference is concrete. If something only half works, one person says “you did a great job”, the other says “that’s not good enough”. When the goal is to make the software as good as possible, the honest version helps more.

That directness needs context, though. The other person has to know that the bluntness is about the work and not a rejection of them. Otherwise misunderstandings follow.

Assign Tasks by Strengths

Teams get the most out of people when they build tasks around strengths rather than just managing deficits. Someone who presents poorly shouldn’t be pushed into presenting, because arguments that are delivered weakly land weakly.

A realistic model splits the roles. One person writes a precise document with the arguments, and a stronger communicator presents them. The arguments carry more weight, and the whole team benefits.

A fallacy Robert runs into often: if someone can’t do one thing, they can’t do the other either. What matters to him is that he does some things less well, but others perhaps even better, and that the team makes use of exactly that.

What Robert Wants from His Team

Acceptance matters most to him: being different without “different” being taken to mean “worse”. Pity doesn’t buy him much, he says.

To his close working group he explained his social behavior in particular, because that is what colleagues notice most. Direct wording, little small talk, the occasional joke he doesn’t get: anyone who can put this in context won’t take it as a personal rejection.

He keeps the information to a manageable amount. Nobody on the team needs to become an autism expert, and too much explanation tends to overwhelm. It is enough for him that the four or five people he works with regularly know about his different social behavior and read it correctly.

For him, tolerance and making use of strengths go together: the team should value and use what he does especially well, and be patient where he is not at his best socially.

Frequently Asked Questions

Can repeated bouts of burnout in adults be a sign of autism?

For Robert, they were. After his third burnout as an adult, he knew this was not normal, and in hindsight autism emerged as a possible explanation: social interaction, surprises and quick changes cost him far more energy than they cost his colleagues, and without enough breaks he quickly becomes irritable and nervous. Even as a teenager he had more psychological problems than his peers, with no explanation, and the hope that things would get better with age did not pan out. The push came from a specialist who told him: the first step is a diagnosis.

Why do autistic people find it difficult to cope with rapid changes?

This is related to cognitive processes, particularly executive functions. Autistic brains tend to work from the bottom up, from details to the big picture, rather than the other way around. As a result, adapting to constantly changing environments requires more effort. Few and slow changes are easier to process than many rapid ones, and surprises consume additional energy.

What are Robert’s strengths as a tester with autism?

Two, he says. First, he notices bugs faster: typos in a document jump out at him without him checking every word. Behind that are patterns. Language, code or XML follow clear rules, and any deviation sets off an alarm right away. He doesn’t search for bugs that way, he finds them. That works where he has experience with the pattern. Second, analysis: because he thinks his way deep into a system and has stored a lot of background knowledge, he gets to the likely causes of a bug faster.

How stressful are meetings for a colleague with autism like Robert?

That depends on the format, Robert says. A scheduled one-on-one meeting with a known agenda is quite manageable for him. The more unfamiliar people, unfamiliar topics and unplanned situations are added, the harder it gets: in one meeting his energy is gone after ten minutes; in another his battery lasts an hour and a half. Small groups and an agenda known in advance help him in practice.

Why is the root cause of an error rarely where it becomes visible?

Everyone finds the error in the obvious place. The tricky errors lie elsewhere, which is why in-depth knowledge of a specific system shortens the search: Those who have a clear understanding of the dependencies in their minds can identify potential causes more quickly. A second factor is responsibility. The first question should be whether the bug even lies within one’s own area of responsibility, because searching through someone else’s code is a waste of time.

Should critical feedback in testing be socially softened?

No, if the goal is to maximize software improvement. Socially softened feedback obscures problems; direct feedback provides complete information. The difference is concrete: If something works only halfway, “that’s not enough” is more helpful than “you did a great job.” This directness, however, needs to be put into context so that the other person relates it to the matter at hand and doesn’t interpret it as a rejection of them as a person.

Should someone who is reluctant to present still be forced to give a presentation?

No. Weakly presented arguments come across as weak, which serves no one’s interests. A realistic approach separates the roles: one person creates the precise document with the arguments, while someone with stronger communication skills presents them. From his own experience, Robert knows the fallacy that if someone can’t do one thing, they can’t do the other either. What matters to him is that he does some things less well, but others perhaps even better.

Does an entire team need to be educated about autism?

No, the information can be provided in measured doses. No one needs to become an autism expert; too much explanation tends to be overwhelming. It’s enough for the few people in the immediate work circle to be aware of the different social behaviors: direct expression, little small talk, and sometimes a joke that isn’t understood. Those who can put this into context won’t interpret it as personal rejection. Acceptance is more important than pity, without equating “different” with “worse.”

Share this page

Related Posts