What is a Product Builder?
I keep seeing the title "product builder." Something about it doesn't sit right, and I've been trying to work out whether that's just me.
It's showing up everywhere now. Product builder. In bios, job posts, in arguments about how to staff in a world of agents and commoditized code. And I keep tripping over it. Not in a strong, I've-got-this-figured-out way. It's more like a word that doesn't feel right, a word you can't stop noticing once you've noticed it.
Sure, I've got an obvious bias. I've been a PM for decades, so of course I'd bristle at a title that sounds like it's replacing my profession. But I also came up as an engineer. I've been on the build side too. So when I say I don't think "builder" is the right word, it isn't me defending my "tribe." If anything both of my old tribes are in this, and it still doesn't feel right.
Here's the distinction I keep landing on. Someone who builds a thing is a builder. That's clean, that's fine. But someone who builds a thing because they understood a problem nobody else understood, and they know who it's for, and they can tell whether it's worth making at all, that person is doing something the word "builder" doesn't cover. The building might be the least interesting part of what they did.
And the building really is the easy part now. That's what changed. When you work with an AI agent, you're deciding what to make, but it's handling most of the how. Anthropic published a study in June 2026 that looked at roughly 400,000 coding sessions from late 2025 through spring, and found people made about 70 percent of the planning decisions while the agent did most of the execution. The thing that predicted success wasn't really about coding ability. It was about how well the person understood the problem. People from all kinds of jobs did about as well as the software engineers. Managers did even better. Honestly, was Dilbert wrong this whole time?
So if the building isn't really the hard part anymore, calling the role "builder" seems to name it after the wrong half. It points at the prompting and skips the judgment. That's the piece that feels off. I'm not offended by the title. Maybe OCD, but it seems precisely imprecise.
I will grant that the title didn't come from nowhere. I'm sure a lot of folks are tired of product managers who don't make anything. A slide deck and a roadmap with no functional output is frustrating to people who "work" for a living. Maybe this is like the Product Owner trend. "Builder" says, "I ship." Fair enough.
Not for nothing, but having expertise and context doesn't mean you're always right. A photographer I know recently built herself a tool to manage crew and shot lists, and she's sure her people need it. She's probably right, but also, maybe not. The cheap build enabled her to get something done that she's been wanting for a long time. She'll find out if that's just something she wanted, or if it's something her people want. As a product, it may not be the right thing for anyone. It may be slop. As a tool for herself, she seems happy enough. I think that's the difference. If it's just for you, no further judgment required: you're a builder. If it's for a market? If it's a business? Maybe it's not just about the build.
So what's the right word? I'm not sure. I keep saying we're all product managers now, and I'm not sure that's right either. Maybe "product manager" drags too much baggage from the deck-and-roadmap version to mean what I want it to mean. I honestly don't know.
I'm more confident about the small claim than the big one. The photographer. The accountant who knows the rules cold. The founder who understands the customer better than anyone she could hire. If they're applying their knowledge to a market, to a business, they're not just builders. They build, sure. But that's not the part that counts. It's the THOUGHT that counts…