Hiring for Altitude, Not Pedigree

I once coached a founder who was about to hire his dream VP of Engineering. Let's call the candidate Alex. Alex had a pristine resume. FAANG leadership experience, a degree from a top engineering school, and a track record of shipping massive products.

The team was ecstatic. The board was impressed. They made an offer Alex couldn't refuse.

Six months later, the company was paralyzed. Alex was brilliant at managing large, established systems with infinite resources. But in a 50-person company where the map was still being drawn, he couldn't operate. He spent his time creating process documents for problems the company didn't have yet, while the actual product stalled.

The team's morale cratered. Alex was eventually managed out, but the damage was done. They lost nearly a year of momentum.

The Gravity of a Mis-Hire

We obsess over the financial cost of a bad hire. The recruiter fees, the salary, the severance. But that's table stakes. The real cost is measured in lost momentum, broken team trust, and squandered opportunity. In a software company, that is everything.

A single mis-hire at a senior level creates a gravity well. It pulls energy and focus away from customers and product. Instead of building, your best people spend their time managing up, containing chaos, or cleaning up messes. The organization becomes inward-looking.

I’ve seen it kill product launches and derail entire funding rounds. The cost isn't a line item on a spreadsheet. It's the future you could have built but didn't. It's the quiet departure of your two best engineers who got tired of the friction.

That is a catastrophic loss.

Resumes Are Rear-View Mirrors

The mistake that founder made with Alex is one I see software leaders make constantly. They hire the resume, not the person. They hunt for pedigree because it feels safe. It's an easy story to tell the board. "We got the person who ran X at Google."

But a resume is a record of performance in a past environment. It is not a predictor of performance in a future one.

Working at a 100,000-person company is a completely different sport than working at a 100-person company. The skills that lead to success in a highly structured, resource-rich environment are often liabilities in a scale-up. Large companies reward people who navigate complexity. Startups reward people who create clarity from chaos.

Pedigree hunting filters for conformity and political skill. It doesn't filter for resourcefulness, resilience, or first-principles thinking. You end up with people who know how to operate a machine that's already built, not people who know how to build the machine in the first place.

Screening for Altitude

A few years after the Alex incident, I saw another founder make a very different kind of hire. He needed a Head of Product. One candidate, let's call her Sarah, came from an unconventional background. She had spent five years in logistics, optimizing shipping routes for a non-tech company. On paper, she had zero SaaS experience.

But in the interview, she didn't talk about features. She talked about systems. She asked relentlessly clarifying questions about the business model, the customer's real-world problems, and the economic levers behind the product. She whiteboarded the flow of information and incentives, not just the user interface.

She got the job. Within a year, she had transformed the product by focusing on a core, underserved workflow that unlocked massive value. She could see the entire system, not just the screen.

Sarah had what I call "altitude." She could zoom out from the immediate feature request and see the whole map. This is what you must screen for. The most predictive trait of a successful hire is not what they know, but how fast they can learn and apply judgment to what they don't.

Stop asking people to solve brain teasers or describe their past accomplishments. Give them a real, messy, and incomplete problem your team is currently facing.

Don't look for the right answer. There probably isn't one.

Look at the questions they ask. Do they seek to understand the constraints? Do they challenge your assumptions? Do they simplify the problem to its core components before trying to solve it?

Look for how they think, not what they know. That's where you find the people who can build the future, not just manage the past.

Your Turn

The best hiring principles are usually learned through scars. The lessons from the people who looked perfect but failed are often more valuable than the successes.

What hiring lessons have you learned the hard way? Reply and let me know.