Interview Tips for Autistic Adults: Prepare Stories, Not Scripts
Most interview advice skips the difficult part.
It tells you to “be confident”, “prepare examples”, “use the STAR method”, and “just be yourself”. Which is lovely advice in the same way that “simply relax” is lovely advice when your nervous system is quietly trying to climb out of a window.
For autistic adults, and honestly for plenty of anxious, ADHD, burned-out, or those with busy minds, interviews are not just conversations. They are horribly vague social assessments with unclear rules, social performance pressure, memory pressure, performance pressure, and a decent chance that someone will ask a question in a way you didn’t prepare for.
The goal isn’t to become magically confident. The goal is to reduce the mental load (because that is at a premium under stress, and that you can do).
Good prep should help you walk in knowing which examples you’re likely to use, why they matter, and how to adapt them when the question shifts slightly. You don’t need a perfect script for every possible question. You need a small set of useful stories you can actually retrieve under pressure.
The standard approach gives you a pile of memorised material and hopes your brain files and retrieves it neatly on demand. Brave. The other gives you a simple method for choosing and using the right evidence in the moment.
For many autistic people, that difference matters a lot.
The problem isn’t just confidence
A lot of interview advice treats confidence as the main obstacle.
Sometimes it is part of it. If you’ve had enough bad interviews, confusing feedback, ghosting and “you were very strong but...” emails, confidence is not going to be sitting there untouched and radiant.
But the harder (and more real) problem may be uncertainty.
What exactly are they asking? How much detail do they want? Are they judging the answer, the tone, the eye contact, the pause, the “culture fit”, or some crazed mixture of all of it? Should you give the direct answer or explain the context properly first? How do you know when to stop talking? And why does “tell us a bit about yourself” manage to ask one thing, but actually be asking for a totally unrelated answer?
This is why “just practise common questions” often doesn’t help enough. It gives you a pile of possible answers but no method for choosing between them in the moment. It can even make things worse, because now you have numerous half-prepared responses floating around your head that look like my badly managed, endless browser tabs.
Teamwork. Leadership. Resilience. Conflict. Adaptability. Initiative. Customer focus. Stakeholder management, because apparently someone had to invent more “crucial topics”.
Better to prepare fewer things, but prepare them well.
Start with the job advert, not a giant question list
Instead of beginning with lists of common interview questions, start with the job advert.
Job adverts are not always well-written. Some read like they’re hiring one person to do three jobs, own a crystal ball, and also “thrive in ambiguity” (which is often corporate for “we haven’t organised this properly”). Still, they’re usually the best clue you have about what the role actually needs.
Read the advert and look for the action words: communicate, organise, improve, deliver, support, analyse, prioritise, solve, coordinate, adapt. Group those into two or three plain-language themes.
For example:
- They need someone who can get useful work done reliably.
- They need someone who can fix or improve things without making new problems.
- They need someone who can communicate clearly with other people.
Or run it through a LLM and ask for the major themes the job advert is looking for.
That’s already more useful than preparing for “an interview” in the abstract. You’re no longer preparing for all possible questions in existence. You’re preparing for this role, which is a much smaller and more manageable target.
Ask what they’re afraid of
This sounds slightly dark but it’s genuinely useful (and for me, empowering).
Once you have the main themes, ask: what are they scared will happen if they hire the wrong person?
If the advert keeps mentioning deadlines, prioritising, and delivery, they may be worried about someone who drifts or needs constant chasing. If it keeps mentioning customers and complaints, they may be worried about someone who makes tense situations worse. If it keeps mentioning accuracy and documentation, they may be worried about things falling through gaps.
You can’t mind-read them perfectly. Interviewers are people, which means they are walking bundles of assumptions, preferences, and well, organisational panic. But you can make a reasonable guess about what they need reassurance on, and then choose stories that actually provide it.
“I’m organised” is a claim. This is stronger:
“I noticed the handover process was unclear, so I created a checklist and the number of missed tasks dropped noticeably.”
That’s evidence. It gives them something to score. It also gives them something to picture. Rather than merely asserting a trait, you’re showing how it appears in real work.
Prepare 3 to 5 stories
For most interviews, you don’t need twenty examples. Twenty examples can quickly become a tiny private database of dread (or if you are me, avoidance).
A sensible starting point is 3 core stories and 2 backups. Your core stories should cover different themes:
One problem-solving story. A time you fixed, improved, clarified, or prevented something getting worse.
One people or communication story. A time you explained something clearly, handled disagreement, supported someone, or adapted how you communicated.
One delivery or adaptability story. A time you got something done despite constraints, deadlines, uncertainty, or things changing halfway through.
Then add one or two backups. A mistake-and-learning story is often worth having, because questions about failure or feedback are common and genuinely irritating if you haven’t prepared one. Nobody enjoys being asked to produce a neat little failure story on command, especially when the honest answer might be: “I have several, but none I particularly want to perform for strangers under thus brutal fluorescent lighting.”
Still. Worth having one ready.
These stories don’t need to be dramatic. A useful example might be: you made a process clearer, helped a customer understand what was happening, spotted a repeated mistake, organised messy information, learned something quickly, or communicated a problem before it got worse.
Small, specific, and real is almost always better than grand, vague, and suspiciously heroic. A lot of people dismiss their own examples too quickly because they feel like “just doing the job.” But interviews are often about showing how you do the job, not proving you once delivered a TED talk, while personally saving a department from collapse.
A clear, modest example can be very strong if it shows the right thing.
Use a simple structure
You’ve probably seen STAR recommended: Situation, Task, Action, Result. It’s fine. It can help. But under pressure, four moving parts can feel like extra admin your brain didn’t request.
A simpler version is PAR:
Problem. Action. Result.
What was the problem? What did you do? What changed?
That’s usually enough to keep an answer clear. (You might also see CAR: Context, Action, Result. Same idea, different label. The label doesn’t matter much.)
For example:
Problem: The weekly report was often delayed because information came from several people and nobody had a clear view of what was missing.
Action: I built a simple tracker, listed who owned each section, and started chasing missing information earlier in the week.
Result: The report started going out on time, and the last-minute scramble mostly stopped.
That’s a clear answer. It gives context, action, and outcome without turning the interview into a memory test about which letter of STAR you’re currently in (been there).
STAR can still be useful for writing notes beforehand, because it helps you check you haven’t forgotten the result, which is a common weak spot. But in the room, PAR is easier to hold onto.
Problem. Action. Result. There’s the issue. There’s what I did. There’s why it mattered.
Practise angles, not scripts
This is the part most interview prep misses.
Once you have your stories, don’t just practise them as fixed speeches. Practise using the same story from different angles.
A story about improving a messy process could answer: “tell me about a time you solved a problem,” “tell me about a time you used initiative,” “tell me about a time you organised information,” or “tell me about a time you worked under pressure.” The story stays the same. The emphasis shifts.
For the problem-solving version, you focus on spotting the issue and working out what needed to change. For the organisation version, you focus on the system you created. For the pressure version, you focus on the deadline and how you prioritised.
This is much more useful than memorising one fixed answer, because interviewers rarely ask the exact question you prepared for. They ask something adjacent. Similar shape, different hat.
For autistic candidates, this can be especially helpful because it avoids the two bad options: total improvisation (which can feel awful) and rigid scripting (which breaks the moment the question is phrased differently). Flexible stories sit in between. You have structure, but you’re not trapped by it.
You’re not trying to become a spontaneous interview guru. You’re trying to make the unpredictable part slightly less unpredictable.
Make your answer easy to score
Interviews often feel vague, but many interviewers are still scoring against some kind of criteria. So help them.
If the question is about teamwork, make the teamwork obvious. If it’s about problem-solving, make the problem and your specific action obvious. You can even name the skill if it feels natural: “This is probably a good example of prioritising under pressure” or “This shows how I handled a communication issue without letting it escalate.”
That might feel blunt, but it’s often useful. You’re pointing them toward the evidence rather than hoping they find it themselves. Subtlety is lovely in novels and unreliable in scoring grids.
Also: don’t spend too long on context. You don’t need to explain the entire history of the department, the software, the customer relationship, and the ancient politics of the spreadsheet, pacing can trip us up. Give enough background for the problem to make sense, then move to what you did.
Plan for blanking
Blanking doesn’t mean the interview is ruined. It means your brain has briefly refused service.
Have a few phrases ready:
- “Could I take a moment to think of the best example?”
- “Could you repeat the question?”
- “I want to choose the most relevant example for that.”
- “I’ll use something from my previous role.”
If you blank, return to the structure. What was a problem I handled? What did I do? What changed? You don’t need the perfect example. You need a relevant one you can explain clearly.
The search for the perfect example can become its own trap as well. You can sit there mentally rummaging through every job, project, and awkward workplace situation you’ve ever been in while the silence slowly inflates in the room. A decent, clear answer is almost always better than an extended internal search for the ideal one.
And if you need to pause: pause. It will feel much longer from the inside than it looks from the outside. A few seconds of genuine thinking is not a disaster. It may even make you look thoughtful, which is a rare case of anxiety accidentally working for you.
Don’t turn prep into masking homework
There’s a difference between preparing well and performing a version of yourself designed to survive someone else’s social expectations.
Some masking may happen (thats a different, complicated topic). Interviews are artificial situations and bias exists. But the point of preparation should not be to make you seem non-autistic. And the reason for that is, it takes away your limited under pressure resources from where you should be focusing: communicating your evidence clearly enough that the interviewer can assess whether you can actually do the job.
That’s a different goal.
The advice to “be confident,” “make eye contact,” “mirror their energy,” and “sound enthusiastic” is not useless, but it teaches performance before method. For autistic people, useful preparation should make the task clearer, not add a layer of social nonsense on top of everything else already being managed.
“Shall I also levitate gently above the chair?” is, unfortunately, how some interview advice lands.
Better questions to ask during prep:
- What are they likely to ask?
- What evidence do I have?
- How do I explain it clearly?
- What do I do if I need more time?
- Where are my genuine gaps?
Those are more useful than “how do I seem more confident?”
Reasonable adjustments may help
This piece is mainly about preparation, but adjustments are worth knowing about.
Depending on the role and the process (and the employer), you may be able to ask about: the interview format, who will be present, whether questions can be provided in writing in advance, whether notes are allowed, whether extra processing time is possible, or whether a remote format would work better for you.
Disclosure is personal and context-dependent. Some people prefer to disclose early and ask for what they need. Some prefer not to, particularly if they’re worried about bias (a very real concern in a lot of cases). Some decide case by case. There’s no single correct answer.
The preparation method helps either way, because it focuses on what you can control: choosing the right stories, practising them flexibly, and reducing the number of live decisions you need to make in the room.
It won’t remove every barrier. It won’t make every interviewer fair or competent. But it can make the process less chaotic, and sometimes that’s a decent improvement.
A quick pre-interview checklist
- What are the 2 or 3 main themes in the job advert?
- What are they likely to worry about in a bad hire?
- Which 3 stories best show you can do the role?
- What are your 2 backup stories?
- What’s the Problem, Action, and Result for each one?
- Which questions could each story answer?
- What will you say if you need a moment to think?
- What questions will you ask them?
- What will you do afterwards to chill?
That last one matters. Interviews take tonnes energy. Planning recovery time is not indulgent. If you know interviews drain you, don’t treat the aftermath as an optional detail. Have something gentle lined up. A walk, food, quiet, no immediate post-match analysis with your inner tribunal if you can possibly avoid it.
You can review it later. You don’t have to dissect your own performance while your nervous system is still red hot.
The actual point
The point isn’t to become brilliant at interviews in some shiny, artificial way.
It’s to reduce chaos.
Start with the job advert. Pull out the main themes. Choose 3 to 5 relevant stories. Structure them simply. Practise using them from different angles. Have a plan for blanking. Give the interviewer clear evidence they can actually score.
That’s a more coherent method than “be confident and use STAR.” It’s also considerably less likely to fall apart the moment someone asks a question you didn’t predict.
The aim isn’t to perform confidence. It’s to go in with a method that still works when the room, the wording, the nerves, and the social fog all start doing their little dance.
Want help choosing your stories?
Interview Decoded helps with the part most interview advice skips: working out which stories to actually prepare for a specific role.
Paste in the job advert and your CV or rough notes, and it builds a focused first-pass prep pack with your strongest stories, likely questions, which story fits which question, and any gaps worth noting.