The Tech Interview Playbook
Last updated: February 2026
TL;DR
- Structured interviews are more predictive of job performance than unstructured ones
- Use scorecards with 1-5 ratings and evidence-based assessments for consistency
- Hold debriefs within 24 hours with all interviewers submitting scorecards beforehand
Contents
Great interviews do not happen by accident. They require structure, preparation, and alignment across your hiring team. Unstructured interviews are not only less predictive of job performance—they also create inconsistent candidate experiences and legal risk.
This playbook provides frameworks and templates for running effective technical interviews. Whether you are hiring your first engineer or scaling a team of hundreds, these principles apply.
The goal is to create a repeatable, fair process that identifies top performers while giving every candidate a chance to demonstrate their abilities.
Phone Screen Framework
Purpose: Quickly assess basic fit before investing interview panel time.
Duration: 30-45 minutes
Structure:
- Intro (5 mins): Explain the role and process
- Background (10 mins): Walk through their experience
- Technical basics (15 mins): Validate core skills for the role
- Motivation (5 mins): Understand their job search and priorities
- Questions (5 mins): Let them ask about the role and company
Sample questions:
- Tell me about a technical project you are proud of. What was your specific contribution?
- What technologies are you most excited to work with? Why?
- What does your ideal next role look like?
Decision criteria:
- Meets minimum technical bar for the role
- Genuine interest in your company/product
- Communication is clear and professional
- Timeline and expectations align
Technical Interview Best Practices
Core principles:
- Test relevant skills: Problems should mirror actual work, not algorithmic puzzles
- Create psychological safety: Anxious candidates underperform
- Provide context: Real problems come with background information
- Allow questions: Good engineers clarify requirements
Format options:
- Live coding: Best for pairing ability and thought process
- Take-home projects: Best for realistic work samples (respect candidate time)
- System design: Best for senior roles and architecture thinking
- Code review: Best for assessing engineering judgement
What to assess:
- Problem-solving approach, not just final answer
- Communication and collaboration style
- How they handle ambiguity and edge cases
- Technical depth in their areas of expertise
Red flags:
- Unable to explain their own past work
- Defensive when given feedback
- No questions about the problem or requirements
Interview Scorecard Template
Candidate: [Name]
Role: [Position]
Interviewer: [Your name]
Date: [Interview date]
Rating scale:
- 1 = Strong no hire
- 2 = Lean no hire
- 3 = Mixed signals
- 4 = Lean hire
- 5 = Strong hire
Technical competency: [1-5]
Evidence: [Specific examples from interview]
Problem-solving: [1-5]
Evidence: [How they approached the problem]
Communication: [1-5]
Evidence: [Clarity of explanations]
Culture alignment: [1-5]
Evidence: [Values demonstrated]
Overall recommendation: [Hire / No Hire / Need More Data]
Strengths: [Bullet points]
Concerns: [Bullet points]
Notes for next round: [Any specific areas to probe]
Hiring Debrief Process
Timing: Within 24 hours of final interview
Attendees: All interviewers, hiring manager, recruiter
Pre-work: All interviewers submit scorecards before debrief
Meeting structure:
- Silent review (5 mins): Everyone reads all scorecards
- Round robin (15 mins): Each interviewer shares their assessment (no interrupting)
- Discussion (15 mins): Address discrepancies and concerns
- Decision (5 mins): Hiring manager makes final call
Rules:
- No piling on—each interviewer speaks independently
- Hiring manager speaks last to avoid anchoring
- Focus on evidence, not gut feelings
- If split decision, bias toward gathering more data
Common pitfalls:
- Letting one strong opinion dominate
- Hiring for culture fit rather than culture add
- Overweighting recent interactions
- Ignoring red flags because of strong technical skills
Downloadable Templates
Available templates:
- 📄 Phone Screen Script - Structured 30-minute screen with scoring rubric
- 📄 Technical Interview Guide - Customisable problem formats with assessment criteria
- 📄 Interview Scorecard - Standardised evaluation form for all interview types
- 📄 Debrief Agenda - Meeting template with decision framework
- 📄 Candidate Feedback Template - Professional rejection and progression emails
- 📄 Interviewer Calibration Guide - Training document for new interviewers
Contact us to receive these templates in editable format.
Key Takeaways
- Phone screens should be 30-45 minutes covering background, technical basics, and motivation
- Technical interviews should test relevant skills that mirror actual work, not algorithmic puzzles
- Create psychological safety—anxious candidates underperform
- Use standardised scorecards with 1-5 ratings and require specific evidence
- Hiring manager should speak last in debriefs to avoid anchoring bias
- If split decision, bias toward gathering more data rather than forcing a choice
- Submit interview feedback within 24-48 hours while memories are fresh
Frequently Asked Questions
How long should a phone screen be?
Phone screens should be 30-45 minutes, structured as: intro (5 mins), background walkthrough (10 mins), technical basics (15 mins), motivation discussion (5 mins), and candidate questions (5 mins).
What is the best format for technical interviews?
The best format depends on what you are assessing. Live coding tests pairing ability and thought process. Take-home projects provide realistic work samples. System design suits senior roles. Code review assesses engineering judgement.
How should I score interview candidates?
Use a 1-5 scale: 1 = Strong no hire, 2 = Lean no hire, 3 = Mixed signals, 4 = Lean hire, 5 = Strong hire. Rate technical competency, problem-solving, communication, and culture alignment separately with specific evidence for each.
When should interview debriefs happen?
Hold debriefs within 24 hours of the final interview. All interviewers should submit scorecards before the meeting. The hiring manager should speak last to avoid anchoring other opinions.
What are red flags in technical interviews?
Key red flags include: inability to explain their own past work, defensiveness when given feedback, no questions about the problem or requirements, and focusing only on the solution without considering trade-offs or edge cases.