How to Prepare for an Interview
Most candidates review their resume and hope for the best. The ones who consistently get offers research the company deeply, build a library of role-specific answers, and practice until delivery stops feeling rehearsed.
The 5-layer preparation system
Company research — 1 week before
Time investment: 3–4 hours
Most candidates Google the company name and read the about page. Hiring managers can tell. Deep research means: understanding the business model (how they make money), recent performance (earnings calls, press releases, growth metrics), competitive context (who they're competing with and why they think they win), recent product or strategy moves, and what's publicly known about the team or function you'd be joining.
How to do it
- →Read the company's 10-K or investor presentations if public; use Crunchbase, PitchBook, or CB Insights for startups
- →Listen to the 2 most recent earnings calls — the Q&A section reveals what investors are worried about, which is often what leadership is focused on internally
- →Read Glassdoor reviews from the last 12 months, filtering for current employees in your target function
- →Find the LinkedIn profiles of your interviewers — note their backgrounds, tenure, and what they've shared publicly
- →Read any press coverage from the last 6 months — both positive stories and critical coverage
Output
A 1-page brief with: company snapshot, 3 things that excite you about the company, 2 risks or challenges the company faces, and 2 questions that demonstrate this research.
Role analysis — 5 days before
Time investment: 2 hours
The job description is a map of every question you'll be asked. Most candidates read it once. The candidates who prepare well annotate it: matching every requirement to a specific example from their history and flagging any gaps that need to be addressed preemptively.
How to do it
- →Print or paste the job description and highlight every requirement and 'nice to have'
- →For each requirement: write a one-sentence example from your experience that demonstrates it
- →For requirements you can't match directly: identify the closest adjacent experience and prepare a bridge ('I haven't done X specifically, but my experience with Y gave me...')
- →Identify the 3 requirements that appear most important based on position in the JD, frequency of mention, and interview format hints
- →Research the technical or domain knowledge areas mentioned — read 1-2 primary sources on any topic you're weak on
Output
A requirements-to-examples mapping table you can use to build your answer library.
Answer library — 4 days before
Time investment: 4–6 hours
Behavioral interviews ask you to prove skills with specific stories. The STAR method (Situation, Task, Action, Result) gives structure to those stories. The mistake is having the same 2–3 stories you tell for every question. The professionals who interview well have 8–12 distinct STAR stories ready, each demonstrating a different skill, and they match them dynamically to whatever question is asked.
How to do it
- →Write 8–12 STAR stories covering: leadership without authority, handling conflict or failure, navigating ambiguity, driving a result under constraints, influencing stakeholders, learning quickly in a new area, managing competing priorities, receiving and acting on difficult feedback
- →Each story should be 2–3 minutes when told aloud — not shorter (too thin) and not longer (loses the room)
- →For technical roles: prepare worked examples or system design scenarios that you can walk through clearly
- →For case interviews (consulting, strategy, some finance): practice 2–3 case frameworks until the structure is automatic
Output
A written answer library — 8–12 stories each with a headline (what skill it demonstrates), the 4 STAR components, and the key result number.
Mock practice — 2–3 days before
Time investment: 2–3 hours across sessions
Reading answers is not preparation. Speaking answers is preparation. Most candidates skip this step because it's uncomfortable to hear themselves stumble. But stumbling in practice is the whole point — you want to find the weak parts of your answers, the places where your timing is off, and the moments where you lose momentum before it happens in the real interview.
How to do it
- →Practice your 5–6 most likely behavioral questions out loud — not silently, and not in your head
- →Record yourself on your phone and watch it back — look for filler words ('um,' 'like,' 'you know'), rambling, and answers that run over 3 minutes
- →Practice with a partner if possible — ideally someone who will ask follow-up questions rather than just listen passively
- →Do at least one full mock interview with 45–60 minutes of questions in sequence, simulating the full interview pressure
Output
A list of the answers that still feel weak after practice — these get additional rehearsal time the day before.
Logistics and mindset — 1 day before
Time investment: 30 minutes
The day-before prep is underrated. Most of what goes wrong in interviews isn't content — it's logistics (tech failure, late arrival, wrong building) or mindset (anxiety that clouds thinking, blank-drawing on an easy question). Both are fully preventable.
How to do it
- →For remote: test your camera, microphone, and internet connection. Know the video platform (Zoom, Teams, Google Meet) and have a backup (phone hotspot, headset ready)
- →For in-person: confirm address, parking, and building entry. Plan to arrive 15 minutes early. Know who you're meeting and have their contact information
- →Review your answer library once — not to memorize, but to refresh the key moments of each story
- →Prepare your 3 best questions for the end of the interview — questions that demonstrate research and genuine curiosity, not questions about salary or vacation
- →Sleep. The cognitive difference between 7 hours and 5 hours of sleep is measurable and will show in how you think under pressure
Output
Confirmed logistics + 3 smart closing questions ready.
Mistakes that cost offers
Only preparing for questions you expect
Prepare for the questions you don't expect — especially 'Tell me about a failure,' 'Describe a conflict with a manager,' and 'Why are you leaving your current role?' These are guaranteed to be asked and the least-prepared candidates stumble on them.
Memorizing answers instead of owning them
Memorized answers sound memorized. Know the structure and the key beats of each story — situation, what you specifically did, the result — without scripting every word. The delivery should feel fluent, not recited.
Asking no questions or asking generic questions
'What does success look like in the first 90 days?' and 'What's the biggest challenge the team is currently facing?' are strong. 'What's the company culture like?' and 'What do you like about working here?' are weak and signal shallow preparation.
Not researching the interviewers specifically
30 minutes on the LinkedIn profiles of your interviewers changes the dynamic. You can reference their work, frame questions around their experience, and calibrate your answers to their background. Interviewers who feel seen engage more.
Common questions
How many days before should you start preparing for an interview?
For a standard screening call: 1–2 days is sufficient. For a full interview loop (multiple rounds with different interviewers): start 1 week out. Spread preparation across multiple shorter sessions — 2–3 hours per day — rather than cramming everything the night before. Spaced practice across several days produces better recall and more natural delivery than a single marathon session. The day before should be light review and logistics, not first-time preparation.
How do you prepare for unexpected interview questions?
The key is building a flexible answer library rather than scripted responses. When you have 8–12 strong STAR stories prepared, you can mix and match them to almost any behavioral question — 'Tell me about a time you had a conflict with a teammate' and 'Tell me about a time you demonstrated leadership' might both be answered with the same underlying story, just with different emphasis. For truly unexpected questions: pause, say 'let me think about that for a moment,' and think about which of your prepared stories comes closest. Interviewers rarely mind a 5-second pause — they do mind rambling answers that go nowhere.
What should you bring to a job interview?
For in-person interviews: 5 copies of your resume (more than you expect to need), a notepad and pen for taking notes, a copy of the job description with your annotations, a list of your references, and any portfolio work samples relevant to the role. For remote interviews: your resume open on a second monitor or printed beside you, your STAR story notes nearby (out of camera view), the job description, a glass of water, and your 3–5 closing questions written down. Knowing you have your notes nearby reduces anxiety even if you never look at them.
Zari builds your interview answer library from the job description — then coaches you through practice.
Zari generates role-specific questions from the job posting, evaluates your STAR answers, and coaches you through every behavioral and technical question you're likely to face. Start free.
Try Zari free