Conducting tech interviews
summary
Twenty years of hiring experience leads to concrete practices: after running ~40 interviews in 2–3 weeks (40+ intro calls, ~21 first-round, 12–15 second-round, 6–7 third-round) prioritize prepared, role-specific questions from the candidate CV, use two interviewers with split roles, and run 15-minute tech / 15-minute coding blocks. Avoid surprise tasks, require Android Studio prepped with dependency bundles, prefer open-ended prompts on coroutines vs Rx, and allow wrong answers while giving timely feedback and send interviewer names beforehand.
AI-written summary · about
chapters (13)
- 0:00Introduction and background
- 2:59Stress in interviews
- 4:47Evolution of tech interviews
- 10:55What to test in interviews
- 15:11Platform vs UI roles
- 16:16Open-ended questions
- 19:51Handling wrong answers
- 22:22Interviewer roles and setup
- 24:25Starting the interview
- 27:00Technical discussion approach
- 30:15Wrapping up the interview
- 33:28Post-interview steps
- 36:22Key takeaways
related talks
50mCracking the Mobile Interview
36mCracking the hiring process
01h 03mWhy Technical Engineering Interviews Are Broken and How to Actually Make Them Better
22mRecruiters, Developers, Good Cheer
26mTechnical Interviews Don't Have to Suck
51mTechnical Interview - Stories from the Other Side of the Desk
36mWe regret to inform you…
01h 02mInterviewing like a Boss