The Three-Way Mexican Standoff That Nobody Wins — Except the Builder

The Builder

6:37

There's a tension running through every product team in Silicon Valley right now, and it goes something like this: The engineer thinks they don't need the product manager anymore. AI can do product thinking.

The product manager thinks they don't need the engineer anymore. AI can write the code. The designer thinks they don't need either of them. AI can generate both specs and interfaces. And here's the uncomfortable truth that nobody in this standoff wants to say out loud: They're all correct.

What's Actually Happening

Andrej Karpathy coined the term "vibe coding" in February 2025 to describe what was already becoming obvious — that the primary act of software development was shifting from writing code to describing intent. The AI handles implementation. The human handles judgment.

That reframe had immediate consequences for job definitions that had been stable for decades.

Product managers discovered they could generate working prototypes directly. Designers found they could ship functional code without touching a compiler. Engineers realized they could mock up interfaces and write product specs faster than they could schedule a meeting with someone else to do it.

The data caught up quickly. By 2026, 63% of vibe coding users are non-developers — people with no formal coding background building real software. The vibe coding tools market hit $4.7 billion. Lovable reached $400M ARR. Cursor crossed $2B. Junior software developer employment is down roughly 20% from peak. Big-tech new-grad hiring in engineering is down 55% since 2019. The three-way standoff isn't paranoia. It's pattern recognition.

The Collapse Is the Point

What's actually happening isn't that one role is beating the other two. It's that the friction between the three — the handoffs, the translation layers, the queues and tickets and review cycles — is collapsing. The engineer used to write code because that's the only way software got made. The product manager used to write specs because that's the only way engineers knew what to build. The designer used to own interfaces because nobody else had the tools or training to make decisions about them.

AI didn't make any one of these people obsolete. It removed the specialization tax. The reason these were separate jobs was never that they required fundamentally incompatible skill sets. It's that each domain required enough depth that one person couldn't practically hold all three at once.

Now they can.

Not because anyone got smarter. Because the execution cost of each domain dropped far enough that a single person with good judgment and the right tools can cover all three.

The Builder

What emerges from this collapse isn't a gap. It's a new role.

Call it builder. The builder is someone who takes an idea from concept to shipped product — handling product thinking, interface decisions, and implementation in a single continuous loop. They might have come up through engineering, or product, or design, or customer success, or somewhere else entirely. Their background gives them a center of gravity — a domain where their intuition is sharpest — but AI fills in the surrounding territory. The builder isn't a full-stack engineer in the old sense. Full-stack still meant code. The builder's stack is judgment across the entire product surface: what to build, what it should feel like, and how it actually gets made.

This isn't theoretical. It's already happening. Solo founders are running companies that would have required teams of 10–15 people five years ago. A solo founder recently hit $1.8 billion in valuation. Fortune documented founders launching products, serving hundreds of customers, and landing exits without a single hire. Forbes called the billion-dollar company of one an inevitability by 2028.

The builder already exists. The job title just hasn't caught up yet.

What Gets Preserved

Here's the thing about the standoff: the skills don't disappear when the roles collapse. Engineering intuition — the ability to understand what's architecturally sound, what will scale, what will break — remains valuable. It just stops being the exclusive province of someone with "engineer" in their title.

Product thinking — the ability to understand user behavior, prioritize ruthlessly, and make hard tradeoffs — remains valuable. It just stops requiring a dedicated headcount to carry it.

Design sense — the ability to recognize when something feels right and when it doesn't — remains valuable. It just stops being locked behind a specialization wall.

What the builder role represents is the synthesis of all three, available to anyone with the judgment to wield it. Your background determines your starting angle. An engineer-turned-builder thinks about systems first. A designer-turned-builder thinks about experience first. A product manager-turned-builder thinks about users first. All of them are right. All of them are building.

The Long View

Ten years from now, "coder" as a job category probably looks different. The act of writing syntax by hand, of translating human intent into machine instructions line by line, becomes increasingly optional — the way typesetting became optional after desktop publishing, the way physical film became optional after digital cameras. But the number of people building software doesn't shrink. It explodes. Because the bottleneck was never ideas. It was execution cost. When execution cost drops far enough, latent builders — people who had the judgment and vision but not the time or technical depth to ship — enter the market.

The standoff ends not with a winner, but with a merger. Three roles, one surface. One job that requires all of it, and AI that makes carrying all of it possible. The era of the specialist was the era of high execution costs.

We're entering the era of the builder.

---

Rich Washburn is a technologist and strategist working at the intersection of AI, cybersecurity, and capital. He is Managing Partner and Chief AI Officer at Eliakim Capital, and CIO of Data Power Supply.