Cracking the hiring process
summary
Based on hundreds of interviews, the practical recipe is: define a scorecard, run a 30-minute screening by a developer on video to fish for dealbreakers, keep processes short, and design a 1–2 hour homework (candidates report tests often take 4–5 hours so measure it). Prefer live pairing on the candidate’s laptop, avoid whiteboards, collect reference examples rather than yes/no claims, and always offer a debrief call after invested stages so rejected candidates get concrete feedback.
AI-written summary · about
chapters (14)
- 0:00Introduction to hiring
- 1:47Why hiring matters to developers
- 5:18Hiring challenges and biases
- 8:47Designing a delightful process
- 11:34Typical hiring process overview
- 12:36Screening call best practices
- 16:07Homework assignments debate
- 19:40Designing effective homework
- 23:12Live coding interview tips
- 27:04Manager interview focus
- 28:46HR interview and soft skills
- 29:07Reference checks importance
- 31:34Rejection calls and feedback
- 35:05Conclusion and key takeaways
related talks
44mHire Better Faster Stronger
43mLanding your next gig
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
26mTechnical Interviews Don't Have to Suck
49mFinding potential in your interview processes
42mInterviewer Skills Hiring the Best Teammates
07m“How to interview software testers to hire the most talented ones”
17mDe-Coding The Technical Interview Process