Most interview preparation is actually rehearsal in disguise. Candidates memorise answers to the questions they expect, practise responses in their heads, and then struggle when the interviewer takes the conversation in a different direction. Rehearsal creates rigidity. Genuine preparation builds flexibility: understanding the company well enough to discuss it naturally, knowing your own examples well enough to frame them differently for different questions, and arriving with a clear view of the role rather than a script.
This guide covers how to build that foundation at every stage, from phone screen to executive interview, including what each stage is actually testing, how to structure your examples, and what to do when things do not go as planned.
What Interviewers Are Actually Trying to Find Out
Every interview, regardless of format or seniority level, is answering three underlying questions:
- Can this person do the job? (skills and experience)
- Will this person do the job? (motivation and work ethic)
- Will this person fit here? (culture and collaboration)
The stage of the process determines which question gets the most attention.
Phone screen: A baseline filter. The goal is to confirm minimum requirements and that you are worth an in-person conversation. Energy, clarity, and not saying anything that eliminates you are the main objectives.
First round: Skills depth and role fit. Interviewers are primarily asking "can this person do the job?" STAR-structured behavioural examples are the main currency here.
Technical: Pure capability assessment. Thinking out loud matters as much as arriving at the correct solution.
Final round: A consensus exercise. Multiple stakeholders are checking for reasons to say no as much as reasons to say yes. The question shifts from "can they do the job?" to "will everyone be comfortable with this hire?"
Executive: A peer conversation. Senior interviewers are not assessing your competence at this stage; they assume it. They are evaluating presence, strategic clarity, and whether you think about problems the way they do. Candidates who prepare like they are being assessed rather than having a strategic discussion often underperform.
For a stage-specific preparation checklist tailored to your job title and company size, use the free Interview Preparation Checklist. It generates a personalised list of action items for your specific interview stage.
How to Research the Company Properly
Three levels of research separate candidates who have done the work from those who have done the minimum.
Surface level (every candidate does this)
Homepage, About page, recent press releases, LinkedIn company page. Necessary but not differentiating. If you are only at this level, you are at the same level as every other candidate who progressed from the CV screen.
Market level (most candidates skip this)
Competitor landscape, recent industry news, and analyst coverage if the company is public. For public companies, the last earnings call transcript and the key highlights of the most recent annual report contain more useful context than any press release. Knowing that the company missed revenue guidance by 7% last quarter, or that it is expanding into a new segment, gives you material for questions that most candidates will not have.
Signal level (almost no candidates reach this)
LinkedIn headcount trend over the past 12 months, Glassdoor review themes from recent leavers, executive hires and departures, product reviews on G2 or Capterra for SaaS businesses, and recent job postings. What a company is actively hiring for signals its strategic priorities more accurately than its public statements.
Researching a private startup with limited public data
Crunchbase for the funding timeline and investor list, LinkedIn for the founding team's backgrounds and headcount trajectory, Product Hunt for early product reception, and any available press coverage. Ask the recruiter directly: "Can you share any context on the company's current stage and growth trajectory?" Most will answer if asked professionally, and the candour of the response is informative either way.
The STAR Method: How to Use It Properly
STAR stands for Situation, Task, Action, Result. It is the standard structure for answering behavioural questions that begin with "tell me about a time when..." Most candidates know the acronym. Fewer use it well.
The structure
- Situation: One or two sentences of context. Where, when, what was happening.
- Task: What you were specifically responsible for.
- Action: The majority of your answer. What you specifically did, step by step. Use "I," not "we."
- Result: A concrete outcome, preferably a number.
Mistake 1: Too much Situation. Most candidates spend 60% of their answer on context and rush the Action and Result. Situation and Task combined should take no more than 20 to 30 seconds. Everything after that should be Action and Result.
Mistake 2: "We" instead of "I." Collaborative language is instinctive but evasive in an interview. "We delivered the project" tells the interviewer nothing about your contribution. Be specific about your role even when the work was genuinely collaborative.
Mistake 3: No result. An action without a result is an incomplete answer. If the outcome was not measurable, use a qualitative one: "The client renewed their contract," "The team adopted the process across all four sites," "My manager asked me to lead the next project as a direct result." Something concrete always exists.
Mistake 4: Only one version of each story. The same project can answer multiple question types if you adjust the emphasis. Prepare two or three angles on your strongest examples: one that demonstrates leadership, one that demonstrates problem-solving, one that demonstrates collaboration. A single well-understood example will serve you better than six half-prepared ones.
A worked example
The question: "Tell me about a time when you identified and resolved a significant operational problem."
Before (unstructured): "So at my last company we had this ongoing issue with our supplier lead times. It had been a problem for a while and everyone knew about it. We got together as a team and figured out a better way to handle it and things improved. It was a good project to be involved in."
After (STAR-structured): "At my previous role as an operations coordinator at a logistics firm, we were consistently missing delivery SLAs because supplier lead time data in our system was 11 days out of date on average. I was tasked with finding the root cause. I audited each of our 31 supplier relationships and found that 23 had no automated data feed into our ERP. I built a business case for a lightweight API integration, presented it to the operations director, received approval, and project-managed the rollout over six weeks. Average lead time data lag fell to 1.4 days and on-time delivery improved from 71% to 89% across the affected routes."
The second version is specific, active, and results-oriented. It uses concrete numbers and clearly attributes the work to the candidate rather than the team.
Preparing by Stage
Phone screen
Your goal is to advance, not to impress. Prepare your two-minute background summary and practise it out loud, not in your head. Have the job description open in front of you. Prepare two questions that signal genuine interest without getting ahead of the agenda for later rounds.
First round
Your STAR examples are the core of this stage. Prepare six to eight examples covering: a challenge you overcame, a time you led without formal authority, a significant failure and what you learned, a decision driven by data, a time you disagreed with a manager, and your proudest professional achievement. These six scenarios address the majority of first-round behavioural questions across industries.
Technical
Narrate your thinking as you work through the problem, not after you arrive at an answer. For code interviews, edge case identification and complexity analysis matter alongside correctness. For case interviews, a structured hypothesis and clear breakdown matter more than the exact conclusion.
Final round
Research each interviewer individually. Note their tenure, background, and any public writing or talks. Prepare at least one question tailored to each person. Have a clear 90-day vision for the role: what you would prioritise learning, what you would begin delivering, and how you would measure your own early progress.
Executive interview
Prepare to have a conversation, not a performance. Senior interviewers are evaluating how you think, not whether you have memorised the right content. Over-prepared delivery often reads as rigidity. Prepare two or three high-level questions about company direction and then listen carefully. The quality of your follow-up questions in the moment matters more than your prepared answers.
Asking Good Questions
Questions are not a courtesy at the end of the interview. At senior stages they are one of the primary ways interviewers assess clarity of thinking and genuine interest. Weak questions close conversations; strong ones open them.
"What does success look like in the first 90 days?" Signals you are thinking about delivery, not just getting the job. It also surfaces whether the role has clear objectives or vague expectations.
"What are the biggest challenges the team is currently navigating?" Shows commercial awareness and gives you information to assess whether this is a role you actually want.
"How has this role evolved over the past year?" Surfaces whether the position is growing in scope or contracting. An honest answer tells you more than any job description.
"What do the people who have thrived in this role have in common?" Invites the interviewer to articulate the real hiring criteria. What they describe is what you should reflect back in your remaining answers.
"What would make you confident you had made the right hire six months from now?" Most effective at final round. It asks the interviewer to define success explicitly and signals you are thinking about outcomes, not just employment.
Questions that fail: "What is the culture like?" is vague and answerable by the website. "When will I hear back?" signals anxiety. Questions about salary or benefits at early stages redirect attention away from your candidacy.
On the Day
Managing anxiety before the interview
Physical preparation affects performance more reliably than last-minute content review. Sleep, eating, and exercise beforehand are performance preparation. Arrive or log on ten minutes early. Stop reviewing notes in the final ten minutes. It raises anxiety without improving retention.
When you blank on an answer
Pause, breathe, and say "let me think about that for a moment." Three to five seconds of silence is entirely normal. If no relevant example comes to mind, offer an adjacent one: "I do not have a direct example of that exact situation, but here is a closely related one." Composure under pressure is a quality interviewers actively look for at senior levels.
Recovering from a poor answer
If you give an answer you are not satisfied with, address it: "Actually, I want to add something to what I just said. I did not mention [X], which is probably the most relevant part." The ability to self-correct in the moment is itself a signal worth sending.
The follow-up email
Send a short thank-you email within 24 hours: thanks for the time, one specific thing from the conversation that interested you, and that you look forward to next steps. Personalised and brief outperforms generic and thorough every time. If you're short on time or unsure how to phrase it, AI outreach messages can generate a first draft in seconds.
If the interviews go well and you end up weighing more than one offer, the framework shifts from "how do I get this job" to "which job do I take." See how to compare job offers for that next stage.
FAQ
How far in advance should you start preparing for an interview?
For a phone screen, one to two days of focused preparation is usually enough. For a first or second round, aim for three to five days. For a final round or executive interview, give yourself at least a week. The depth of company and stakeholder research required is significantly higher and rushed preparation shows.
What is the STAR method and how do you use it?
STAR stands for Situation, Task, Action, Result. It is a structure for answering behavioural interview questions that start with 'tell me about a time when...'. Situation sets the context briefly, Task explains what you were responsible for, Action describes what you specifically did, and Result quantifies the outcome. The most common mistake is spending too long on Situation and not enough on Action and Result.
What questions should you ask at the end of an interview?
Ask questions that demonstrate you have thought seriously about the role and the company. Strong examples include: 'What does success look like in the first 90 days?', 'What are the biggest challenges the team is currently navigating?', and 'How has this role evolved over the last year?' Avoid questions about salary at early stages and questions easily answered by the company website.
How do you prepare differently for a startup versus an enterprise interview?
Startup interviews test adaptability, ownership, and cultural fit more than process adherence. Expect less structured questions and more scenario-based discussion. Enterprise interviews are typically more structured with defined competency frameworks. Prepare more formal STAR examples and expect multiple rounds with different stakeholder groups. Research signals also differ: startups expect you to know the product intimately; enterprise interviewers expect strategic and market-level awareness.
What should you do if you blank on an answer during an interview?
Pause, take a breath, and say 'let me think about that for a moment.' Silence for three to five seconds is entirely acceptable and far better than filling the gap with an incoherent answer. If you genuinely cannot recall a good example, say so and offer a related one: 'I do not have a direct example of that specific situation but here is a closely related one.' Interviewers value composure and honesty over a polished answer to every question.