C̶r̶a̶c̶k̶i̶n̶g̶ Fixing the coding interview
summary
Examines how software engineers commonly mishandle technical interviews and identifies six specific recruiting mistakes made when assessing candidates. Describes practical steps to improve interviewer skills for evaluating engineers’ technical competence rather than relying on brainteasers or standard ‘cracking the coding interview’ prep.
AI-written summary · about
chapters (23)
- 0:00Intro
- 0:11CRACKING THE CODE INTERVIEW
- 2:25Candidate is not impressed
- 3:02interviewing is hard
- 4:44What is the difference between Vue & React?
- 5:36Bad predictor of skills
- 7:41What is the actual job definition
- 8:57Disruptor? Executioner? Enabler?
- 10:07Do your Research
- 11:49Experience is about how you make decisions based on what you know
- 12:06So, you've built a job scheduler? How the api looked like? How did you handle errors? And scale? Oh, how did you deploy? And what about tests?
- 12:40Fractal Questions
- 12:56can you apply your experience to our set of problems?
- 15:0920 minutes of Poker Face
- 16:14Engineering practices Clean code Production ready Tests
- 16:55Setting expectations
- 18:43culture fit is about shared values
- 19:24generalist vs. specialist pragmatic vs purist tech vs. product
- 20:25Through decisions & skills
- 21:16What do you focus on when you code review?
- 22:42Interview is a two way road
- 24:39SUMMARY
- 26:21Go train your interviewing muscle!
related talks
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
17mDe-Coding The Technical Interview Process
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
51mEngineering the Technical Interview
01h 03mCracking the Coding Interview
25mHow to Not Suck at Technical Interviews
25mWhy Interviewing is Terrible
48mHow to Hack the Interview