Everyone is a builder now

Something different is happening in software teams right now. Designers are shipping code. Engineers are making design decisions. And the boundaries that used to define these roles are dissolving.

AI is transforming how we build software, and in doing so, it’s blurring the lines between designers, engineers, and product managers. As tools like Codex, Claude, Cursor, Lovable, and Vercel’s v0 increasingly generate production-ready code from natural language or design files, the traditional workflow of “design → handoff → implementation” is breaking down. For startup founders, this shift represents a new era of leaner teams, faster iteration, and hybrid roles.

The key question: what happens when everyone becomes a builder?

Designers as builders

Modern AI tools now allow designers to move beyond static mockups and directly build working software. OpenAI’s GPT can turn a hand-drawn sketch into a live website in seconds. Tools like Cursor, Lovable, or Vercel’s v0 let designers describe what they want and generate deployable components without writing code from scratch.

Anthropic has reported similar results internally—designers feeding concepts into Claude and receiving usable frontend code back. As one Vercel engineer put it, “We’re seeing new product designers blend UX, UI, and code in one creative flow.” AI becomes the glue between design intent and execution.

This doesn’t mean every designer must become a software engineer. Rather, it means AI fills the gap, letting designers test, ship, and iterate independently. Human oversight is still needed for polish, integration, and system thinking, but the barrier to implementation has dropped dramatically.

Engineers must learn design

As AI handles more of the coding grunt work, the role of engineers is shifting. “AI has completely changed what it means to write software,” said OpenAI CEO Sam Altman in 2025. Engineers no longer differentiate themselves by writing boilerplate—they add value through system design, product intuition, and quality judgment.

Vercel’s Lee Robinson describes this as the rise of the “product engineer”—someone who understands both code and UX, and can deliver features end-to-end. In the AI-first world, engineering is less about implementation and more about defining what to build and why it matters to users.

That requires engineers to embrace design thinking: user flows, aesthetics, ergonomics. AI can generate five UI layouts in seconds, but only a thoughtful engineer can choose the best one. And with faster iteration comes a need for engineers to own product decisions, not just execute them.

Rise of the product engineer

The convergence of design and engineering is giving rise to hybrid roles: product engineers, design engineers, AI product creators. These are people who think across disciplines and use AI to amplify their reach.

Lee Robinson notes this trend began before AI but is now supercharged. One person can realistically ideate, build, and ship an entire feature. Some even talk about the “single-person startup”—a founder or product engineer building an MVP solo using AI copilots like Lovable.

Falk Gottlob frames this as a new role: the AI Product Engineer, who combines “the strategic thinking of a PM, the technical skills of an engineer, and the creative instincts of a designer, all amplified by AI.” This isn’t theory. Small teams are already doing it. With AI, iteration speed becomes a core advantage. New ideas can be tested in hours, not weeks.

What happens to product managers?

If designers and engineers are shipping faster and taking on more product thinking, where does that leave PMs?

Some suggest the role could shrink or even vanish in small teams. Ryan Ford provocatively asked: “Why do we need PMs if designers do more and engineers disappear?” In AI-native startups, the old model of a PM coordinating between silos is less relevant because the silos themselves are disappearing.

Still, most experts agree that PMs aren’t going away—they’re evolving. AI generates outputs, but it can’t define strategy, understand users emotionally, or prioritize trade-offs. Vince Law argues that PMs now play a bigger role in steering the team, not just writing specs. When everyone has a “turbo paddle,” someone needs to steer the boat.

Future PMs will spend less time writing Jira tickets and more time synthesizing feedback, defining goals, and making sure the team builds the right thing. They may also take on AI-specific duties like model governance or managing AI-integrated products.

A new model for product teams

AI is dissolving the boundaries between traditional roles. Designers can now build. Engineers must design. PMs shift from task managers to strategic leaders.

Startups that embrace this fluidity can move faster and do more with fewer people. They can ship prototypes using tools like Lovable, tweak them with AI, and test them with users—all in days, not months. The most innovative teams aren’t rigid org charts, but integrated units of humans and AIs solving problems together.

This doesn’t mean every team member must be a generalist. But it does mean the walls between “design,” “engineering,” and “product” are coming down. The best creators in this new era will be those who speak all three languages and know how to wield AI as a co-creator.

Final thoughts

The AI revolution isn’t about replacing designers or engineers—it’s about augmenting them, accelerating them, and blending their workflows. For founders, this means rethinking how teams are structured. Instead of three separate departments passing work down an assembly line, imagine a few product engineers collaborating directly with AI to ship features from idea to execution.

Those who adapt fastest—by hiring hybrid thinkers, embracing AI tools like Lovable, and flattening communication—will have a huge edge. Because in 2025, speed of iteration is the ultimate competitive advantage.

LFG

---