Interview Them Where They Are
summary
Argues that technical interviewing is broken and prescribes concrete fixes: refactor job descriptions to state required stack and success metrics (example: JavaScript/React, Go, Kubernetes, Postgres) and drop gatekeeping year/degree rules; replace one-size-fits-all whiteboard grilling with made-to-measure interviews — take‑homes, pairing sessions, system‑diagram exercises, refactoring tasks — the company Test Double already uses pairing and modular interview modules to get higher‑fidelity signals of real work.
AI-written summary · about
chapters (6)
- 0:00Start
- 9:22Optimize for demonstrating competencies
- 25:21Doesn't this introduce bias
- 26:04Uniform != Unbiased
- 27:21Try made-to-measure interviews
- 27:43Look for strengths rather than prod for weaknesses
related talks
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
17mDe-Coding The Technical Interview Process
25mWhy Interviewing is Terrible
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
27mA Better Technical Interview
01h 16mTalks about 'Interview Like Google (or not)-But Better!'
01h 02mHow to be a better interviewer, change the world and work with amazing people
27mTech hiring is broken' is broken