Talks about 'Interview Like Google (or not)-But Better!'
summary
Focus on getting usable signal not whether a problem is finished: probe why mistakes happen, adjust for lost time, and note communication or nervousness as separate signals. Prefer fundamentals like arrays strings hash tables over obscure graph trivia, pick problems where candidates can give brute force then optimize, coach with increasingly specific hints, favor one hour coding slots, use HackerRank only as an early screen, avoid take‑home projects, and choose panels like two coding interviews plus one design and one behavioral.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 2:07Core hiring philosophy
- 6:16Knowledge questions explained
- 11:34Problem-solving scenarios
- 19:01Focus on signal not answers
- 21:31Choosing good interview questions
- 25:43Fundamentals over obscure knowledge
- 29:15Example of a bad question
- 31:22Example of a good question
- 33:46Supportive interviewing techniques
- 34:51Coaching vs hints in interviews
- 38:24Evaluating candidate performance
- 43:04Coding quality and style
- 47:39Whiteboard vs computer coding
- 51:33Final reminders on signal
- 52:15Q&A session begins
related talks
46mIncreasing Effectiveness As A Technical Candidate/Interviewer
30mInterview Them Where They Are
27mInterview with Confidence
27mA Better Technical Interview
05mThe perfect job interview (well, maybe)
17mDe-Coding The Technical Interview Process
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
01h 02mHow to be a better interviewer, change the world and work with amazing people