Ch6 01: Stop Worshipping Résumés. Start Testing for Survival Skills.#

You just paid triple your budget to hire a director from a big tech company. He’s got the logo on LinkedIn. He’s got the vocabulary, the frameworks, the acronyms, the slide templates.

Three months in, you notice something uncomfortable. He writes beautiful strategy decks. But when you need someone to call a customer, hack together a landing page, or make a decision without data—he freezes. He keeps asking for resources you don’t have. He references processes that don’t exist. He waits for someone else to do the grunt work.

You didn’t hire a leader. You hired a logo.

This happens far more often than anyone admits. And it’s one of the most expensive mistakes early-stage founders make—not because the person is bad at their job, but because the job they’re good at doesn’t exist at your company yet.

The Platform Illusion: Achievement vs. Momentum#

Here’s something nobody at big companies talks about: a lot of what looks like individual achievement is actually platform momentum.

At a company with a hundred million users, a recognized brand, massive marketing spend, and a well-oiled distribution machine—things just work. Campaigns hit numbers. Products find users. Partnerships close. And the people running those functions get credit for outcomes that were largely pre-determined by the platform’s gravitational pull.

This isn’t to say they’re not talented. Many are. But their talent has been exercised in one very specific context: abundant resources, clear processes, specialized roles, and institutional momentum. Remove that context, and you’re looking at a completely different capability set.

A marketing director at a major e-commerce platform can point to campaigns that drove millions in revenue. Dig deeper: did she design the campaign from scratch, or optimize an existing template? Did she acquire the users, or did the platform’s existing traffic do the heavy lifting? Did she do the work herself, or manage a team of twenty?

At a startup, there’s no template. No existing traffic. No team of twenty. Just her, a laptop, and a credit card with a $500 limit. Same title. Completely different job.

The Stage Mismatch: “0 to 1” vs. “10 to 100”#

Big company people are trained for the “10 to 100” phase. Systems exist. Processes are established. Product-market fit is proven. The job: optimization, scaling, management.

Early-stage startups are in the “0 to 1” phase. Nothing exists. No systems to optimize. No team to manage. The job: survival—build something, find someone who wants it, don’t run out of money.

These are fundamentally different skill sets. They rarely overlap.

A CTO from big tech knows how to architect systems for millions of users, manage engineering teams across time zones, navigate corporate politics. None of that helps when you need someone who can ship a working prototype over a weekend using no-code tools and duct tape.

The “10 to 100” person asks: “What’s the process?” The “0 to 1” person asks: “What needs to happen by Friday?”

The “10 to 100” person wants a team. The “0 to 1” person is the team.

The “10 to 100” person delegates. The “0 to 1” person does.

This isn’t character judgment. It’s training. People get good at what they practice. Big company veterans practiced a game that looks nothing like yours.

Three Warning Signs of Stage Mismatch#

Spot these before they cost you six months and a year’s salary:

Sign 1: Process dependency. They keep asking “What’s the process for this?” when no process exists. In a big company, this is smart—follow established workflows. In a startup, there are no workflows. You invent them on the fly. If someone can’t function without a defined process, they’ll be paralyzed in your environment.

Sign 2: Resource requests. “I need a designer.” “I need a data analyst.” “I need a project manager.” At a big company, this is how things get done—leverage organizational resources. At a startup, this is how nothing gets done—those resources don’t exist. The person you need designs the slide themselves, pulls data from a spreadsheet, and manages the project on a sticky note.

Sign 3: Responsibility diffusion. When something goes wrong, they instinctively look for whose responsibility it was rather than just fixing it. In a big company, accountability structures matter. In a startup, there’s no structure. There’s just the ball on the ground, and someone needs to pick it up. Right now.

How to Actually Evaluate Talent (Forget the Résumé)#

Test 1: The “no resources” scenario. Describe a real situation from your startup: “You need fifty users to test a new feature by next Friday. Zero budget. No marketing team. No existing user list. What do you do?”

Listen carefully. If the answer involves building a plan, assembling a team, or allocating budget—big company answer. If it involves personal outreach, creative hustling, and scrappy tactics—startup answer.

Test 2: The ambiguity test. Give an intentionally vague problem: “Users are churning. Fix it.” No data. No context. No constraints.

Big company people ask for dashboards, reports, and team support. Startup people start asking: “Which users? When did it start? Can I talk to three of them today?” The startup person moves toward the problem. The big company person moves toward the process.

Test 3: Dissect the “past glory.” Ask about their biggest achievement. Then keep asking why until you separate personal contribution from platform contribution. “I grew our user base by 200%.” Why? “I launched a referral program.” Why did it work? “We had strong brand recognition and an existing base of two million.”

There it is. The growth came from the platform, not the program. The program was a lever, but the fulcrum was the company’s momentum.

Not everyone from a big company fails this test. Some genuinely drove results through personal initiative and scrappy execution. Those are the ones you want. But you have to dig past the logo to find them.

A Tale of Two Hires#

Company A spent months recruiting a VP of Engineering from a major tech firm. Premium salary, equity, the title. The VP arrived and immediately started building: an engineering process, a team structure, an eighteen-month technical roadmap. Within six months, the team grew from three to twelve. Burn rate tripled. And the product? It moved slower than before. More people meant more coordination, more meetings, more overhead. The MVP that three engineers could have shipped in a month now required cross-team alignment and sprint planning.

Company B hired a technical lead who’d previously co-founded a failed startup. No fancy logo. Salary: a third of Company A’s VP. He showed up on day one and asked: “What’s the most important thing that needs to ship this month?” He built the MVP himself in three weeks with open-source tools and a free-tier cloud host. When it broke, he fixed it. When users complained, he responded. When a feature was needed, he built it over the weekend.

Company B’s product was live and generating revenue while Company A was still debating their tech stack.

The VP wasn’t incompetent—he was mismatched. Running the “10 to 100” playbook in a “0 to 1” environment. That’s not his fault. It is the founder’s mistake for hiring him.

Four Pitfalls#

Pitfall 1: Hiring for confidence. Big company people are polished presenters. They sound authoritative, use the right jargon, feel reassuring when you’re drowning in uncertainty. But confidence is not competence. The person who confidently presents a six-month roadmap might be less useful than the one who nervously says, “I’m not sure, but let me try something this week.”

Pitfall 2: Hiring for your future stage. “We’ll need a VP of Sales when we scale, so let’s hire one now.” No. Hire for the stage you’re in. A VP of Sales with no product to sell, no leads, and no sales process will either build premature infrastructure or quit from boredom. Hire them when you actually need them.

Pitfall 3: Confusing domain expertise with stage expertise. Someone who deeply understands your industry is valuable. But if their experience is entirely within large organizations, they know what to build but not how to build it in your context. Domain expertise plus big-company habits equals frustration for everyone.

Pitfall 4: Equating team size with progress. Twelve people doesn’t mean twelve times the output. In the early stage, it often means twice the output at five times the cost. Communication overhead, alignment meetings, and coordination costs eat the productivity gains.

Reflect and Self-Diagnose#

Look at your current team. For each person, answer: if you removed the resources, the title, and the process—just them, a laptop, and a problem—could they still produce results?

If the honest answer for anyone is “probably not,” you have a stage mismatch. That person might be incredible at your next stage. But right now, in survival mode, you need people who produce output, not people who manage processes.

One more question: when evaluating candidates, what impresses you more—where they’ve worked, or what they’ve built with their own hands?

If it’s the former, you’re hiring logos. If it’s the latter, you’re hiring capability.

The résumé tells you where someone has been. It tells you almost nothing about what they can do when everything is stripped away. And in the early stage, everything is stripped away.

Hire for the bare floor, not the corner office.