The Rise of the Hybrid Builder

I’ve spent most of my career feeling like a misfit.

Not engineer enough to be hired as an engineer.

Not designer enough to be hired as a designer.

Not “PM” enough to be hired as a PM.

But give me a domain, a problem, a vague brief, or a half-baked idea, and I’ll figure it out and deliver it well. I always have. I just didn’t know there was a name for that kind of builder, and for a long time it didn’t feel like the industry valued it anyway.

Lately, I’m realising I’m not the only one wired like this. And more interestingly, the tools are finally starting to reward this shape of brain.

Listening to Claire Vo (ChatPRD) and Nan Yu (Linear) on the Product Growth Podcast with Aakash Gupta is what knocked this loose for me.

Claire is product to the bone.

User-centric. Taste-driven. Structured.

ChatPRD forces clarity. It teaches you to think like someone who cares about users and outcomes, not outputs.

Nan is almost the opposite.

Engineer-centric. Fast. Crisp. Zero ornamentation.

Linear gives you rails that quietly eliminate most of the drag teams create for themselves.

These two philosophies shouldn’t overlap, yet somehow they do, and that overlap is where the story is.

Neither tool is “flexible.”

Neither wants you to invent your own workflow.

Both are prescriptive in a way that makes you better if you just go along with it.

And that’s the quiet truth: opinionated tools create opinionated builders. Opinionated builders create higher-quality work. Faster. More repeatably. With fewer mistakes.

This clicked for me the first time I ran a full cycle with both tools stitched together.

I dropped a handful of features and bugs into Linear without cleaning anything up.

ChatPRD pulled them in, turned them into real PRDs, and sat there like a second brain, sharpening the thinking I’d already started.

Then Linear became the home base where agents got spun up, code got written, PRs opened, and notifications came back to me once everything was ready for review.

And suddenly the distance between an idea, the spec, the code, and a shippable change became… one continuous flow rather than a chain of handoffs.

It felt almost unfair.

The reliability. The speed. The clarity.

And underneath all that, this strange feeling that the lines between roles were dissolving in real time.

There’s a new type of builder emerging, and it’s the one I accidentally became.

The hybrid.

The misfit.

The generalist with taste, curiosity, and enough technical depth to get themselves into trouble and then climb their way out again.

Someone who can toggle between mental models with almost no friction.

Someone who knows when to act like a PM, when to act like an engineer, and when to act like a designer, even if none of those hats fit perfectly on their own.

For years, this profile looked “unhireable” because it didn’t slot neatly into a job title.

Now it looks inevitable.

On one side, you have teams like Linear.

Small. Engineer-heavy. High-output.

The traditional PM role becomes less essential because the tools close most of the gaps.

On the other side, you have the rise of the solo or duo builder.

People shipping entire products end to end.

People using tools and agents as force multipliers rather than toys.

But here’s the tension.

Speed is now cheap.

Taste is not.

Anyone can ship an app in a weekend.

Very few can ship something people actually want.

This is where the hybrid builder stands out.

Not because they can build fast.

But because they understand products, users, and the craft behind the decisions—so when they build fast, it actually lands.

This new wave creates a dangerous illusion for inexperienced builders.

Agents make it feel like you have superpowers.

You can generate wireframes, specs, and code in a day.

You can ship things that would’ve taken teams weeks.

And that’s exactly how you end up thinking you’re better than you are.

But the iceberg is still under the waterline.

Taste. Judgement. User understanding. Product intuition.

These aren’t generated for you.

They’re amplified… or exposed.

And the hybrid builder only works when those things are already there.

For years I wished I’d studied engineering instead of architecture.

I thought I’d backed myself into an odd corner, too broad to specialise, too specialised to be broad.

I assumed I’d always be “almost” qualified for the roles I was drawn to.

Then this modern toolchain arrived, and everything snapped into place.

The generalist wasn’t the problem.

The environment just wasn’t built for us yet.

Now it is.

If I could hand my younger self one sentence, it would be simple:

Never stop learning.

The rest catches up eventually.

The hybrid builder was always here.

We just didn’t fit cleanly on org charts, and traditional hiring didn’t know what to do with us.

Now the tools are blurring the boundaries.

The workflows are collapsing.

The work is getting more agentic, more rapid, more fluid.

And suddenly the way we think—for years, a weird edge case—feels obvious, practical, and increasingly normal.

It feels like we weren’t wrong.

We were early.

And the work is a lot less lonely now.