How to Interview for Builder DNA: What I Learned Hiring at Intugine
The Problem With 'Smart'
Early-stage startups have a consistent hiring mistake: they optimize for intelligence and credibility — IIT pedigree, FAANG experience, top-tier MBA — and are repeatedly surprised when these hires struggle in the zero-to-one environment. This isn't a failure of the people. It's a failure of the matching process. Intelligence is a necessary but completely insufficient condition for building.
What you need in the first 20 hires of an early-stage company is something different: builder DNA. The ability to operate in ambiguity, own outcomes (not just tasks), and find creative solutions to problems that have no documented playbook. Here is how I learned to find it.
The Signals That Actually Matter
Signal 1: What Have They Built Unprompted?
The most reliable signal of builder DNA is a history of building things that nobody asked them to build. Not projects assigned at a job. Not coursework. Not hackathon projects done for a prize. What did they build because the problem bothered them and they couldn't not build it? This could be a side project, a community they organized, a process they invented at a previous job, a tool they made for personal use that turned into something others used.
The key question I ask: "Tell me about something you built that wasn't part of your job description." The quality of the answer — and the emotion with which they describe it — tells you almost everything.
Signal 2: How Do They Handle Constraint?
Give a candidate a real, current problem from your company — not a case study, not a hypothetical, an actual problem you are struggling with right now. Give them 10 minutes to think about it. Then ask: "What would you do with zero budget, two weeks, and only the resources you can find internally?"
Candidates with builder DNA lean forward. They start making assumptions, asking clarifying questions, breaking the problem into parts. They propose ugly, practical, immediate solutions alongside their vision for the better long-term answer. Candidates without builder DNA tend to either propose theoretically perfect solutions that require resources they don't have, or freeze entirely because the constraints feel unreasonable.
Signal 3: Do They Know What They Don't Know?
Intellectual honesty about the edges of one's own knowledge is a builder trait. Builders know that they don't know everything — because they've been in enough situations where they had to figure things out that they didn't originally understand. Ask a candidate about a domain adjacent to their core expertise. Listen for "I'm not sure, but here's how I'd figure it out" versus "I know that" followed by a shallow answer. The former is a builder. The latter is often a credential-holder.
The Interview Question I Always Ask
"Tell me about a time you were given a goal but no path to the goal. What did you do?" The answer reveals everything: how comfortable they are with ambiguity, whether they take initiative or wait for direction, how resourceful they are, and — perhaps most importantly — whether they can tell the story of their own thinking.
The Hires I Got Wrong
The worst hires I made at Intugine came from over-indexing on pedigree and under-indexing on these signals. Every single time, we hired someone with a brilliant resume who was fundamentally a coordinator — someone who could execute a defined plan brilliantly but could not generate the plan. In a startup with an undefined roadmap, coordinators without builders upstream of them are expensive and demoralizing.
The best hires I made were people who were slightly underqualified on paper but had unmistakable evidence of building things on their own initiative. Almost without exception, they outperformed their resumes within 90 days.