Technical Interviews Don't Have to Suck
summary
Teams use a set list of interview questions and a rubric to keep evaluations consistent, avoid live whiteboarding by design so candidates relax (no whiteboarding), and run conversations as coached problem-solving instead of quizzes (interactive coaching). Hiring scales from 10 to 60 front-end engineers, feedback takes 15 to 30 minutes after each hour interview, and examples pivot in difficulty or focus to reveal real experience and collaboration skills rather than trivia.
AI-written summary · about
chapters (11)
- 0:00Kind technical interviews
- 1:24Consistent and fair interviews
- 3:51Beyond whiteboarding
- 5:39Welcoming interview atmosphere
- 8:50Clear candidate expectations
- 10:13Interactive coaching
- 15:02Concrete skill assessment
- 17:08Detailed feedback
- 21:48Behavioral assessments
- 23:16Power dynamics in interviews
- 24:42Changing the industry
related talks
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
36mCracking the hiring process
25mWhy Interviewing is Terrible
51mTechnical Interview - Stories from the Other Side of the Desk
25mHow to Not Suck at Technical Interviews
30mInterview Them Where They Are
27mA Better Technical Interview