Hiring Developers, with Science!
summary
Argues that most interviews are invalid because they measure the interviewer not the candidate and offers Industrial/Organizational tools: focus on validity, reliability, usability of each stage. Recommends testing interviews against outside samples, use constrained work samples or timed homework, prefer behavioral interviewing over whiteboard puzzles and trivia, standardize schedules and scoring rubrics, log objective evidence in debriefs, craft inclusive job postings (Textio, Joblint), and avoid unpaid live coding on production.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:09interviewing is hard
- 1:51interviewing is expensive
- 4:32industrial & organizational psychology
- 8:27RELIABILITY
- 15:25what do you need?
- 23:10INTERVIEW DAY
- 28:13tell me about a time...
- 30:47RECAP
related talks
25mWhy Interviewing is Terrible
30mInterview Them Where They Are
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
24mInterviews for developers, by developers
28mThe Science of Hiring Developers - Recruiting for Raw Talent
36mCracking the hiring process
42mInterviewer Skills Hiring the Best Teammates
51mEngineering the Technical Interview