The Interview Prep Checklist Most Candidates Skip

You know the standard interview prep advice. Research the company. Practice common questions. Dress professionally. Show up on time. That advice is not wrong, but it is table stakes. Every halfway-serious candidate does those things.

The gap between candidates who get offers and candidates who "did fine but were not selected" is almost never about qualifications. It is about preparation depth. The candidates who win consistently are not smarter or more experienced. They are more thoroughly prepared in ways their competition did not think to be.

Here is the complete checklist. It is longer than most interview prep guides because it covers what most guides leave out.

1. Research the Interviewer, Not Just the Company

Every candidate researches the company. Surprisingly few research the actual person who will be interviewing them. This is a massive missed opportunity.

When you know who you are speaking with, you can:

• Understand their background and what they value (a CTO with an engineering background will ask different questions than one who came up through product management)
• Find genuine common ground that creates rapport naturally
• Anticipate what aspects of the role they care most about
• Tailor your examples to resonate with their experience

How to Research Your Interviewer

Start with LinkedIn. Look at their career path, not just their current title. What did they do before this role? How long have they been at the company? Have they published any articles or given any talks? Check if they have a personal blog, a Twitter/X account, or have been quoted in industry publications.

You are not stalking them. You are doing the professional equivalent of reading the syllabus before the first day of class. Interviewers notice when a candidate says, "I read your post about scaling the engineering team — I have faced similar challenges and I am curious how that has evolved." That is not flattery. That is showing you did the work.

If you do not know who your interviewer is, ask. A simple email to the recruiter or coordinator saying "Could you share who I will be meeting with so I can prepare effectively?" is completely reasonable and signals seriousness.

2. Prepare for the Specific Interview Type

A behavioural interview, a case interview, a technical screen, and a culture fit conversation are four entirely different assessments. Preparing the same way for all of them is like training for a sprint and a marathon with the same workout.

Behavioural Interviews

These focus on past experience as a predictor of future performance. The interviewer wants specific stories, not general philosophies. Prepare 8–10 stories from your career that cover: a major accomplishment, a failure and what you learned, a conflict with a colleague, a time you led without authority, a time you had to make a decision with incomplete information, and a time you had to influence someone senior.

Technical Interviews

These test domain knowledge and problem-solving ability. The preparation depends entirely on the field. For software engineering, practice coding problems. For data science, review statistics and work through case studies. For marketing, prepare to walk through campaign analysis. Ask the recruiter exactly what to expect. "Will this be a live coding exercise, a system design discussion, or a take-home?" Those require completely different preparation.

Case Interviews

Common in consulting, strategy, and increasingly in product roles. Practice structuring your thinking out loud. The interviewer cares less about your answer than about your framework for arriving at it. Practice with a timer — two minutes to structure, then walk through your approach.

Culture/Values Interviews

These are the interviews candidates prepare least for, which is a mistake. Research the company's stated values. Prepare one specific story for each value that demonstrates you live it. Do not just say "I value collaboration." Describe a time your collaboration with a specific person produced a specific result.

3. The STAR Method, Done Right

Everyone has heard of STAR: Situation, Task, Action, Result. Most people use it badly. The two most common mistakes are spending too long on the Situation and Task (the setup) and not enough time on the Action and Result (the part the interviewer cares about).

Here is the ratio to aim for:

• Situation: 10–15% of your answer. Two to three sentences. Set the scene quickly.
• Task: 10% of your answer. One to two sentences. What was your specific responsibility?
• Action: 50–60% of your answer. This is the core. What did you specifically do? Not the team. You. Be detailed about your reasoning, your decisions, and the steps you took.
• Result: 20–25% of your answer. Quantify wherever possible. Then add what you learned or what you would do differently.

The critical word in the Action section is "I." Interviewers are trained to listen for whether you use "I" or "we." "We decided to restructure the team" tells them nothing about your role. "I proposed restructuring the team, got buy-in from the engineering lead by showing the timeline impact, and then reassigned tasks based on each engineer's strengths" tells them exactly what you contributed.

4. Questions That Actually Impress

"Do you have any questions for me?" is not a formality. It is an evaluation. The quality of your questions reveals the quality of your thinking.

Here is what not to ask: anything you could find on the company's website, anything about salary or benefits in a first-round interview (save that for later stages or the recruiter), or generic questions like "What do you like about working here?"

Instead, ask questions that demonstrate you have thought about the role specifically:

• "What does the first 90 days look like for someone in this role?" Shows you are thinking about ramp-up and early impact, not just getting the offer.
• "What is the biggest challenge the team is facing right now that this hire would help address?" This tells you what problem you are actually being hired to solve — which might differ from the job description.
• "How is success measured in this role at the 6-month and 12-month marks?" Reveals whether the company has clear expectations or is making it up as they go.
• "I noticed [specific recent company initiative or product launch]. How has that affected the team's priorities?" Proves you did real research and are thinking about context.
• "What is something you wish candidates understood about this role before joining?" Often surfaces the unglamorous realities that determine whether you will actually enjoy the job.

Prepare five to six questions. You will likely only get to ask three or four, and some may be answered during the conversation. Having extras means you are never caught with nothing to ask.

5. The 24-Hour Pre-Interview Routine

What you do the day before and the morning of your interview matters more than most people realise. Not in a superstitious way — in a practical, cognitive-performance way.

The Day Before

• Do a final review of your research, not a cram session. Read through your notes on the company, the interviewer, and your prepared stories. You should be refreshing, not learning new material.
• Test your technology (for virtual interviews). Camera, microphone, internet connection, lighting. Close every application you do not need. Restart your computer. These sound obvious. People still get tripped up.
• Plan your outfit and logistics the night before. Decide what you are wearing. Know exactly how you are getting there (or where you are sitting for a video call). Eliminate every possible decision and anxiety source for the morning of.
• Do not rehearse past 8pm. Over-rehearsing the night before makes your answers sound scripted. You want to be conversational, not robotic.

The Morning Of

• Exercise, even briefly. A 20-minute walk or light workout reduces cortisol and increases focus. This is not motivational fluff — the research on exercise and cognitive performance is robust.
• Eat a real meal. Your brain consumes roughly 20% of your caloric intake. An interview is a sustained cognitive effort. Do not do it on an empty stomach or a sugar crash.
• Arrive (or log on) 10 minutes early, not 30. Arriving too early can be awkward for in-person interviews and creates unnecessary idle time that breeds anxiety. Ten minutes is professional without being excessive.

6. Post-Interview Follow-Up That Influences Decisions

The follow-up email is not a formality. Done well, it can genuinely affect the outcome — especially when you are neck-and-neck with another candidate.

Timing

Send your follow-up within two to four hours of the interview. Same day is essential. Next day is too late — by then, the interviewer may have already written their feedback.

Structure

Keep it to four to five sentences maximum. Include:

1. A genuine thank-you (one sentence).
2. A specific callback to something discussed in the interview that excited you. Not a generic "I enjoyed learning about the role." Reference the actual conversation. "The challenge you described around scaling the onboarding process for enterprise clients is exactly the kind of problem I find most engaging."
3. One brief addition. This is where you add something you wish you had said, or expand on a point you made. "I wanted to add to our discussion about stakeholder alignment — in my last role, I developed a framework for cross-team prioritisation that reduced conflicting requests by 40%. Happy to share more details if useful."
4. A forward-looking close. "Looking forward to the next steps."

If you interviewed with multiple people, send individual emails to each. Do not copy-paste. Reference something specific from each conversation. This takes ten extra minutes and is one of the highest-return activities in the entire interview process.

Putting It All Together

The full checklist, distilled:

None of this is secret. None of it requires unusual talent. It requires preparation that most candidates are too busy, too anxious, or too overconfident to actually do. That is precisely what makes it a competitive advantage.