The hiring process isn't designed to find the best candidate. It's designed to eliminate risk, and "pretty good" represents the highest risk of all.
I was in a debrief meeting at a major tech company where we'd just rejected a candidate who'd impressed everyone in interviews. The hiring committee had 12 people from different teams, all of whom gave positive feedback. The candidate had solid experience, good communication skills, and relevant technical depth. But the hiring manager said simply: "Not exceptional enough for the bar."
"What bar?" someone asked.
"The bar we're setting for this role," he replied. "We're not filling a position. We're building a team that can execute at the 95th percentile for the next three years."
That's when it clicked for me. We weren't looking for someone who could do the job—we were looking for someone who could redefine what the job could be.
The Paradox of the Almost-Perfect Candidate
The candidate we rejected that day exemplified the "pretty good" syndrome perfectly. They had no glaring weaknesses, but also no standout strengths. Their resume showed solid progression, their technical skills were adequate, and their cultural fit seemed fine. In a traditional hiring scenario, they'd be the perfect candidate. In our world? They represented maximum risk.
The fundamental misunderstanding about hiring is that companies want the "best" candidate. They don't. They want the candidate who minimizes regret. The "pretty good" candidate maximizes post-hire anxiety because they represent the middle ground between obvious hire and obvious no.
The Decision Matrix That Actually Matters
Here's what the hiring committee really evaluates:
Not technical skills vs. cultural fit
But potential for exceptional performance vs. risk of mediocrity
The candidate we rejected had checked all the standard boxes. Five years at a prestigious company, impressive educational background, clean code samples. But when we dug deeper, the pattern emerged: they'd always been a solid contributor, never a standout. Good at execution, not great at innovation. In our debrief, one interviewer noted: "They solve problems well, but don't seem to see problems that don't exist yet."
That's the killer. In tech, especially in AI/robotics, the ability to identify non-obvious problems is worth more than solving obvious ones efficiently.
The Hidden Cost of "Pretty Good"
The real cost of hiring "pretty good" candidates isn't their performance—it's the opportunity cost of not hiring exceptional ones. Every "pretty good" hire occupies a slot, consumes mentorship time, and represents a bet on incremental improvement rather than breakthrough performance.
I've seen this play out countless times. Teams hire the "pretty good" candidate, then watch as the exceptional candidates they could have hired go to competitors or start their own companies. The "pretty good" hire? They do their job adequately while the competition innovates.
The constraint isn't talent scarcity. It's the psychological comfort of hiring someone who won't embarrass you. But comfort is the enemy of excellence.
What "Pretty Good" Actually Means
"Pretty good" isn't a compliment—it's a euphemism for "not exceptional enough to justify the risk." These candidates have:
- Decent but not outstanding technical skills
- Good communication but lack compelling vision
- Solid experience but no breakout achievements
- Clean execution but no evidence of exceptional problem-solving
In our debrief, the VP of Engineering summarized it best: "I can justify hiring someone who's clearly exceptional even if they have some gaps. I can't justify hiring someone who's merely adequate, even if they have no obvious weaknesses."
The Exceptional Candidate Profile
Exceptional candidates don't just meet requirements—they redefine what's possible. They typically show:
Not linear career progression
But evidence of exponential impact
Not comprehensive skill coverage
But outlier-level performance in critical areas
Not consensus-building communication
But ability to articulate contrarian technical visions
An exceptional candidate who interviewed with us had spent two years at a startup that failed, but they could articulate exactly why it failed and what they'd do differently. Their technical skills were actually less polished than the "pretty good" candidate, but their understanding of system-level tradeoffs was orders of magnitude deeper.
The Process Reality
Here's what actually happens in hiring committee meetings:
Timing: 9 AM Monday morning, everyone's caffeinated and cranky about weekend emails.
Dialogue snippet:
"Weaknesses?" The hiring manager asks.
"Candidate demonstrates solid technical execution but lacks evidence of systems thinking," says the senior engineer.
"Communication is fine but not inspiring," adds the product lead.
"Seems like they'd fit in well, but..." the manager trails off.
That "but" is where the rejection gets decided. Not on capability, but on ceiling.
The Real Decision Constraint
The constraint isn't "do they meet the bar?" The constraint is "are we willing to bet our team's next three years on their potential for exceptional performance?"
This is why "pretty good" gets rejected most often. They represent the maximum risk-reward uncertainty. You can't build a high-performing team by avoiding downside risk—you have to bet on upside potential.
The hiring committee knows that "pretty good" candidates will likely perform adequately, but they also know that adequate performance in a high-growth environment eventually becomes inadequate. Better to leave the position open than hire someone who'll need to be replaced in 18 months.
The Cold Math of Hiring
Every hiring decision is a bet on future team performance. The math is brutal:
- Exceptional candidate: High potential upside, manageable downside risk
- "Pretty good" candidate: Moderate potential upside, maximum downside risk
- Clearly inadequate candidate: Low potential upside, clear downside risk
The "pretty good" candidate occupies the middle ground that maximizes decision regret. They're not clearly good enough to justify the hire, but not clearly bad enough to justify rejection. This ambiguity creates maximum anxiety in the decision process.
What Actually Gets You Hired
Exceptional candidates don't get hired because they're perfect. They get hired because they make the committee believe in their potential to create outlier results. They demonstrate:
- Evidence of identifying and solving non-obvious problems
- Ability to work effectively with better talent
- Track record of making good teams great, not just adequate teams adequate
In contrast, "pretty good" candidates try to minimize weaknesses rather than maximize strengths. This strategy fails because hiring committees aren't looking to minimize risk—they're looking to maximize potential return.
The Pattern Recognition Failure
The fundamental error "pretty good" candidates make is assuming that hiring is a rational, skills-based process. It's not. It's a pattern recognition exercise where committees look for evidence of exceptional potential, not evidence of adequacy.
I've watched hiring committees struggle to justify rejecting clearly capable candidates, but when a candidate is merely "pretty good," the decision becomes easy. The absence of compelling evidence for exceptional performance becomes the evidence for rejection.
The Reality of Team Construction
Building high-performing teams requires exceptional individuals who can raise the performance ceiling. "Pretty good" candidates lower it by occupying slots that could go to exceptional performers, consuming mentorship that should go to high-potential individuals, and creating a culture of adequacy rather than excellence.
This is why hiring managers would rather leave positions open than fill them with "pretty good" candidates. The long-term cost of mediocrity far exceeds the short-term benefit of adequacy.
The Verdict
The hiring process isn't designed to find the best candidate. It's designed to eliminate the highest risk candidates, and "pretty good" represents maximum risk. They're not exceptional enough to justify the hire, but not inadequate enough to justify easy rejection. This ambiguity makes them the most likely to be rejected.
The cold reality is that in competitive environments, adequacy becomes inadequacy over time. Teams that optimize for exceptional performance can't afford to hire people who represent the opportunity cost of not hiring exceptional candidates.
"Pretty good" candidates get rejected most often because they represent maximum regret—the hiring manager who chooses adequacy over waiting for exceptional will be second-guessed, but the one who waits and gets exceptional will be celebrated.
The system isn't broken. It's working exactly as designed.
— Johnny Ma
FAQ
Q: How can candidates avoid being categorized as "pretty good"?
A: The key is demonstrating exceptional potential in at least one critical dimension rather than adequate performance across all dimensions. Show evidence of identifying and solving non-obvious problems, creating disproportionate impact, or demonstrating contrarian thinking that led to measurable results. The goal isn't to be well-rounded but to be exceptionally capable in ways that matter for future performance.
Q: Why don't hiring committees just focus on skills matching?
A: Because skills matching optimizes for current adequacy while potential matching optimizes for future exceptional performance. In high-growth environments, the difference between adequate and exceptional performance compounds over time. Committees are essentially betting on which candidate will create the most value three years from now, not who can do the job today.
Q: What should candidates focus on to stand out from "pretty good" competition?
A: Focus on articulating your potential for exceptional performance rather than documenting adequate past performance. This means discussing the problems you haven't solved yet but could, the systems you haven't built but understand the principles for, and the innovations you haven't created but could enable. The goal is to make the committee believe in your ceiling, not your current capabilities.