Blog

What to do when two candidates are equally good

Stuck between two strong candidates? Stop trusting your gut. Here's a hiring decision framework that helps startup founders pick the right person without coin-flipping.

You've been hiring for three weeks. You've screened resumes, run interviews, checked work samples. And now you're staring at two candidates who are both, by every measure you can think of, excellent. Same caliber of experience. Similar energy in the interviews. Comparable technical chops.

One slot. Two people who could fill it.

This is the moment most startup founders reach for gut instinct. Something about Candidate A's energy. A vibe from Candidate B's follow-up email. A feeling.

That instinct is the worst tool you could use right now.

Why gut feel fails when candidates are close

Research on hiring decisions is blunt about this. A 2008 study by Scott Highhouse in Industrial and Organizational Psychology found that decision-makers default to intuitive judgment even when structured, data-driven tools are available. The closer the call, the more they lean on instinct. And the more they lean on instinct, the more error they introduce.

This isn't a personality flaw. It's a pattern. When the data doesn't hand you an obvious winner, your brain fills the gap with narrative. "She reminded me of our best engineer." "He seemed more passionate." These stories feel meaningful. They're noise.

The numbers back this up. Schmidt and Hunter's landmark 1998 meta-analysis in Psychological Bulletin showed that structured interviews predict job performance with a validity of .51, while unstructured interviews land at .38. That gap widens in close-call scenarios, where the signal is weak and the stakes are high.

So if both candidates scored well in structured interviews, you already have good data. The question is whether you're using it, or overriding it with a hunch.

Go back to your scorecard

If you used a scoring rubric during interviews, now is when it earns its keep.

Pull up the scores. Don't look at the totals first. Look at the individual criteria. Where did each candidate score highest? Where did they dip? Are those dips in areas that matter for the first 90 days of this role, or areas that matter at month 12?

Most founders set up scorecards with equal weight across every criterion. That's a reasonable default for initial screening, but it's the wrong lens for a tiebreaker. Re-weight the criteria based on what this role needs most in the next quarter.

If you're hiring a first sales rep, objection handling matters more than CRM fluency. If you're hiring a backend engineer for a product with scaling problems, systems design matters more than clean code style. Adjust the weights. See if a winner emerges.

If you didn't use a scorecard, that's a separate problem. And it's worth fixing before you hire again. A structured process keeps candidates engaged and gives you better data.

Test for the differentiators that don't show up in interviews

Standard interviews surface skill and experience well. They're weaker at surfacing adaptability, learning speed, and how someone handles ambiguity.

These qualities matter more at a startup than at a 5,000-person company. Your role description will be outdated within three months. The person you hire will need to figure out problems you haven't anticipated yet.

LinkedIn's Future of Recruiting research consistently identifies adaptability and learning agility as top predictors of long-term hire success beyond technical skills. Ask yourself: which of these two candidates showed more evidence of learning something new, changing course, or operating outside their comfort zone?

If your interview process didn't surface that, consider adding a short exercise. Give both candidates a realistic problem they haven't prepared for. Not a trick question. A genuine scenario from your business. "Here's a situation we hit last month. Walk me through how you'd approach it." The answer matters less than how they think through ambiguity.

If you've never formally interviewed before, this kind of real-world exercise is also easier to evaluate than behavioral questions you're not trained to score.

Run a structured reference check

References get a bad reputation because most people do them badly. A five-minute call asking "Would you hire them again?" generates almost no useful information.

But structured reference checks, where you ask the same behavioral questions about both candidates, can surface patterns that interviews miss. How did this person handle a deadline they couldn't meet? What happened when they disagreed with their manager? How did they ramp up in the first 60 days?

The key is consistency. Ask the same questions for both candidates. Write down the answers. Compare them side by side.

You're looking for one thing: a pattern that distinguishes the two. Maybe Candidate A's references describe someone who thrives in chaos, while Candidate B's references describe someone who builds systems to prevent chaos. Neither is better in the abstract. But one of those profiles fits your company's current stage more closely.

Project forward 12 months

Stop comparing the candidates as they are today. Start comparing where they'll be in a year.

Your startup won't look the same in 12 months. The role won't look the same. The question isn't "who is better right now?" It's "who has more room to grow into what this role will become?"

This is where founder judgment is useful, because you know your roadmap. If you're about to expand into a new market, the candidate with cross-functional experience has an edge. If you're about to double your team, the candidate who has managed people before has an edge. If your next six months are heads-down building, the candidate who ships without needing direction has an edge.

Map each candidate against your actual plans, not an abstract idea of who's "stronger."

Stop using "culture fit" as a tiebreaker

84% of recruiters say culture fit is a key factor in hiring decisions. But when researchers dig into what people mean by "culture fit," they find almost no consistency. It usually translates to "I'd enjoy having lunch with this person."

That's not culture fit. That's similarity bias.

If you're going to factor in cultural alignment, define it in terms of behaviors and values, not vibes. Does your company value direct feedback? Async communication? Ownership without hand-holding? Those are measurable. "They'd fit in well" is not.

Only 25% of recruiting professionals feel confident in their ability to measure quality of hire. The reason is that most companies haven't defined what "quality" means in specific, observable terms. If you want culture fit to be a legitimate criterion, write down what it means before you use it to break a tie.

Make the call

At some point, you have to decide. And here's the uncomfortable truth: if you've done all of the above and both candidates are still neck and neck, either choice is probably fine.

The risk isn't picking the wrong person. The risk is spending another two weeks deliberating while both candidates take other offers. Top candidates don't wait. If your hiring process drags, the decision gets made for you.

Make the offer. Move forward. The structured process you used to get here means you have two strong options, and that's a better problem than most founders face.

Build a process that makes this easier next time

The hardest part of choosing between two candidates isn't the final decision. It's realizing you don't have enough structured data to make it confidently.

Bringboard gives you interview scorecards, candidate comparison tools, and a hiring pipeline that captures the signals that matter, so the next time you're stuck between two people, the answer is already in your data.

Start hiring with structure →

Ava Stavros

Head of Content at Bringboard

Recruited for three startups before any of them had an ATS. Spent too many hours wrangling spreadsheets, chasing scheduling emails, and explaining to founders why "just post it on LinkedIn" isn't a hiring strategy. Now writes about what growing teams get wrong about hiring, and how to fix it without buying software built for Fortune 500 companies.

Keep readingAll posts →