Almost every founder who comes to me is hiring for a position that is already on fire. They will say, get me the candidate yesterday and I would have onboarded them already. I understand that pressure. A founder is taking calls at six in the morning and again at midnight, and a missing hire is a real weight on the whole team.
But after four years of startup hiring, I have learned something that is hard to hear in that moment. The candidate they are asking for, the flawless ten-on-ten who performs from the first day, is very often the reason the role stays open for months.
The candidate every founder asks for
The demand is almost always the same. If the candidate is a ten on ten, they will move. If the candidate is a nine on ten, it will not work for them. They would rather sit through a hundred more interviews than accept someone who is a nine and coach them up to a ten.
I understand where it comes from. In a startup of seventy people, everyone is doing real work, and one person who does not fit can hamper the whole team. The cost of a wrong hire is far higher here than in a company of ten thousand, where one or two people not performing is close to invisible. So founders try to remove all of that risk inside the interview room. The problem is that the risk does not actually live there.
What "best talent" actually means when you unpack it
When a client tells me they want the best talent, it sounds simple, but there is a very specific definition hiding inside it. They usually mean a candidate who comes from the exact same industry, who fits the budget, who matches the experience band, and who will start performing from the very first day.
The first three are reasonable, and they are things a good recruiter can deliver. It is the last one that quietly breaks the whole thing. Nobody, however perfect on paper, walks in and performs from day one, because they have not yet learned your product, your process or how your company actually sells. That part takes time, and pretending it does not is where the trouble starts.
The math nobody wants to hear
Let me put some real numbers on how narrow this already is. For one recent tech role, we sourced around two thousand profiles. That role carried six rounds of interviews. Out of all of it, four offers went out. Roughly one candidate in a hundred makes it all the way to an offer.
That funnel is the reality of hiring for a strong startup team, and it exists before anyone adds extra conditions. When a founder insists on nothing less than a ten on ten, they are shrinking an already narrow funnel even further, and then wondering why it is taking so long to fill.
I can take a nine on ten candidate and make them a ten on ten. That is the part founders skip.
Why even the perfect hire needs ninety days
Here is something I say often, and it applies even to the candidate who looks flawless on paper. On a target-based role, you have to give a person around three months before you can fairly judge their output. Expecting them to hit targets in the first fifteen days is not a high standard, it is a misunderstanding of how anyone ramps. A person has to understand the product before they can sell it.
This is also why hires that look perfect on paper sometimes fail. In the interview you are checking a salesperson's pitch, their connects, the revenue they generated somewhere else. What you cannot see is how they will feel about your specific product once they are inside. When there is a mismatch there, it surfaces after joining, not before. The way we reduce it is to be blunt from the start, to describe the real role plainly and help the candidate picture the actual work, so any back-out happens early instead of three months in.
The nine-on-ten candidate you are overlooking
My honest view, as someone who has spent years mentoring a team, is that a nine on ten is not a compromise. It is a ten on ten who has not been developed yet. I have taken candidates who were an eight and, with guidance, watched them become the strongest people on the team. That is a large part of what recruitment actually is once you stop treating it as slotting a resume into a seat.
I once placed a candidate who held an offer from a large product company at twenty-four lakhs, while the startup I was hiring for could offer around twenty. On paper he should have taken the bigger number. He wanted the growth a smaller company gives you, and I could show him what had happened to people I placed before, many of whom reached one and a half times their package within three to six months. He joined, and that is the difference between filling a role and building a team. You are not placing a candidate, you are placing an asset, and the founders who understand that end up hiring faster than the ones still waiting for a flawless ten.
Give a new hire around three months to learn the product before you judge their output.
Say plainly what the role really involves up front, so a mismatch surfaces early rather than after they join.
Move quickly on feedback. A slow response loses strong candidates who have other offers in hand.
Weigh coachability. A committed nine can be mentored into a ten, and often becomes your most loyal hire.
About the author
Anjali Kandhari leads recruitment at ConsultBae, where she has spent four years building startup teams from scratch across tech and non-tech roles. She works most closely with the candidates in the final rounds, because that is where a hire is won or lost.
You are not filling a seat. You are building a team.
Tell us the role and the bar you actually need, and we will bring you pre-vetted candidates worth building around, not just names on paper.
Talk to our recruitment team
