The Three Questions That Reveal Your First Engineer
Most founders evaluate first engineers on technical skill — and miss the thing that actually breaks early teams: judgment. These three interview questions cut through the résumé and show you how someone thinks when things get hard.
1:25
Transcript
Your first engineer will either save your product or quietly sink it. And you probably can't read their code well enough to know which one you're hiring. That's the real problem. Technical screens test ability. But ability isn't what kills early engineering teams — judgment does. Judgment about what to build, what to skip, and when to push back on you.
Here's how the vetting decision actually flows. You're looking for three signals: do they push back when something's wrong? Do they have strong opinions about what not to build? And can they explain tradeoffs without oversimplifying? A strong yes across all three is a hire. Weak on one — dig deeper. Weak on two or three — proceed with real caution. These aren't bonus qualities. They're the job.
Ask these three questions in every first-engineer interview. The first: "Tell me about a technical decision you regret." Listen for ownership — not blame. The second: "What's the feature you're most proud of killing?" If they've never killed a feature, that's the answer. The third: "Walk me through a time you disagreed with a PM or founder." You want someone who can disagree and then commit. Those three questions will tell you more than any coding test.