9 ms·
It's not only the applicants who have limited time. The startup founders are also time constrained. You can't found a successful startup if you spend 10+ hours
by chatmasta 11y ago
It's not only the applicants who have limited time. The startup founders are also time constrained. You can't found a successful startup if you spend 10+ hours a week interviewing potential employees.
I suspect much of the initial bias and "hard line" preferences are due to a startup's unwillingness to spend inordinate amounts of time interviewing candidates to find that one diamond in the rough.
Imagine 4 of every 10 "academic programmer" candidates are a good fit, and 6 of 10 "product programmer" candidates are a good fit. Why waste time interviewing 10 academic programmers, for a max hit rate of 40%, when you could focus solely on product programmers and get a max hit rate of 60%?
This data certainly suggests that different founders have their own biases and preferences for what makes a "good programmer." Most of them probably realize they are pigeonholing and could be wrong, but they're willing to risk that for more efficient interviewing and a high hit rate.
Stick with what you know if it's "good enough." Optimally, as a founder you can already identify multiple potential early hires just from your own network. If you have the right background and connections, you can hire your first couple employees without doing a single interview.
Time is money. Interviews take time and cost money.
- ammon 11y agoThis is definitely true. The filters that companies and recruiters use mostly trend in a meaningful direction. There are a higher percentage of good programmers among MIT grads than SUNY Potsdam grads. But this fact does nothing to help the good programmers who look bad on paper who everyone is ignoring. This is precisely the problem that we're trying to fix with Triplebyte. We want to make actual technical evaluation (not credential evaluation) cheap and accurate, so we can just interview everyone.
- sillysaurus3 11y agoThe filters that companies and recruiters use mostly trend in a meaningful direction. There are a higher percentage of good programmers among MIT grads than SUNY Potsdam grads. Imagine how mistaken that would sound if you substitute "startup founders" for "programmers." The reason you feel company filters are anything except random noise is personal bias. It's disheartening that your article notices that company preferences are essentially random noise, and then you don't really internalize that fact or take it to its logical conclusion: Interviews where programmers do anything except work-hire tests tuned to the signal that the companies want are doomed to fail. And it's almost impossible to do a work-hire test in an interview. A real work-hire test. The type of test where you actually do some work and then show that yours is effective. We're so backwards that people probably read this and think I'm saying whiteboard work or something stupid like that. No. Real, actual work. The problem you're working on can be fake, but the problem needs to be literally the same type of thing that the company does on a day-to-day basis. Want a 100% success rate? Do that, and then don't pay attention to anything but the results. Including whether the candidate has an MIT degree, or any degree at all. If you actually set up a work-hire test, a real one, and then stop asking about all the other stuff that doesn't matter, then you will get a 100% rate. Again, you have to tune the test to what the company is looking for, but that's not hard. "Here is an iOS app. Find and fix these bugs, then add a new feature."
- dmoy 11y agoHow do you do a work-hire test for someone who already has a job, and is not allowed to work on another company's stuff?
- vonmoltke 11y ago> The problem you're working on can be fake I'm assuming if it was a fake problem, it wouldn't be something the other company could actually use.
- ryandrake 11y agoIt's not about what they could use. It's about what they own and where it's going. If your employment agreement states that any code you write belongs to your employer and that you're not allowed to share company code with others, then a work-sample test essentially asks candidates to violate their current employment agreement.
- vonmoltke 11y agoTaking that interpretation would mean any interview where you write code would violate your employment agreement.
- sillysaurus3 11y agoEmployment agreements like that are certainly frustrating. I've had experience with a few. One thing to realize is that your employer can't really retaliate. The hypothetical iOS app I mentioned is set up for one purpose: to let candidates show they can do work the company is looking for. Not only will the code be thrown away, but it wouldn't make any sense to use it.
- s73v3r 11y agoI would say that if the new company is not in the same section of the industry, than enforcing that agreement is entirely unreasonable.
- 11y ago
- LordHumungous 11y ago>The filters that companies and recruiters use mostly trend in a meaningful direction. There are a higher percentage of good programmers among MIT grads than SUNY Potsdam grads. Uh are you sure about that? Google's experience seems to be that academic achievement is not a good predictor. And they know a thing or two about hiring. http://qz.com/180247/why-google-doesnt-care-about-hiring-top-college-graduates/ http://qz.com/180247/why-google-doesnt-care-about-hiring-top...
- Retric 11y agoInterviewing is ridiculously important for any small company. The problem is most people have little idea how to do anything except look for people like them.
- ammon 11y agoPrecisely. It's a flaw (shortcut) in the human brain, with effects far beyond programming interviews. This is why structuring interview evaluation is so important
- Matt_Mickiewicz 11y agoFortunately, the solution to the problem is super cheap. $20 buys you a copy of "The Who" book, which is a proven, scalable system with specific questions to ask at each step of the interview process....
- TimPC 11y agoMany successful people who've built and exited massive start-ups have suggested that it's worthwhile on the start-up side to spend 25% of your time on hiring when you're actually hiring as so you can easily get above 10 hrs a week given a full time role on this and have that be a good result. Optimizing to minimize the cost of hiring an early engineer is definitely solving the wrong problem, given the early engineers are almost as crucial to success as founders. Unfortunately, hit rate is also often the wrong variable from the company end: if you interview an academic programmer to confirm their product programming skills you generally get someone better with a larger skill set than if you focus in the category you want for the skills you want (early-stage you generally want breadth over depth for many roles). It clearly sucks for people on the receiving end of the low hit rate interview, but I'd caution start-ups against optimizing their process for the wrong things.
- lpolovets 11y agoMy data as an investor supports your point. For a lot of young startups -- especially those with <=5 people -- people often spend >=10 hours per week on recruiting. Not every person at the company will spend that much time, but a lot of founders spend a huge chunk of their week on recruiting.
- nostrademons 11y agoI talked to the CEO of a high-growth unicorn once and he said his job description is basically a glorified recruiter. Pretty much everything he does is related to getting the right people on board his startup.
- masonoise 11y agoAbsolutely. At my last startup I was VP of Engineering and at one point I tracked my time and was spending 45% of my week on recruiting activities. But that was necessary, both to protect my team's time and to grow. You can't hire good people without putting in the time to find them, talk to them, and convince them to join if you like them. And that effort can't be outsourced to a recruiter, either, if you want it to be productive.
- deleted 11y ago[deleted]
- LordHumungous 11y agoThat would be true if you could show that candidate "types" are actually meaningful distinctions and not just the founder's first impression based on limited data. I think that's a stretch.