Stuttering in a phone interview: what actually helps
Someone in a stuttering forum said this recently, and I haven't stopped thinking about it:
If you've ever been screened out of a job on delivery — while being entirely capable of doing the actual work — you know that specific flavour of unfairness. It isn't that you couldn't do it. It's that ten minutes on a phone decided you couldn't, and there was no appeal.
Phone screens are, structurally, close to the worst possible format for someone who stutters. No face. No body language. No whiteboard, no portfolio, nothing to point at. Just a voice, being judged, on a compressed line, by someone with a checklist and eleven more calls today. Every tool you've built up to communicate well gets stripped out, and the one channel you're least in control of is the only channel left.
So here's what actually helps. Not "relax" — real things.
1. Decide about disclosure ahead of time, not mid-block
There's no universal right answer here, and anyone who tells you there is hasn't thought about it hard enough. But there is a wrong way to handle it, which is: deciding while it's happening. Panicking mid-call about whether to explain yourself, spending working memory on that instead of on the answer.
The options, honestly:
Say it up front
Something short and unapologetic at the top: "Quick heads up — I stutter, so you might hear some pauses. Just let me finish, I'll get there." That's it. No apology, no explanation of the neurology.
What it buys you: the interviewer stops doing the private arithmetic ("is the line frozen? is he nervous? is something wrong?") and starts listening to your answers. It also removes the thing that's actually eating your bandwidth — managing their confusion in real time. Many people find they stutter less after saying it, precisely because the anticipatory load drops.
What it costs: you've raised it. Some interviewers handle that badly. That's information about them, but it's information you receive after the fact.
Don't mention it
Perfectly legitimate. You don't owe anyone a disclosure about how you talk, and plenty of people would rather be judged on the answers without a frame around them.
What it costs: the bandwidth. You're now managing their perception silently, which is the tax from the last post.
Put it in writing beforehand
The underused option. A line in the email confirming the call: "Looking forward to it — one note, I stutter, so please just give me a beat to finish my thoughts." Written disclosure means it's handled before the call starts, you don't spend a second of the actual call on it, and you never have to say it out loud under pressure.
Pick one. Write it down. Don't renegotiate it at 2:04pm.
2. Script the openings, not the answers
Full scripts collapse the moment the interviewer goes off-menu, and then you're improvising while your plan is on fire. But the first few words of each likely answer? Absolutely script those. Starting is the hardest part; a running start gets you past it.
Have openings ready for the four things you'll definitely be asked: tell me about yourself, why this role, walk me through your experience with X, do you have questions for us.
3. Stop substituting — it's making the interview worse
Word substitution feels like a coping tool. In an interview it's actively hurting you.
When you swap the precise word for the sayable one, you're not just changing the sound — you're downgrading your answer. You say "worked on" instead of "architected." You say "a lot" instead of the number. You give the vaguer example because the good one starts with a hard sound. The interviewer doesn't hear a stutter you dodged. They hear a weaker candidate.
Say the real word. Block on it if you block on it. A three-second pause on the word "architected" reads as thinking. "Worked on" reads as junior.
4. Practise the format, not just the answers
Most interview prep is content prep — rehearsing what you'll say. But the thing that gets you isn't content. It's the call: the ring you didn't schedule, the silence after an answer that you feel compelled to fill, the follow-up you didn't see coming.
You can't rehearse that alone in a room. Practising your answers in your head is practising the easy version — you're calm, you're in control, there's no one there. The gap between that and a live phone screen is exactly where things fall apart.
5. Ask for a different format when you can
Worth knowing: in the US, stuttering is a disability under the ADA, and asking for a reasonable accommodation in a hiring process is legal and normal. That can be a video call instead of phone, written questions in advance, or extra time.
Whether to ask is a genuinely personal call — some people find it levels the field, others don't want the frame. But know that it exists, so it's a choice you're making rather than an option you didn't have. (I'm not a lawyer and this isn't legal advice — just something a lot of people don't realise is on the table.)
The unfair part
None of this makes it fair. It is genuinely unjust that a hiring process can filter for smooth delivery and call it filtering for competence. Plenty of people who stutter are better at the actual job than the fluent candidate who got it, and the phone screen never finds that out.
What you can control is a narrower thing: showing up to the format having practised the format. Not being smooth. Just not being ambushed.
Practise the phone screen, not the answers.
Pickup Calls rings your real phone at a moment you didn't pick — including an interviewer who asks follow-ups and leaves silences you have to fill. Tell us what you actually do, and the call is built around your field.
Get your first call — freeBuilt by someone who stutters. 5 minutes max. Pause anytime.