Lenny Rachitsky says companies waste time hunting for the "best" engineer by name instead of defining what they actually need. Stack-rank the specific skills and experiences required, then build your sourcing and assessment around those criteria. A clear definition of success makes it easier to find and close the right person.
Chapters
The mistake that most companies make is they'll say, hey, Lenny, who's the best product engineer you know? That is the worst question you can ask because you haven't spent like the time objectively identifying what great looks like. You kind of have to put these very specific characteristics or skills or needs for your team. What are like the skills and experiences you're looking for? You stack rank these things. You get really clear objectively before you talk to any candidate. It sets up your sourcing strategy. It sets up your pitch because you're asking questions like, why is this role important? What would success look like? It really helps you craft those things. It also helps you set up your assessment process of like what you're going to be assessing against. And it helps you think about kind of that close of like why this person and why this role is going to have big impact here. And then that's way easier for you to conjure up people that way than like this broad question of who's the best person.