Interview prep that actually lowers nerves
Build a notes bank, practise answers out loud, take think-time, and treat cases as conversations — not recitations from a framework book.
Most interview advice stops at "research the company and practise STAR." That is necessary. It is not what drops heart rate in the first two minutes of a live round. Candidates who convert screens into offers usually share one habit: they keep preparing until the questions feel familiar enough that nerves no longer steal working memory.
That does not mean memorising scripts. It means a personal notes database, verbal reps, and a plan for the first sixty seconds of every prompt — especially on video, where you can glance at a page without looking lost.
Build a notes bank before you need it
Open a doc (or Interview notes in DocuResume) and dump stories while they are still vivid: conflict, failure, leadership, a tight deadline, a time you were stuck. Tag each story so a behavioural prompt can retrieve it in seconds. Link stories back to bullets on the CV you actually submitted — interviewers probe what they can see.
For online interviews, keep the bank on a second screen or printed page. Hide it for cold drills so you can still speak if the tab crashes. For in-person rounds, the bank is for rehearsal only — do not read in the room.
Prepared, not rehearsed
Over-rehearsed answers sound like they belong to someone else. Framework-heavy prep (MECE trees, "Cracking the PM Interview" chapter dumps, canned case courses) is useful until it becomes a mask. If every estimate starts with the same three buckets, interviewers hear a course, not you.
Introverts often need think-time more than extra talking points. Take a minute. Write the question. Restate it. Ask one clarifying question before you solve. Silence while you structure is cheaper than a confident wrong problem.
Cases: name the type before you calculate
Not every case is a market-size. Some are profit trees. Some are qualitative: why would customers choose X, what operational constraints matter, what would you check before recommending a rollout. If you treat a "how would you think about electrical plugs in a new market" prompt as a TAM slide, you will miss plugs, safety, retailers, and installers.
When you are stuck, say so and show the next test: "I do not know the attach rate — I would look at comparable SKUs and then sanity-check against store count." Honesty plus a path beats a fake number. Land a recommendation even if the math is rough — synthesis is the skill.
Fit, referrals, and standing out without gimmicks
Apply where you can explain the fit in one sentence that is true. Referrals help after you have applied (when the process requires it) and after a contact can speak to your work — not as a substitute for the posting.
Standing out is substance: a specific product observation, a numbered result, a question that could only come from reading the role. Gimmick openings and "I can do anything" blur you into the pile.
Speak the full answer. Then hide the notes.
Typing STAR in a doc is half the work. Say the answer out loud until you can hit roughly 60–90 seconds without reading. Then lock the notes and do a cold pass. If you only ever practise with the page open, the live round will feel like a different sport.
An AI voice interviewer can run follow-ups for a timed block (about 30 minutes is plenty) if you never let it write the answer for you. Use it as a hostile-but-fair interviewer, then debrief yourself. Product loop: practice sits, think-time, and story tags live on Interview Prep and in the practice hub.