How to Prepare for a Job Interview (Practical Guide)

Most candidates spend 80% of their prep time rehearsing answers and 0% understanding the company they are interviewing with. That is backwards. Interviewers notice within the first few minutes whether a candidate has actually thought about the role — and most have not.

Start with the role, not with yourself

Before you prep a single answer, spend 30–45 minutes doing this:

1. Print or paste the job description into a document. Highlight every repeated word — those are what the team actually cares about, not the boilerplate.
2. Map each highlighted requirement to a specific example from your work history. This becomes your answer bank.
3. Read the company's last 3 press releases, their about page, and Glassdoor reviews from the past 12 months. You will be asked 'why us' — generic answers are disqualifying.
4. Find the interviewer on LinkedIn if you know who it is — not to stalk, but to understand what they care about professionally.

This step alone puts you in the top 20% of candidates before you say a word.

Structure your answers — but not robotically

The STAR framework (Situation, Task, Action, Result) is useful but often produces stilted, over-rehearsed answers. A better mental model:

• Context (one sentence): what was the situation and why did it matter?
• What you specifically did (not "we"): two or three concrete actions, in order.
• The outcome (specific, quantified where possible): what changed because of your decisions?

Interviewers are trained to listen for "I" vs "we". Saying "we built the feature" tells them nothing about your contribution. Be specific about your decisions, your judgment calls, your trade-offs.

The questions you must prepare for

These appear in nearly every interview regardless of level or role:

• "Tell me about yourself" — this is not an invitation to summarise your CV. It is a 90-second pitch for why you are the right person for this specific role.
• "Why are you leaving your current job?" — be honest but frame it as moving toward something, not fleeing from something.
• "Tell me about a time you failed" — the answer they want is one where you actually failed, took ownership, and learned something specific. Confected failures are obvious.
• "Where do you see yourself in 5 years?" — connect it to what this role enables, not a generic ambition statement.
• "Why do you want to work here?" — if you cannot give a specific, researched answer, do not expect to advance.

Technical and case rounds: what preparation actually looks like

For technical roles, most candidates over-prepare obscure knowledge and under-prepare communication. In a live technical screen, articulating your thinking out loud usually matters more than silently arriving at the right answer.

• Practise problems while explaining each step. If you cannot explain it, you do not understand it well enough yet.
• For case interviews (consulting, product, strategy roles): practise structuring the problem before solving it. Rushing to a solution before framing it is the single most common mistake.
• Mock sessions with someone who has done these interviews — or sat on the other side of them — are far more valuable than practising alone. Self-evaluation of interview performance is unreliable.

Questions to ask them (this is not optional)

Asking good questions signals genuine interest and preparation. 'No, I think you've covered everything' is one of the worst things you can say. Prepare three to five. The best ones:

• "What does success look like in this role at 90 days?" — shows you think in outcomes, not just tasks.
• "What are the biggest challenges the team is currently navigating?" — shows you are thinking about the real job, not the job description.
• "How would you describe collaboration between this team and [adjacent team]?" — probes culture and cross-functional dynamics honestly.
• "What made previous people successful in this role?" — and optionally: "What caused people to struggle here?" Both reveal a great deal.

Avoid questions about salary, leave, and benefits in the first round. Those conversations belong after an offer exists.

Logistics that trip people up

• Virtual interviews: Test your audio and camera 30 minutes before, not 2 minutes. Close background apps. Use a wired connection if the call is important.
• In-person: Arrive 10–15 minutes early. Bring printed copies of your resume even if you submitted digitally. Know who you are meeting and how to pronounce their name.
• Dress code: When in doubt, dress one level above what you think the office norm is. Nobody has ever been rejected for being slightly overdressed.

The 48 hours before and the day after

The day before: review your notes, do a final spoken practice session (out loud, not in your head), sleep normally. Cramming extra material the night before rarely helps and reliably increases anxiety.

The day after: send a short, specific thank-you email to your interviewer within 24 hours. Reference one concrete thing from the conversation. This is professionalism, not flattery — and it keeps you top of mind during deliberation.

If you do not hear back within the timeline they gave you, one follow-up email after that deadline is appropriate. Beyond that, move your energy to the next opportunity.