The Code-Free Developer Interview
summary
Claims that dozens of hires happen without ever seeing a candidate's code and that code review role play and collaborative system design replace coding tests. Details: give a tiny, readable pull request with a couple realistic smells (not production code), role-play the reviewer conversation, or sketch an MVP (e.g., Facebook friending vs feed) and scale complexity to judge junior/mid/senior in ~15 minutes. Also keep a consistent rubric and written notes.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:29What is a "Coding Interview"
- 2:28Disfavored Interview Techniques
- 3:56The Problem With Coding Interviews
- 6:52General Interviewing Tips
- 14:53Selecting Code to Review
- 17:22Evaluating a Code Review
- 20:30What is "Collaborative System Design"?
- 22:00How To Pick A CSD Project
- 23:46General Tips for Running CSD
- 25:14Build Facebook: The MVP
- 27:50When To Use Coding Interviews
related talks
24mInterviews for developers, by developers
18mHow To Review Someone's Code While Not Being A Jerk!
26mA Solution to the Tension Between Worker Shortage and the Hungry Hungry Developer
38mCracking the Code Review: from Guesswork to Automated Guidance
45mThe Science of Code Reviews
30mCode Reviews is more than a crushing Developer Experience
45mCracking the Code Review
38mCode reading