Why Most Candidates Under-Prepare
Most candidates read the job description and browse the company's About page. Then they walk into the interview hoping the conversation goes well. That's not preparation — it's hoping.
Good interview preparation is structured, deliberate, and typically takes 3–6 hours for a role you really want. It covers four areas: knowing the company, knowing the role, knowing your own stories, and knowing the logistics. Missing any one of these creates avoidable gaps that sharp interviewers will find.
The upside of thorough preparation is significant. Research consistently shows that prepared candidates perform better not just in what they say, but in how they come across — composed, engaged, and genuinely interested rather than guessing their way through.
Company Research: What to Know Before You Walk In
Business basics: what does the company do, who are their customers, and how do they make money? You should be able to explain this in 2–3 sentences without looking at your notes.
Recent news: check the company's press page, LinkedIn, and Google News for the last 3–6 months. Recent funding rounds, product launches, leadership changes, expansions, or challenges give you context and potential conversation points.
The interviewer: if you know who's interviewing you, look them up on LinkedIn. What's their background? How long have they been there? What do they seem to care about? This helps you calibrate your language and emphasis.
The team or department: find out as much as you can about the team you'd be joining. How large is it? What are they working on? What's their remit?
The competition: who are the company's main competitors, and what's the company's differentiated position? This signals commercial awareness.
Why this company specifically: you will almost certainly be asked "why us?" Have a real, specific answer that isn't just "great company, great mission." What specifically about this company, at this stage, is right for you?
Role Preparation: Match Yourself to the Job Description
Go through the job description line by line and prepare a story or example for each major requirement. The STAR method (Situation, Task, Action, Result) is the standard framework:
- Situation: the context — where, when, what was happening
- Task: your specific role or responsibility in that situation
- Action: what you specifically did — the concrete steps you took
- Result: what happened — quantify wherever you can
Prepare 5–8 strong STAR stories from your own experience. Most interview questions — "tell me about a time you..." "give me an example of..." "describe a situation where..." — are best answered with a story in this structure. The LoopCV STAR Answer Builder can help you structure these before your interview.
For every requirement in the JD: ask yourself "what is my strongest example of this?" If you can't answer that, you've identified a potential weak point to address or prepare to talk around.
While you're here
Build your STAR interview answers before you go in
The LoopCV STAR Answer Builder helps you structure experience-based interview answers with a speaking time estimate. Free, no sign-up.
Build my STAR answer — freePractise Out Loud — Not Just in Your Head
The most common mistake in interview preparation is mentally rehearsing rather than verbally rehearsing. Thinking through an answer feels complete — until you try to say it out loud and discover it's much harder to deliver than it was to think.
Practise by speaking answers out loud, not just reviewing them mentally. Time yourself — most strong interview answers run 90 seconds to 2 minutes. Shorter and you may seem thin; longer and you may seem unable to edit.
Record yourself. Even a voice note on your phone reveals things you can't hear in your head: filler words ("um," "like," "sort of"), trailing sentences, lack of concrete structure. Watch one playback and identify the top two things to fix.
Do a mock interview. Ask a trusted person to ask you questions and give honest feedback, or use a structured mock interview tool. The goal is replicating interview conditions, not just reviewing content.
Logistics, Day-Of Prep, and Follow-Up
Logistics:
- Know exactly where the interview is (or which video platform, with login details tested in advance)
- Plan to arrive 10 minutes early — not exactly on time, not 30 minutes early
- Bring a printed copy of your resume, a notepad, and a pen — even for video interviews
- Confirm the format in advance if not specified: how many interviewers? How long?
Day of:
- Sleep well the night before — fatigue is the most underrated interview impairment
- Eat something — low blood sugar affects cognitive performance measurably
- Review your key STAR stories and company research notes one final time
- Dress appropriately — when in doubt, slightly more formal than you expect the dress code to be
After the interview:
Send a thank-you email within 24 hours. Brief and professional — express genuine appreciation, reiterate your interest in the role, and note one specific thing from the conversation. The LoopCV Interview Thank-You Email Generator produces a subject line and full email body in under a minute.
Questions to Ask at the End
"Do you have any questions for us?" is not a closing formality — it's part of the assessment. Candidates who ask sharp questions show commercial thinking and genuine interest. Candidates who say "I think you've covered everything" signal a lack of preparation.
Prepare 3–5 questions in advance, across these areas:
The role: "What does success in this position look like in the first 90 days?" / "What are the biggest challenges the person in this role is likely to face?"
The team: "How does this team collaborate with [related department]?" / "What's the team culture like?"
Growth: "What development opportunities are available for this role?" / "What career paths have people in this role typically followed?"
Next steps: "What are the next steps in the process, and what's the expected timeline?"
Ask real questions you actually want answered. Don't ask things easily found on the website — it signals you didn't research.