De-Coding The Technical Interview Process
summary
Five concrete changes to fix technical interviews: run them like pair programming sessions and teach small fixes such as using array destructuring to shorten assignments or applying BEM naming to reduce repeated CSS; replace abstract puzzles with job‑relevant prompts (sort menu items by price, debug why a pink box isn’t styled); allow candidates to Google so interviewers can evaluate search and reasoning; use two interviewers who submit blind feedback and then debrief; offer paid take‑home options.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:33The Worst Technical Interview
- 4:18Use the Interview as a Teaching Opportunity
- 7:24Ask Questions
- 9:55Practical Questions
- 11:12Trivia Style Questions
- 12:10Google
- 12:41Two Interviewers
- 13:42Unconscious Bias
- 14:59Questions
related talks
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
30mInterview Them Where They Are
27mA Better Technical Interview
25mWhy Interviewing is Terrible
51mTechnical Interview - Stories from the Other Side of the Desk
36mCracking the hiring process
32mApplied humaning for technical interviews