A Better Technical Interview
summary
Claims a better interview measures real work habits not trivia and gives candidates value back; specifics include a timed take-home exercise where candidates use their own editor and reviewers focus on design, tests and diffs, a structured rubric with written notes and an advocate who prevents anchoring, plus a short pair programming session to observe collaboration, tool fluency, and teaching ability. The process emphasizes declared grading criteria, humility, dialogue, and concrete examples of code reviewed and changed rather than whiteboard puzzles.
AI-written summary · about
chapters (32)
- 0:00Intro
- 0:15Sam Jones @samjonester
- 3:17A Better Technical Interview
- 4:41Goals
- 5:14Trivia Questions
- 5:29Good Interviews Highlight The Candidate
- 5:45Unnecessary Algorithms
- 6:06Unrealistic Situations
- 6:27Good Interviews Reflect The Job
- 6:45Lack of Transparency
- 7:01Unclear Rubric
- 7:46Good Interviews Give Feedback
- 8:06Continuous Improvement
- 8:42Expectations: · Breakdown Work . Communicate • Learn
- 12:16Solidify Values
- 13:00Humanize Yourself
- 13:37Compliment
- 14:20Internal Stories
- 15:48Unintentional Discrimination: Salesman Guys
- 16:45Cultural Fit Addition
- 17:28Structured Rubric
- 18:27Increase Accountability
- 19:06Allow Time For Evaluation
- 19:32Anchoring During Transitions
- 20:40Clarify
- 21:01Coordinate
- 21:25Promote the Company
- 21:48The Actual Interview
- 22:07"Review", "Refactor"
- 23:52Take Home and/or Pair
- 25:40Recap
- 26:09COLLECTIVE
related talks
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
17mDe-Coding The Technical Interview Process
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
30mInterview Them Where They Are
05mThe perfect job interview (well, maybe)
32mApplied humaning for technical interviews
01h 16mTalks about 'Interview Like Google (or not)-But Better!'
51mTechnical Interview - Stories from the Other Side of the Desk