Judge a builder by their failures
Every portfolio is a highlight reel. What a builder says about the projects that went wrong tells you more than any demo.
Every builder’s portfolio is a highlight reel. The demos worked, the screenshots are real, and nobody puts the disaster on the homepage. So you can’t judge a builder by their successes — those are curated. Judge them by how they talk about failure.
Ask for the story of a project that went wrong
A good builder answers immediately. They have one, it’s specific, and somewhere in the telling they say what they changed afterwards — a habit, a check, a clause in how they scope. The story costs them something to tell, and they tell it anyway.
A bad one hesitates, or blames the client entirely, or can’t remember a single project that wasn’t a triumph. A career with no failures isn’t excellence. It’s either a short career, a forgetful one, or work that never mattered enough to break.
The questions that predict the experience
Anyone can answer “what have you built like this”. The revealing questions are the others. When did you last deliver something the client didn’t end up using? What did that cost you? What happens in month four, after the launch applause? Who answers when it breaks at month-end? How do you decide what not to build?
You’re not listening for perfect answers. You’re listening for whether the person thinks in systems or in demos — whether the world after launch exists for them as a first-class thing, or as a place where their responsibility quietly ended.
Why this is the tell
Software that matters fails sometimes. Neighbours change their interfaces, data arrives wrong, users do the thing nobody predicted. A builder who can’t discuss failure comfortably is either unfamiliar with real software or won’t be nearby when yours has a bad day — and every system has bad days.
The builders worth hiring bring up failure before you do. It’s not humility. It’s experience, priced in.
The successes tell you what a builder can do. The failures tell you what they’ll do when it’s your project that’s on fire.
Working on something this applies to? Tell us about it — thirty minutes, no pitch.