The Hiring Mistake That Almost Killed Our Startup
We hired for credentials instead of curiosity. By the time we realized our mistake, we'd burned through 6 months of runway and had to rebuild the team from scratch.
We hired for credentials instead of curiosity. By the time we realized our mistake, we'd burned through 6 months of runway and had to rebuild the team from scratch.
In our Series A hiring sprint, we optimized for impressive resumes. Big-name companies, prestigious degrees, years of experience. On paper, our team looked incredible.
What Went Wrong
The engineers we hired were excellent at executing well-defined tasks. But at a startup, nothing is well-defined. We needed people who could operate in ambiguity, make decisions with incomplete information, and pivot without losing momentum.
Instead, we got a team that waited for specs that didn't exist, debated architectural decisions for weeks, and treated every technical choice as permanent.
The Turning Point
Our best hire was someone with two years of experience and no CS degree. She shipped a critical feature in her first week by making reasonable assumptions and iterating. That's when we realized our hiring criteria were backwards.
What We Changed
We now hire for three things: curiosity (do you ask good questions?), bias for action (can you ship with imperfect information?), and communication (can you explain your reasoning?). Technical skill is table stakes — we assess it, but it's not the differentiator.
The Result
Our team is smaller, less credentialed on paper, and 10x more effective. They ship faster, communicate better, and actually enjoy the chaos that comes with building something new.