Live data from Hacker News

You don't want to hire "the best engineers"

otherbranch.com

241–250 of 326 posts

Re: You don't want to hire "the best engineers"

#241

Earlier quoted context omitted.

The market is definitely not dead. It started warming up last summer and has continued to do so throughout 2025. But the market is two-tiered in a way it hasn't been before, particularly w.r.t. remote hiring. Almost all engineers want remote jobs and a small number of employers offer them, so the remote job hunt still puts employers in the driver's seat. But (good, senior) engineers hold the cards right now for in-of…

No offers here, local or remote. Hoping Section 174 fix helps.

To where are you local, what are your desiderata, and what does your resume look like?

I can take a look privately if you'd like, or publicly here if you want broader opinions / to serve as a data point for others.

Re: You don't want to hire "the best engineers"

#242

Earlier quoted context omitted.

If you don't mind me asking, what's the role?

AI Engineer. Lots of candidates that want to be one but not many with actual experience, is the problem I’ve heard.

Honest question: if you'd hired someone who wanted to be an AI Engineer and had plenty of experience with general software engineering, and was of roughly the median quality of the engineers you've hired for other positions, do you think you'd be better or worse off than you are now?

Re: You don't want to hire "the best engineers"

#243
post #170
post #107

Earlier quoted context omitted.

Hire people on the way up. 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 ten…

Do you have any advice for how to suss out someone's hunger, drive, and scrappiness during the hiring process?

Verifiable evidence of them learning key new skills on their own, building passion projects (ideally somewhat comparable to what your startup needs), taking work to the finish line, etc.

Press (politely) for extra details via follow-up questions. Make it easy for the legitimate doers to share specifics of what they've done and learned, while the posers get vague in a hurry and change the subject.

Re: You don't want to hire "the best engineers"

#244
post #235

Not mentioned enough: watch out for engineers (or any hires) who will take zero interest in helping the business succeed. You can try and hire for brains and experience, say. And have your business constantly undermined by empire building, "just collecting a salary", resume building, and other popular nuisances. Attitude and alignment matters. If you are yourself "empire or resume building", nevermind, carry on.

> watch out for engineers (or any hires) who will take zero interest in helping the business succeed

To my experience, 80% of software developers are like this. May be each 5th bothers to ask "what are we building and for whom?"

Re: You don't want to hire "the best engineers"

#245

It brings Steve Jobs' quote to mind: "It doesn't make sense to hire smart people and then tell them what to do. We hire smart people so they can tell us what to do" Companies who generically look for "the best engineers" think their problems will be solved if they can just hire someone smart and tell them what to do. They say they want "the best engineers" but then their job descriptions and interview processes screa…

> We hire smart people so they can tell us what to do Or from Bell Labs: "How do you manage a bunch of geniuses? You don't" > Companies who generically look for "the best engineers" If you need "the best" then your system is (most likely) too complicated and you're going to have a hard time keeping "the best" as their work becomes frustrating. > The best engineers will tell you why your architecture is wrong, why you…

>These are "I'm thinking out loud" phrases.

Not just that, it's also "I want to know what your opinion and reasoning is on this as well" This has often led to some of the most productive conversations of my career.

Re: You don't want to hire "the best engineers"

#246

Earlier quoted context omitted.

It's always been the case that FAANG or whatever are not always the "best" home for the "best" engineers. Many do not/did not feel comfortable there, especially as they became more and more corporate and slow. But unfortunately the answer now is that "best engineers" can't work there either because the layoff / employment-squeeze is in full swing. You're right that the equity packages offered by startups to engineers…

Large corporations are probably the worst place actually. You get slotted into some random project treadmill (which will be completely different from whatever position you interviewed for) where most of the decisions are made by middle managers at least one or two levels above you. Going out of your way to solve problems will be ignored at best and my even result in a reprehend. These places are for people who hate t…

Top Talent won't be leveled such that PMs can be 1 or 2 levels above. They'll be high enough that the project plan heavily consults them from inception.

Re: You don't want to hire "the best engineers"

#247

Earlier quoted context omitted.

The only addendum to this I'd add is the best engineers rarely have to go through the hiring process in a meaningful way, it's usually someone recognizes them from a previous job and vouches heavily for them. 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.

This is a good addendum. Do you mind if I add it to the post (credited, of course)?

I'm not the poster you replied to, but as a recently retired multi-decade serial tech startup founder of the old-school bootstrap type - the addendum I'd add is what I now teach to young entrepreneurs: Assuming you're a first-time founder whose not playing the high-profile "raise more/spend more drag race" then accept you cannot hire "the best" engineers. You simply don't have the capital or reputation to recruit proven, top-notch talent. So, the only way to win is to play the game differently.

* Aside from a random, serendipitous surprise (which you shouldn't count on), early on the only proven "A players" you're going to have are your co-founders - which is why you chose them and gave them a huge chunk of equity. So you're going to have to get good at the art of hand-crafting a team that can win out of B and C level players. Doing this is hard but it's a tangible skill you can develop if you consciously work at it. They key is developing the knack for spotting raw, undeveloped and emerging talent. Of course, experience over time is the best way to get the knack but there are shortcuts. Always ask your circle of experienced advisors to tell you about times when they've seen someone emerge as a star despite starting from average (or below) expectations. Ask what that future star was like before and probe deeply on this. Ultimately, just being aware this is something you need to do and focusing on it can go a long way.

* Since you can't recruit enough star talent to win playing the game you wanted to play or using the strategy you'd planned, you have to adapt. Be willing to change your game, strategy or approach based on the unique talents and abilities the team you can recruit has. This is how great coaches can still win even with 'B-level' random talent.

* Be willing to accept unconventional, incomplete or flawed candidates if they have above average talent in one or more domains that matter to your unique value prop. Maybe you've figured out there's a backdoor way to win by making a product which doesn't have all the checkbox features but is fr faster than any other alternative at a couple critical things - and your hypothesis is that for some set of customers that will be enough to overlook your lack of features. Then you hear about a dev who's "the best goddamn high-perf optimizer I've ever seen" but after finding and talking to him, you learn he's got an uneven, checkered resume, has a felony record and can't work or live within 500 feet of a school - which is probably why he's available to start immediately if you're willing to have a chat with his parole officer.

Okay, maybe it's not that bad but the point is, you don't have the luxury of being inflexible. Back in the 80s I hired a talented engineer who was openly trans - and this was in a fairly small mid-western city. Times were very different then and it caused significant problems with other employees and even our landlord but I managed the downsides and this person delivered some incredible code that helped our launch product shine. Since times are (fortunately) different today, let's update the example. Maybe today's deeply flawed but weirdly-gifted-in-one-useful-way candidate comes to the interview wearing a MAGA hat and inquires if their licensed hidden carry firearm is going to be an issue in the office. Are you a good enough coach to extract winning results from a random team of flawed players with some unique gifts which are only partial, potential or still emerging? Can you craft a winning team by thinking different and digging deeper than anyone else through the bottomless pool of candidates who couldn't pass the first screen at Google or that hyper-funded AngelList-darling startup everyone's buzzing about? Because there are gems buried in that mountain of mediocrity if you can find and polish them.

Re: You don't want to hire "the best engineers"

#248

Earlier quoted context omitted.

In hindsight, would you have stayed at Google?

Probably. I was going crazy working there, I grew to really dislike it. But from a purely selfish $$ POV, it's likely I would have got caught in one of the rounds of layoffs or been able to take this latest voluntary layoff package. Unless the frustration led to bad performance reviews, which could have happened. My mental health would have suffered, but holding on another 1-3 years would have probably led to me bein…

My story is the same as yours, and the same timing, but it was Meta. I missed out on a LOT (!!!!) of money by quitting, but I don't regret it at all. The place was rotten.

I'm actually now at Google and things are just fine and peachy.

Re: You don't want to hire "the best engineers"

#249
post #13

> 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…

The only addendum to this I'd add is the best engineers rarely have to go through the hiring process in a meaningful way, it's usually someone recognizes them from a previous job and vouches heavily for them. 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.

If you're not talking about compensation, you're leaving money on the floor. I'm no "best engineer", but I've never failed to get meaningful bumps to my starting comp by giving some pushback on a company's initial offer. Most of the time the only leverage you'll have is the innate friction in the hiring process: By the time a company has extended an offer to you, they've committed non-trivial resources convincing people you're the right pick. It's a PITA to throw all that away, so something like "I'm very interested your offer. For $(offer+X) I could sign today" or "I like your company, but you're offering a bit below market rates. (A contractual pay bump after 3/6 months, an additional week PTO, whatever) or an extra $X would make me willing to accept immediately." will likely work. This should be ideally in person, or at lease over the phone or VOIP, so you have the opportunity to smooth things over and retreat with your tail between your legs if they take it very poorly, but I've never seen that happen. Worst I've heard of is a firm "Sorry, that's the offer, take it or leave it", leaving the applicant no worse off than they were before.

Not negotiating compensation just means you're paying a conflict avoidance tax.

Re: You don't want to hire "the best engineers"

#250

Earlier quoted context omitted.

> leave the ego at the door and not talk about compensation or try to demand remote work This makes it sound like these things are written on stone tablets and we just need to accept them as is. They are businesses buying labor. Everything is negotiable. Talking about those things is not “ego” it’s a perfectly rational thing to do. Whether you should be paid $50k or $500k is not a law of nature but a compromise betwe…

Rationality on an individual level is not the same thing as what produces the best long-term outcomes for both parties. On an individual level, bringing up comp immediately significantly reduces your chances of being moved forward. It shouldn't, but it does. See this other post from us: https://www.otherbranch.com/shared/blog/would-you-still-hire...

You have no leverage "immediately". You bring up compensation at the last minute, when the company extends its offer.
Post reply on HN