I was prepared to straight up fight with this author until I actually read what they were saying: 1. Don't hold infeasibly high standards when you're starting up. Time is more precious than than anything (you can't spell "scrappy" without "crappy"). 2. Be more intentional than a lottery-ticket financial plan when it comes to evaluating what traits matter and at what priority order. If everything is a priority, nothin…
Great talent knows how to scale mediocre talent, but you should do so after building that initial core team.
You don't want to hire "the best engineers"
101–110 of 326 posts
Re: You don't want to hire "the best engineers"
#102When the average pre-revenue startup says:
> "We need the best engineers"
What they really mean is this:
"We really need ex-FAANG engineers from Ivy League, Stanford, MIT and Oxbridge for close to below market rates."
*6 months later:*
"We have a skills shortage of the best engineers"
What they really mean is this:
"No one wants to accept our below market price offers, even with 0.01% equity which may be worth something one day."
If the startup cannot offer a competitive compensation to FAANG or the big AI companies, just walk away. Likely dodged a bullet anyway.
Re: You don't want to hire "the best engineers"
#103> The best engineers make more than your entire payroll. They have opinions on tech debt and timelines. They have remote jobs, if they want them. They don’t go “oh, well, this is your third company, so I guess I’ll defer to you on all product decisions”. They care about comp, a trait you consider disqualifying. They can care about work-life balance, because they’re not desperate enough to feel the need not to. And ho…
I say this because if you're going through the hiring process like a chump, I'd leave the ego at the door and not talk about compensation or try to demand remote work on a desirable position.
Re: You don't want to hire "the best engineers"
#104Re: You don't want to hire "the best engineers"
#105Earlier quoted context omitted.
it's more like short term gain vs long term gain. experienced engineers can design an architecture that will allow you to scale cheaper and faster in the future, at the high initial cost. it will be cheaper to maintain, better for security. depends at what point your business is at the moment of hiring and what you plan to do with the product. do you need volume or quality (both variants are right)?
If your business is going to cease to exist in 4 months, who cares about scalability? Pay the interest when it comes due and when you can afford it. If someone is serious about building a company they will be okay with that.
Re: You don't want to hire "the best engineers"
#106Re: You don't want to hire "the best engineers"
#107I was prepared to straight up fight with this author until I actually read what they were saying: 1. Don't hold infeasibly high standards when you're starting up. Time is more precious than than anything (you can't spell "scrappy" without "crappy"). 2. Be more intentional than a lottery-ticket financial plan when it comes to evaluating what traits matter and at what priority order. If everything is a priority, nothin…
I think the post is getting at the idea that pedigree is not a reliable predictor of talent, but because it's a convenient and standard one, everyone uses it (which in turns reduces its usefulness). It's harder for a recruiter to fully experience the perils of hiring mediocre people, but they're definitely at ground zero for "what's on a resume is mostly not representative of actual talent".
Hire people who are going to do their best work ever, for you, after having partially but not fully mastered everything you want, via their previous jobs. It's easy to evaluate a resume. It's harder -- but not impossible -- to assess potential. Working inside a big tech company for six years, I saw that PM hires were done almost entirely on pedigree: find me another Stanford grad. These tended to produce a lot of fast exits as well as some comically bad and totally predictable fails.
Engineering hires were done on hunger, drive, scrappiness (and networks). They fared better.
Re: You don't want to hire "the best engineers"
#108Earlier quoted context omitted.
Engineers don't really care about equity anymore because they've been burned so many times. The big payouts from a successful company are not necessarily guaranteed the way they were pre-2015 or so. It has become too common for there to be behind-closed-doors dlilutions and investor-only exit opportunities. It has become very unwise to trust anything beyond real cash wired to your bank account.
Every single solitary person I've personally known who worked at a successful startup got screwed out of their equity somehow. Literally every single one.
Re: You don't want to hire "the best engineers"
#109I worked for 5 startups before I went back to grad school and then entered academia; it was over a quarter century ago but I think some of the lessons remain valid. The best startup I was at was one where four engineers who knew each other had dropped out of a big company and started with a consulting project, developing the first version of the product for an early customer (a national lab) using FPGAs. Then they go…
Re: You don't want to hire "the best engineers"
#110Earlier quoted context omitted.
Great talent knows how to scale mediocre talent, but you should do so after building that initial core team.
Why ever hire mediocre talent?