Practicing for Interviews When Interviews Scare You

I have shipped production apps, run research programs with hundreds of participants, and built design systems that outlasted my tenure. I also find interviews genuinely hard. Not paralyzing, but hard. For a long time I treated those two things as a contradiction. One of them had to be wrong. Eventually I stopped trying to resolve the contradiction and started treating interviews as a skill with its own learning curve, separate from the work.

That reframe changed how I prepare.

Nerves are a bandwidth problem

Anxiety does not make you forget what you know. It makes what you know temporarily inaccessible. The working memory you need to construct a story in real time is exactly what stress contracts. So you reach for the story, find the entrance, and then lose the thread somewhere in the middle. This is not a competence failure. It is a retrieval failure under load.

The practical implication is that anything rehearsed to automaticity survives anxiety. Anything left to construction under pressure does not. This is why over-rehearsing the first ninety seconds of your intro is worth the time: not because the intro is the most important thing, but because when it comes out automatically, your nervous system has a moment to settle while you are already talking. The hard part of the interview is easier once you are through the first minute.

A small set of stories, prepared deeply

The instinct when preparing for interviews is to cover as much ground as possible. Prepare answers for fifty questions, review every project, make sure nothing catches you off guard. This is understandable and mostly counterproductive.

Breadth creates a preparation that lives in notes. Depth creates a preparation that lives in you. The goal is not to have an answer for every question. The goal is to have five or six stories that you know so well they bend to fit whatever question arrives.

I keep the set small on purpose. One story about a decision made under genuine constraint. One about a time I had to change direction based on evidence that contradicted my assumption. One about building something that had to survive beyond my involvement. A few more. Each one prepared not as a script but as a set of anchors: the core facts, the tradeoff, the outcome. From those anchors I can reconstruct the story under pressure without losing the shape of it.

The number that matters is not how many stories you have. It is how deep you can go on the ones you keep.

The gap between knowing and telling

There is a specific skill in delivering a story in two minutes that is entirely separate from knowing the story. I learned this by recording myself.

The first time I listened back I heard things I had not noticed while talking: sentences that trailed off, answers that ran four minutes when they needed to run ninety seconds, places where I buried the most interesting part under context the listener did not need. Knowing a project is not the same as being able to tell it cleanly under time pressure. The telling is its own practice.

The rule I follow now: every story I intend to tell in an interview, I say out loud at least ten times before the interview. Not in my head. Out loud, timed. Standing up helps. The point is to hear where the telling breaks, not to memorize a script. Scripts break under pressure. Practiced delivery adapts.

This feels excessive until the first time you sit in an interview and the story comes out clean without effort. That is what the reps produce. Not a performance. A skill that is available when you need it.

Treating it as a conversation between practitioners

The frame that helps me most is also the one that requires the most preparation to believe. Before any interview, I try to hold this: the panel is not administering a test. They are trying to figure out if we would work well together on hard problems. The conversation goes better when both sides are evaluating.

This reframe only works if you have actually done the preparation. If you have not prepared, the interview feels like a test because you are genuinely uncertain whether you can answer the questions. The reframe does not create confidence from nothing. It becomes available once preparation has created the conditions for it.

When I have done the work, the frame holds. I am curious about their product. I have questions about what is actually hard on their team. I am not performing someone who is qualified. I am a practitioner in a conversation with other practitioners about whether we have a problem worth solving together.

That is a different room to be in. Getting there reliably requires designing the reps that make it possible.

Confidence is downstream of reps

This is the thing I wish someone had told me earlier: you do not wait until you feel confident and then do the interview. You do the reps until the performance part gets small enough that confidence has room to exist.

The reps are specific. The intro, out loud, timed, until it is boring. The three hardest decisions from each project, stated cleanly without over-explaining. The whole delivery, recorded and reviewed at least once. The frame, practiced before the call.

None of this makes interviews feel easy. But it makes the anxiety a smaller portion of what is happening. The work is still there, in full. And the work was never the problem.