Don't forget surfboards!
This was a great post, Alex. Thanks for sharing! Hunger and high agency are such important traits in every startup hire.
And yeah, high agency is really trendy at this moment in the startup sphere, but hunger is not talked about enough IMO. Maybe because it's too obvious to be even worth mentioning.
edit: interestingly, that happens even in comments..
I’m on HN a lot, and I usually tend to passively browse Who’s Hiring and interesting looking YC ads. Outside of that, I don’t think I would pursue a startup job through job search sites. I would most likely want to find projects I think are neat and start to research and maybe contribute if they have OSS projects, then do individual outreach. I’d probably also start blogging and posting more so people can see if I am a fit for them. Agents may be involved, but only insomuch as I could spend more time doing human stuff like writing, listening, and ideation.
I hope this helps a CTO find a good candidate. I’m personally not on the market right now, but AMA if you want help finding similar folks.
Engineers follow a pareto distribution. In a normal sized team, with a typical hiring funnel, you will have a few high performers, who are responsible for most of the team's productivity. If you can only hire one person from that team, then it is more likely than not that you will hire someone with productivity below the team's mean. At an early startup, this could be a death sentence. Especially since we typically reason and plan in terms of means, so it may come as a surprise that your single engineer is less productive than the mean of most teams that you have worked with.
The other reason (also not mentioned) is that you eventually want to scale hiring. That means that you need to have people, that you have hired yourself, hire more people on your behalf. The best people (A players in the metaphor) don't have imposter syndrome, they know how good they are, and how good they aren't. They want to work with other talent, that makes their lives easier, more interesting, and less stressful than covering for/babysitting other people. It's also the only way they can grow from where they are at. So they can be trusted to hire more A players, out of self interest.
The median engineer (let's call them a B player) often knows about where they stand as well, and often they will have started to diversify their skillset into organizational politics. They intuit: hiring people more competent than them gives them less leverage, and they are pretty good at zero-sum status games, that's their edge. They don't want true competition, so they hire C players.
So the reason you want to start with the best is because it's the only way to ensure you can move fast when you need to, and the best way to keep the organization effective long enough to exit. All organizations decay into incompetence, but hopefully you can get yours and get out before that happens.
I would extend that even further, I'm a fan of the idea that you should thoroughly vet the founders for excellence if you want to maximize your chances of ending up at a great startup. Like with your "A player" engineers example, founders need to be exceptional if they want to attract great talent to work for them. So if you're pretty unimpressed with them as you're getting to know the company, the likelihood that the team they hired makes up for that deficiency is very low, and you'll end up around non-A players.
But this candidate profile is the best anywhere. It’s also a bit like writing an article and saying “you shouldn’t try to buy shares in the most well known tickers, try to buy things that are undervalued but will be great in the future”. Yeah, but also duh.
1. Having FAANG-level budgets to hire vs three packs of ramen and a spool of string at the average startup makes it so that you have to learn how to spelunk through less obvious talent, you're looking at very different pools of potential hires.
2. This is written with the first-time YC-style startup CTO in mind who might be in their early 20s and might have never had to interview a single person until that point. I remember none of this being obvious to me the first time around, and I'm still refining my thinking all the time as the projects and markets change
akurilin•1h ago
kekqqq•55m ago
akurilin•29m ago
Centigonal•22m ago
One thing I'd add re: "non-obviousness." There are also tarpits; people who make you think "I can't believe my luck! How has the market missed someone this good!?" At this point, I have enough scar tissue that I immediately doubt my first instinct here. If someone is amazing on paper/in interviews and they aren't working somewhere more prestigious than my corner of the industry, there is often some mitigating factor: an abrasive personality, an uncanny ability to talk technically about systems they can't actually implement, a tendency to disappear from time to time. For these candidates, I try to focus the rest of the interview process on clearing all possible risks and identifying any mitigating factors we may have missed while getting the candidate excited to work with us assuming everything comes back clean.
akurilin•9m ago
Do you find that in the tarpit scenario they will typically have a work history hinting at these quirks?