3 ms·
> Thomas Ptacek has this great line about how “we interview people whose only prior work experience is "Line of Business .NET Developer", and they end up showin
by bob1029 5y ago
> Thomas Ptacek has this great line about how “we interview people whose only prior work experience is "Line of Business .NET Developer", and they end up showing us how to write exploits for elliptic curve partial nonce bias attacks that involve Fourier transforms and BKZ lattice reduction steps that take 6 hours to run.”
This is why we stopped hiring based on resume and just use it as a conversational piece to figure out if the candidate can be coached or not. We don't give much of a shit what you currently know as a prospective employee. We care about how fast you could learn new things that we haven't even thought of yet.
- ryandrake 5y agoI wish more interviewers were like you! I happen to think there are a lot of developers and other tech employees out there who, for reasons you as the interviewer don't know, are plugging away at a company/role way below their capability or current skill level. Or, who are literal geniuses but don't happen to have MIT, Stanford or UC Berkeley on their resume. Capable of research and invention, but no PhD. People who just were never discovered, mentored and given the opportunity to get on a rocket ship. Raw talent sitting there writing CRUD apps for some dopey company just limping along, who sometimes don't even know how good they are. Yet, when [the usual suspect] companies are hiring, they back a truck up to Stanford and just shovel new grads onto it. Or their automated filters (that desperately try to get the candidate flow from 6,000 to 6) eliminate anyone that doesn't have a narrowly defined "right background". Better to just look for things like: grit, coachability/potential, focus, ability to reason about things across many orders of magnitude, ability keep a lot of aspects of a complex system visualized, and generally whether they can understand problems and come up with solutions. None of these involve playing "algorithm gotcha" or solving leetcode puzzles. EDIT: Easier said than done, though. I don't have a practical solution to how to do this with a multi-thousand candidate flow for each job posting.
- sjg007 5y agoStanford is good but also overrated. What this means is that should not pay out the nose for a Stanford grad.
- aidenn0 5y ago> Better to just look for things like: grit, coachability/potential, focus, ability to reason about things across many orders of magnitude, ability keep a lot of aspects of a complex system visualized, and generally whether they can understand problems and come up with solutions. If you want to hire 100 people then using "Got into Stanford and didn't flunk out" is a fairly cheap filter to approximate these things.
- c0nfused 5y agoIn the modern era where us news is ranking schools based on graduation rates it may be more fair to say that they were a successful looking junior in high school. https://www.usnews.com/education/best-colleges/articles/how-us-news-calculated-the-rankings https://www.usnews.com/education/best-colleges/articles/how-...
- aidenn0 5y agoIt used to be that having graduated from a selective school was a proxy for SAT, which was a proxy for IQ, and large companies legal departments tend to refuse to sign off on IQ tests as they are possibly biased against protected classes, so recruiting from selective schools was a way to launder recruiting people with high IQ scores.
- 908B64B197 5y ago> Or, who are literal geniuses but don't happen to have MIT, Stanford or UC Berkeley on their resume. Capable of research and invention, but no PhD. People who just were never discovered, mentored and given the opportunity to get on a rocket ship. Raw talent sitting there writing CRUD apps for some dopey company just limping along, who sometimes don't even know how good they are. I've scouted smaller/less known schools with great CS programs, so it definitely can be done. I know enough French to be dangerous so they sent me to the Polytechniques (Montreal, Paris, Swiss...) and got a great signal to noise ratio there. But it's a plane ride instead of an Uber... > Better to just look for things like: grit, coachability/potential, focus, ability to reason about things across many orders of magnitude, ability keep a lot of aspects of a complex system visualized, and generally whether they can understand problems and come up with solutions. None of these involve playing "algorithm gotcha" or solving leetcode puzzles. A degree from a solid school is a good predictor of that. Algo questions are used because it's a common vocabulary, everyone who matters just knows this stuff and it's possible to solve a problem in 45 minutes (vs giving a 2hour+ take home assignment). And it's really good at spotting people who, no matter how long you give them, won't be able to write a single line of code.
- zsmi 5y ago> We care about how fast you could learn new things that we haven't even thought of yet. Are you accurately able to determine that in a conversation that lasts less than an hour? If so, I am really curious how. I tutored people for years in college and I don't recall my first impressions being all that accurate. Accuracy would be even worse if I also had to guess the speed at which they would learn.