Increasing Effectiveness As A Technical Candidate/Interviewer
summary
Panel argues tech interviews are broken and shows concrete fixes: stop keyword filters, run short technical calls that probe depth, use pair programming exercise to observe thinking, use the whiteboard for system architecture not for trivia and avoid asking trick algorithm puzzles. Companies report outcomes: Chef adds live pairing, some teams give candid rejection reasons, Github inspected for impact not polish. Expect practical examples, tradeoffs, and whether those changes actually improve hires.
AI-written summary · about
chapters (10)
- 0:00Tech interviews are broken
- 4:13Screening candidates
- 12:02Empathy in screens
- 14:07Mistakes in interviews
- 23:18Whiteboard debate
- 30:36Candidate mistakes
- 34:51Signals for success
- 39:48Passion beyond role
- 40:30Open source in hiring
- 43:21Feedback responsibility
related talks
30mInterview Them Where They Are
17mDe-Coding The Technical Interview Process
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
27mA Better Technical Interview
49mFinding potential in your interview processes
25mWhy Interviewing is Terrible
01h 16mTalks about 'Interview Like Google (or not)-But Better!'
32mApplied humaning for technical interviews