Interview preparation that actually changes the outcome
Effective interview preparation is mostly retrieval practice, not reading. Build six to eight stories from your own experience in STAR form — situation, task, action, result — and rehearse them out loud until each runs about two minutes. Research the company's product, customers and recent announcements, prepare three specific questions of your own, and confirm the format of every round in advance so you practise the right thing.
How to do it
Confirm the format
Ask the recruiter what each round covers, who is in it, and how long it runs. Preparing for a system-design round that turns out to be a code review wastes the whole effort.
Build a story bank
Write six to eight STAR stories covering a shipped success, a failure you owned, a conflict you resolved, a deadline you saved, something you led, and something you learned fast.
Rehearse out loud
Speak each story to a timer. Two minutes is the target. Reading them silently gives no indication of how they sound, and the difference is immediately audible to an interviewer.
Research narrowly, not broadly
Know the product well enough to describe who pays for it and why, plus one recent launch or announcement. That beats memorising the About page.
Prepare your own three questions
Ask about how success is measured in the role, what the first ninety days look like, and something specific to the team's current work. Generic questions signal generic interest.
Follow up once, concretely
Send a short note within 24 hours referencing one specific thing discussed and adding anything you promised. One follow-up. Then wait for the timeline they gave you.
Why STAR works
Behavioural questions ask what you did, but untrained answers drift into what you believe. STAR forces the specifics an interviewer is actually assessing: the constraint you faced, your own contribution as distinct from the team's, and what changed as a result.
The Result is the part candidates most often omit, and the only part that demonstrates competence rather than participation. Give a number where you have one and an observable change where you do not.
Technical rounds
Interviewers are scoring your process at least as much as your answer. Narrate as you work: restate the problem, name your assumptions, outline an approach before writing code, and say what you would test.
Being stuck is normal and is not disqualifying. Being stuck in silence is, because it gives the interviewer nothing to evaluate and no opening to help.
Salary and the compensation question
When asked for expectations early, give a researched range and anchor it to the market and the scope of the role. In many US states the employer must disclose the posted range on request, and in several it must appear in the listing.
If you can defer without friction, do: "I'd rather understand the scope first — can you share the band for this level?" is a reasonable and common answer.
Remote and panel interviews
Test camera, microphone and screen sharing on the actual platform beforehand, and have a phone fallback ready. Sit with light in front of you, not behind.
In a panel, answer to the person who asked but include the room with your eyes. Note each interviewer's name and role as you are introduced — you will want them for the follow-up.