How to prepare for the YC interview

It is famously short, famously fast, and nothing like a pitch. You don't get to perform — you get interrupted. Preparation still works, but not the kind most founders do.

Prepare answers, not a pitch

The single most common preparation mistake is rehearsing a ten-minute narrative. The interview is commonly described as roughly ten minutes of rapid questions from several partners, who interrupt, change direction, and follow the thread that interests them. A narrative you've polished end-to-end gets derailed in the first thirty seconds, and then you're improvising while rattled — the worst of both worlds.

What survives that format is a stock of short, self-contained answers. Thirty of them, each landing in fifteen to thirty seconds. What do you make. Who uses it. How many. Growth rate. How you make money. Why you two. What's the hardest part. Why now. Who else is doing this. What did you learn from your last three users. The interview is a shuffle of that deck, and your job is that any card can come up and you produce the answer without a run-up.

One sentence first, then the detail

Train every answer to open with a single declarative sentence that would satisfy someone who wanted nothing else. "Eleven thousand dollars a month, growing about twenty percent month over month for five months." Then stop. If they want the texture, they'll ask, and you've earned the follow-up. Founders who bury the answer in setup — "so the way our pricing works is complicated, there are two tiers…" — get cut off mid-setup, and the partners have learned nothing except that you can't be concise.

This is a memorization problem, not a personality problem. The one-sentence version of each answer should be verbatim-solid, because that's the part you'll produce under adrenaline. The elaboration can be gist.

Your numbers have to be reflexive

Nothing costs more credibility than fumbling your own metrics. Revenue, growth rate, active users, retention, burn, runway, CAC if you have it — these need to be automatic, in the same way your phone number is automatic. Not "roughly", not "let me think". And know the shape behind them: if you say twenty percent month over month, expect "from what to what?" immediately.

Drill them separately from everything else, and drill them out of order. A number you can only reach by walking through your dashboard in your head is a number you will lose the moment someone interrupts you.

Why re-reading your application does nothing

Most founders prepare by re-reading their application and their notes. It feels productive and it is close to useless. In the classic testing-effect studies (Roediger & Karpicke), material people kept retrieving was still near 80% a week later; material they merely restudied after one success fell to the mid-30s. Pulling an answer out of your head is what builds the memory. Reading it builds the feeling of knowing it, which is exactly the illusion that collapses when a partner interrupts.

The method proven on freshly-written material is diminishing cues (Fiechter & Benjamin, 2018): recall with the full answer in front of you, then with words blanked, then from first letters, then from nothing. Each rung forces real retrieval while keeping enough success that the practice sticks.

Rehearse being interrupted

This is the part almost nobody practises, and it's the part the interview is made of. Pressure eats working memory unless the pressure is familiar — Beilock & Carr (2001) showed that practising under even mild evaluative stress inoculates against choking, because the arousal becomes a known quantity rather than a novel threat.

So build the interruption into the drill. Have someone fire questions in random order, cut you off at fifteen seconds, and follow up on the weakest thing you said. Or let an AI do it: LobsterClass's roleplay plays a skeptical partner, interrupts, pushes on vague answers and grades what you actually said against what you meant to say. The first time you get cut off mid-sentence should not be in the room.

Two founders, one answer

If you're interviewing as a pair, decide in advance who owns which questions, and practise the handoff. Partners notice when co-founders talk over each other, contradict a number, or both defer. Agree the split — one owns product and users, the other owns metrics and market, either can take "why you" — and rehearse it together at least twice out loud. Then rehearse breaking it, because they will ask the other person on purpose.

The night before

Don't cram. The spacing literature is unambiguous that short repeated sessions beat one long one, with the optimal gap between sessions running roughly 10–30% of the time you have left (Cepeda et al., 2008). And sleep is doing real work: in one study (Mazza et al., 2016), the same two sessions split across a night's sleep took about half the relearning effort and held up far better later. Last real session the evening before, then sleep. In the morning, warm up on your opening sentences and your numbers only — nothing new.

You cannot make the interview slower. You can make it so that whatever they ask, the first sentence is already there.