1. Prepare Thoroughly (Do This Before the Interview)

• Re-read the job description and identify the 5–8 core competencies or results the role demands (e.g., “drives SQL-heavy analysis,” “manages stakeholders in different time zones,” “writes production-grade Python”).

• Build a short interview guide with 2–4 targeted questions per competency. Use behavioral (“Tell me about a time…”) and situational (“How would you…”) questions.

• Assign roles if it’s a panel: who asks what, who takes notes, who watches body language.

• Review the candidate’s resume and LinkedIn for 5–10 minutes. Mark 3–4 specific items you want to probe (gaps, short tenures, achievements that seem inflated, etc.).

2. Set the Right Tone (First 3–5 Minutes)

• Start on time and greet them warmly—remember they’re evaluating you too.

• Give a 60–90 second overview: company stage, team size, why the role exists, and what success looks like in the first 6 months.

• Explain the interview structure (“We’ll spend 35 minutes on your experience, 10 minutes on a short exercise, and leave time for your questions”).

3. Ask Great Questions and Listen More Than You Talk

Golden rule: 80/20 → candidate talks 80 % of the time.

• Start with an easy warm-up: “Walk me through your journey to this point in your career.”

• Use the STAR follow-up method when answers are vague: Situation → Task →  Action → Result Example: “What was the outcome?” → “How did you measure success?” → “What would you do differently next time?”

• Dig for contrarian evidence: if they claim they’re “very data-driven,” ask for the last time data changed their mind against their gut.

• Avoid hypothetical questions (“What would you do if…”) unless paired with real past examples—they’re easy to fake.

4. Test Real Skills (When Relevant)

• For  technical roles: live coding, take-home that mirrors real work (with a strict time box), or a 20-minute whiteboarding session.

• For non-technical roles: case studies, writing exercises, role-plays, or inbox prioritization tasks.

• Always explain the “why” behind the exercise so it doesn’t feel like a gotcha.

5. Sell the Role and the Company

Top candidates have options. Use the last 10 minutes to:

• Ask what matters most to them (growth, impact, compensation, culture, remote policy, etc.).

• Address their priorities directly with concrete details (“We promote 40% of individual contributors to management within 3 years,” “Everyone gets £5k annual learning budget,” etc.).

• Share one authentic, recent win story from the team.

6. Close Cleanly and Set Expectations

• Thank them and explicitly say what happens next and when (“You’ll hear from us by Thursday even if it’s a no.”).

• Ask for any final questions and answer transparently—avoid corporate jargon.

7. Debrief Immediately (Within 30 Minutes)

• Each interviewer independently writes feedback and scores (1–5) against the core competencies before discussing.

• Look for specific evidence, not vague feelings (“loved his energy” → weak; “correctly identified the join bottleneck in under 2 minutes” → strong).

Bonus Tips

• Illegal questions: Never ask about age, marital status, kids, religion, health issues, etc. When in doubt, focus only on job-relevant criteria.

• Reduce  bias: Use the same question set for every candidate in the same stage. Score immediately and rely on evidence.

• Remote interviews: Test tech 10 minutes early. Keep video on. Have a quiet, well-lit background.

A great interview feels like a deep, mutual conversation—not an interrogation. When you prepare well, listen intently, test real skills, and sell authentically, you dramatically increase the odds of finding someone who will thrive in the role and make your team stronger.