Interviews

Interview preparation: stories, structure and questions

Interview performance is mostly preparation you did in advance. Six well-built stories cover the majority of behavioural questions you will ever be asked.

Build six stories, not thirty answers

Write each in STAR form — Situation, Task, Action, Result — and keep each to about 90 seconds spoken. Cover: a delivered achievement, a failure, a conflict, a leadership moment, an ambiguous problem, and a time you changed your mind.

The result sentence is the part people skip. Always end with what changed, ideally with a number and what you took from it.

The standard questions

A STAR story, weak vs. stronger

Weak: "We had a really tough project at my last job, deadlines kept moving, and it was stressful, but we managed to get it done and the client was happy." Stronger: "A key client's launch date moved up by three weeks (Situation). I was responsible for coordinating design, engineering and legal review (Task). I restructured the review process into parallel tracks instead of sequential sign-off and flagged the two riskiest items to leadership on day one (Action). We shipped four days early, and the client renewed a 12-month contract shortly after (Result)."

The weak version has all four STAR elements buried inside a mood description. The stronger version separates them clearly and ends on a concrete, business-relevant outcome rather than a general feeling of relief.

Salary conversations

• Research a range for the role, level and city before the first call.
• If asked early, give a researched range and say it is flexible depending on total package.
• Never anchor on your current salary; anchor on the market rate for the role.
• Negotiate after the offer, once, with a specific number and a reason.

Questions worth asking

• What does success in this role look like after six months?
• What is the biggest obstacle the person in this role will hit?
• How are decisions made when the team disagrees?
• Why is the role open?
• What is the next step and the timeline?

Preparing for panel and technical rounds

• Ask the recruiter in advance who will be in the room and what format to expect — a panel, a case study, a live technical exercise.
• For panel interviews, address the person who asked the question first, then briefly bring in eye contact with the rest of the panel during the answer.
• For technical or case rounds, practise thinking out loud beforehand; silent problem-solving reads as disengagement even when the reasoning is sound.
• Bring one clarifying question to any case or technical prompt before diving in — it signals structured thinking and often surfaces a constraint you would have missed.
• If a panel member seems unconvinced by an answer, offer to go deeper or give a second example rather than moving on and hoping it was enough.

Handling questions you did not prepare for

1. Pause deliberately for a few seconds rather than filling the silence with filler words — a short pause reads as thoughtful, not weak.
2. Restate the question in your own words if it is broad; this buys thinking time and confirms you understood it correctly.
3. If you genuinely lack the experience asked about, say so plainly and pivot to the closest related situation you do have.
4. For estimation or case-style questions, narrate your reasoning out loud — interviewers are usually scoring the process, not just the final number.
5. If you realise mid-answer that you are off track, say so and redirect rather than continuing down an answer you know is weak.

After the interview

Send a short thank-you within 24 hours that references one specific point from the conversation and adds anything you wish you had said. It is rare enough to be remembered.

A weak vs. stronger answer to "why are you leaving"

Weak: My manager and I didn't really get along, and honestly the whole team culture was pretty toxic, so I just need to get out. Stronger: I've grown as far as I can in my current scope, and I'm looking for a role with more ownership over strategy rather than execution — which is what drew me to this posting's emphasis on cross-team planning.

The weak answer may be true, but it puts the interviewer in the position of wondering whether you will describe them the same way in a year. The stronger answer stays honest about wanting change while keeping the focus on what you are moving toward, not what you are escaping.

Remote and virtual interview specifics

• Test camera, microphone and lighting at least thirty minutes before, not five — early problems have time to be fixed.
• Keep a printed or second-screen copy of your key stories and the job posting nearby; glancing at notes briefly is normal on video in a way it is not in person.
• Look at the camera lens, not the screen, during your main answers — it is the closest virtual equivalent of eye contact.
• Have a backup plan for connectivity (phone hotspot, a neighbouring quiet space) and mention it upfront if a call ever drops.

Group and case interviews

Group interviews test collaboration under mild competition, and the common mistake is either dominating the conversation or staying silent to avoid conflict. A more reliable approach is to actively build on at least one other candidate's point by name before adding your own, which demonstrates listening as much as contribution. In case interviews, state your assumptions out loud before calculating anything — interviewers are usually more interested in whether your assumptions are reasonable than whether your final number is exactly right.

Recovering from a stumble mid-interview

Nearly every candidate has one moment in an interview where an answer goes worse than planned. What separates a recoverable stumble from a lasting one is usually the next thirty seconds: acknowledge briefly that you want to add to the previous answer, give the sharper version, and move on without dwelling on the mistake. Interviewers remember composure under a wobble more than they remember the wobble itself.