✳flâneur — a map of the web's best reading
How I Interview
rkoutnik.com · 1,922 words · saved by 1 readers
Technical interviews are terrible because we don’t know what we’re filtering for.
Technical interviews are terrible because we don’t know what we’re filtering for. Interviews are filters I think we all can agree that a good interview filter passes those who will do well at work and fails those who won’t. The trouble arises when we try to come to a common agreement on what “do well at work” means - every company is different. Instead, when we discuss interviews, we should grade them not on conformance to some holy standard but in how effectively they model day-to-day life at the company. This allows us to remove some of our pre-existing bias and focus on finding candidates w
Explore this link on the map →related reading
- Ask HN: What is a better approach to interviewing? | Hacker Newsnews.ycombinator.com
- The Guerrilla Guide to Interviewing (version 3.0) – Joel on Softwarejoelonsoftware.com
- How to hire engineering talent without the BS · Jesal Gadhiajes.al
- How We Hire Engineers When AI Writes Our Code | Tolans.comtolans.com
- How I Hire Programmers (Aaron Swartz's Raw Thought)aaronsw.com
- Technical interviewweb.archive.org
- The Hiring Post - Quarrelsomesockpuppet.org
- Interviewing tipschristinacacioppo.com
- How Firebase Interviewed Software Engineers • Andrew's Blogstartupandrew.com
- 40 Favorite Interview Questions from Some of the Sharpest Folks We Knowreview.firstround.com
- Questions I'm asking in interviewsjvns.ca
- Notes on the Industry Job Searchalisawuffles.github.io