AI summary by TwinMind
Rethinking the Technical Interview
Theo - t3․gg
13m 9s
Current State of Technical Interviews
- Most companies doing interviews "egregiously incorrect"
- Standard format: random technical questions from company question bank
- Algorithm-heavy, code-focused problems
- Boils down to: "do you know what algorithm this problem is based on?"
- Method persists because it filters for people willing to grind through nonsensical tasks
- Alignment with company culture: maintaining 20-year-old services no one wants to work on
- Interview culture reflects type of company you'll work at
Proposed Alternative: Agency-Based Interview Model
- Core principle: give more agency to interviewee during interview
- Goal: set up engineers for success, not challenge them
- Send document to candidate weeks before interview
- Document details multiple interview options and expectations
- No surprises or curveballs during interview
- Reference: publicly shared document sent to Dan Abramov in 2021
- Dan's performance: only passed traditional interviews in author's format
Four Interview Options Framework
Option 1: The Traditionalist
- Standard LeetCode-style algorithmic problems
- Acceptable option if candidate trained for this format
- Goal: let candidates showcase skills in their comfort zone
- Not aligned with actual daily work at most companies
Option 2: The Pragmatist
- Realistic code problems vs weird algorithms
- Example: Pokedex problem (used 100+ times)
- Step-by-step building approach
- Tests React core concepts understanding
- Starts with JavaScript object → reusable component → array rendering → table → selection component integration
- Mirrors actual daily development work
- No special practice required beyond regular coding
Option 3: The Realist
- Candidate brings own project/bug/feature
- Share repo ahead of time
- 1.5-2 hour pair programming session
- Shows actual working style and collaboration
- Reflects real daily work (pair programming)
- Best way to understand technical capability and collaboration style
- Surprisingly few people choose this option
Option 4: The Specialist
- Custom approach if other options don't fit
- Candidate proposes better way to showcase skills
- Interviewer willing to try new techniques
- Flexibility over rigid process
- Worth risking 1.5 hours for incredible hire
Take-Home Assignments Considerations
- Author personally likes doing them as candidate
- Concerns as interviewer:
- Certain employee types can't justify unpaid free time
- Feels wrong not paying for potentially usable work
- Would create take-home if candidate prefers
Interview Participation Recommendations
- Do more interviews on both sides (giving and receiving)
- Qualified job candidates = qualified to interview
- Talk to manager about joining interview process ASAP
- Benefits of interviewing others:
- Understand team fit better
- Gauge where you fit on team
- Learn how interviews go well/poorly
- Improve your own interview performance
- Author did 6 interviews/week at career peak
- Became "lunch buddy" for struggling candidates
- Helped save candidates who would have fallen through cracks
Interview Feedback Philosophy
- Always provide feedback to rejected candidates
- Not giving "cheat codes" - giving growth opportunities
- Return value for time spent interviewing
- No reason to withhold improvement suggestions
Market Context
- Author at "ping" company
- Fewer recent interviews due to market conditions
- Still concerned about current interview experiences
- Good interview processes create positive word-of-mouth
- Team quality limited by interview process quality
