How to Not Suck at Technical Interviews
summary
Dataset from interviewing.io shows over 100,000 interviews and 10,000 hires; 40% of hires didn’t look good on paper. Women are 7× likelier to quit after one bad run and 3× after two, which explains performance gaps. Successful candidates wait ~4 minutes before coding, define ~3.29 functions vs 2.71, and a run of ~five mock interviews boosts real-screen pass rates 1.5–2×. Concrete tactics: offer choices to the interviewer, ask what to prioritize, write clean modular code, and treat interviews as collaborative practice.
AI-written summary · about
chapters (16)
- 0:00Introduction to technical interviews
- 1:23About the speaker and platform
- 3:09Performance inconsistency in interviews
- 5:18Mindset and gender disparity insights
- 7:03Practical interview tips
- 10:16Working code vs problem-solving
- 12:03Collaboration and interviewer focus
- 13:48What predicts interview success
- 15:11Mock interview data and practice
- 17:43Free interview replays resource
- 18:46Free mock interview offer
- 19:31Q&A: Googling in interviews
- 20:54Q&A: Big O complexity importance
- 22:17Q&A: Take-home vs live coding
- 23:39Q&A: Interviewer backgrounds
- 24:39Q&A wrap-up and closing
related talks
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
26mTechnical Interviews Don't Have to Suck
51mEngineering the Technical Interview
24mInterviews for developers, by developers
42mInterviewer Skills Hiring the Best Teammates
36mCracking the hiring process
27mInterview with Confidence