Interviewing is a noisy prediction problem · Erik Bernhardsson
I have done roughly 2,000 interviews in my life. When I started recruiting, I had so much confidence in my ability to assess people. Let me just throw a couple of algorithm questions at a candidate and then I'll tell you if they are good or not! Over time I've come to the (slightly disappointing) realization that knowing who's going to be good at their job is an extremely hard problem.
Interviewing is a noisy prediction problem 2018-05-02 I have done roughly 2,000 interviews in my life. When I started recruiting, I had so much confidence in my ability to assess people. Let me just throw a couple of algorithm questions at a candidate and then I'll tell you if they are good or not! Over time I've come to the (slightly disappointing) realization that knowing who's going to be good at their job is an extremely hard problem. The correlation between who did really well in the interview process and who performs really well at work is really weak. Confronted by this observation I've
Explore this link on the map →related reading
- How We Hire Engineers When AI Writes Our Code | Tolans.comtolans.com
- Notes on the Industry Job Searchalisawuffles.github.io
- Ask HN: What is a better approach to interviewing? | Hacker Newsnews.ycombinator.com
- The Hiring Post - Quarrelsomesockpuppet.org
- ML Job Interviews: The Ultimate Guide – Silvia Saporasilviasapora.github.io
- The Guerrilla Guide to Interviewing (version 3.0) – Joel on Softwarejoelonsoftware.com
- How to hire engineering talent without the BS · Jesal Gadhiajes.al
- 40 Favorite Interview Questions from Some of the Sharpest Folks We Knowreview.firstround.com
- How I Hire Programmers (Aaron Swartz's Raw Thought)aaronsw.com
- How to Interview and Hire ML/AI Engineerseugeneyan.com
- Finding Person-Problem Fit - Compound Manualmanual.withcompound.com
- How to Prepare for an Interview | Grow with Googlegrow.google