The Rise of the AI Builder

For decades, building a product meant assembling a team of specialists. A product manager to define what to build. A designer to shape how it looks. An engineer to write the code. Each discipline had its own title, career ladder, and way of thinking.

That model is breaking down. But this is not entirely new.

In startups, a single person has always worn multiple hats. Writing specs, talking to customers, mocking up designs, and shipping code. When the team is small, there is no room for "that is not my job." The builder who works across product, design, and engineering was already a reality in early stage companies long before anyone gave it a formal title.

AI has supercharged this pattern. It gives one person the leverage to do what used to require a cross functional team. Not just in startups, but inside the largest companies in tech.

LinkedIn calls this person the "Full Stack Builder." Others call it the "Product Builder." The underlying shift is the same: the walls between product, engineering, and design are converging into a single builder role.

Before AI: The Early Movers

Some of the biggest companies were already moving in this direction.

At Figma Config 2023, Airbnb CEO Brian Chesky said: "The designers are equal to the product managers, actually we got rid of the classic product management function." He later clarified that Airbnb merged PM with product marketing into an Apple style product marketing function. Designers were elevated to "architects" who sit alongside engineers, rather than receiving direction from PMs.

The approach mirrors how Steve Jobs ran Apple in the 2000s, where managers worked closely with engineers and designers rather than relying on a separate PM function. The product thinking did not disappear. It got distributed across the people who build.

PostHog tells a similar story. They built their entire company around "product engineers" rather than product managers. Small, autonomous teams own their products end to end: engineers drive the roadmap, talk directly to customers, and make product decisions.

What Airbnb and PostHog proved with culture, AI is now making accessible to everyone else. The instinct to converge roles was always there. AI just removed the skill barriers that made it impractical at scale.

The Companies Leading the AI Builder Movement

LinkedIn: From Product Manager to Product Builder

LinkedIn's Chief Product Officer Tomer Cohen has gone further than any other leader at a major company in formalizing this convergence.

In late 2025, LinkedIn scrapped its longstanding Associate Product Manager (APM) program and replaced it with an "Associate Product Builder" program starting January 2026. New hires now learn coding, design, and product skills together instead of specializing in one.

Cohen introduced a formal "Full Stack Builder" title and career ladder, enabling anyone from any function to take products from idea to launch. His reasoning:

"We have an opportunity to collapse the stack back and say, 'Hey, development requires an idea and creativity, but it also needs other things like, how do you code your product, how do you spec it, and how do you design it?'"

Instead of working with five to ten teams across multiple functions, a full stack builder uses AI to collapse a multi-disciplinary process into a streamlined activity completed by one person.

The five skills Cohen emphasizes for this new role are vision, empathy, communication, creativity, and judgment. As he put it: "Everything else, I'm working really hard to automate."

Even the hiring process reflects the convergence. Applicants submit a 60 second demo of something they built, not a traditional resume. Show what you shipped, not which silo you belong to.

Shopify: Prove AI Cannot Do It First

Shopify CEO Tobi Lutke published an internal memo in April 2025 that became one of the most discussed documents in tech. The core mandate: employees must prove AI cannot do a job before requesting additional headcount.

AI usage became a "fundamental expectation of everyone at Shopify" and was folded into performance reviews. Every employee is now evaluated on how well they use AI to expand what they can do.

The implication for roles is direct. If one person with AI can do the work previously requiring multiple specialists, and you must justify every new hire by proving AI cannot do the job, the natural outcome is fewer specialized roles and more generalists who build end to end.

Figma: The Data on Role Convergence

Dylan Field, CEO of Figma, stated it plainly: "We're all product builders, and some of us are specialized in our particular area."

Figma's 2025 shifting roles report provides some of the clearest data on this convergence:

• 72% of respondents named AI tools as a key reason for role expansion.
• 56% of non-designers now engage "a lot" or "a great deal" in design tasks, up from 44% the prior year.
• 64% of respondents identify with two or more roles, showing how traditional boundaries between disciplines are blurring.

Engineers are designing. Designers are prototyping. PMs are coding. Figma is both documenting and accelerating it.

Anthropic: Every Function Codes

Boris Cherny, the creator of Claude Code at Anthropic, predicted that the "software engineer" title will start disappearing, replaced by "builder" or "product manager." He described what is already happening inside Anthropic: "Engineers are very much generalists, and every single function on our team codes," including PMs, designers, engineering managers, and finance people.

The convergence goes both directions. Engineers are picking up product skills. PMs are picking up engineering skills. The roles are meeting in the middle.

Anthropic's internal research (surveying 132 engineers and conducting 53 in-depth interviews) confirms this: engineers are becoming more full stack, able to succeed at tasks beyond their normal expertise. Security teams use AI to analyze unfamiliar code. Alignment and Safety teams build front end visualizations. The old boundaries no longer describe how work actually gets done.

Why This Is Happening Now

This convergence is not just cultural. It is enabled by tools that make it technically feasible for one person to work across disciplines that used to require separate specialists.

Vibe coding, a term coined by Andrej Karpathy in February 2025, describes a workflow where you describe what you want in natural language and AI generates the code. Product managers can now create working prototypes instead of spending weeks writing specs for engineering teams. Major tech companies like Google, Stripe, and Netflix are reportedly adding "vibe coding" rounds to PM interviews.

Replit CEO Amjad Masad shared a revealing detail: a public company CEO told him that AI coding had negligible impact on his engineering teams. The real transformation was on their product and design teams using Replit. The people who understood what to build suddenly had the ability to build it themselves. That is convergence in action.

PwC's 2026 AI Predictions framed it as a macro trend: AI could end the ever increasing specialization of work that has marked most of the industrial era. Their advice to companies: "look for all around athletes" and evolve recruitment toward "AI forward generalists and agent orchestrators."

Aha.io's Brian de Haaff described this as an "era of role consolidation" where AI expands what each person is capable of: "Anyone with the right mindset who can direct AI effectively is now a product builder."

The Solo Builder Economy

This convergence is not just happening inside big companies. It is reshaping startups, where smaller teams and solo founders are shipping products that used to require entire departments.

According to Carta data, solo founders now start 36.3% of all new companies, a record high. Solo led exits account for 52.3% of successes.

Y Combinator CEO Garry Tan said that for about a quarter of current YC startups, 95% of the code was written by AI: "You don't need a team of 50 or 100 engineers. You don't have to raise as much."

YC's Fall 2025 "Requests for Startups" go even further, with one calling for growing a company to $100 billion in revenue with just 10 people.

Whether it is one person or ten, the pattern is the same: AI collapses the need for large specialized teams. The builder who can work across product, design, and engineering is no longer a curiosity. They are the default.

When Convergence Goes Wrong

Not every company gets this transition right. Some mistake convergence for elimination: instead of expanding what each person can do, they simply cut the people.

Klarna shrank from 5,527 employees to roughly 2,907 using AI. Revenue grew 108% during the same period. It looked like a success story.

Then CEO Sebastian Siemiatkowski admitted "we went too far." Customer complaints increased, satisfaction dropped, and they began rehiring humans, particularly in customer service.

The lesson: this is not about making product managers or any other role obsolete. Product thinking, the ability to understand users, define the right problem, and decide what is worth building, is more critical than ever. Convergence works when you give capable people better tools to work across boundaries. It fails when you use it as an excuse to cut headcount without ensuring the remaining people have the judgment and depth to cover the expanded scope.

Atlassian made this point well: "Shipping the wrong feature quickly is worse than shipping the right feature slowly. In a world where implementation is cheap, building the wrong thing becomes the most expensive mistake you can make."

The Silicon Valley Product Group (SVPG) adds another caution. They acknowledge that "triple threats" (people skilled in product, design, and engineering) exist, but call them "true unicorns" and warn that covering all three roles is "usually not sustainable" long term. The goal is not to turn everyone into a solo generalist who never collaborates. It is to expand each person's range so they can work across boundaries more fluidly.

Why I Am Bullish on Young Professionals

I believe the next generation of AI builders is already here. They are the young professionals and students who grew up with AI tools as a default part of how they learn, build, and work.

The numbers support this. 80% of Gen Z use AI tools in their daily lives. 74% have used generative AI tools like ChatGPT or Claude. 80% of Gen Z professionals use AI for more than half their daily tasks.

They are AI native. Marc Prensky, who originally coined the term "digital native," is now pioneering the concept of AI natives as the next evolutionary leap:

"In the same way that analog natives who didn't adapt to the Internet were out-competed by digital natives, we will start to see the more rigid digital native millennials replaced by those who use AI to their advantage."

Here is why young professionals are a natural fit for this converged builder role:

They do not carry the baggage of traditional role definitions. They have never internalized the idea that "product is someone else's job" or "I only write code." They see a problem and reach for whatever combination of human skill and AI capability solves it best. As LupaHire noted, AI native employees "don't just use AI; they think with it, through it, and beyond it."

They are comfortable learning across disciplines. The converged builder role demands someone who can think about users, shape interfaces, and ship working software. Young professionals who grew up building side projects with AI tools have been doing all three naturally, without even realizing those used to be three separate jobs.

They adapt fast. The World Economic Forum estimates that 39% of workers' core skills will change by 2030. The people who succeed will not be the ones who mastered one tool. They will be the ones who can pick up the next one.

The One Area to Watch: Fundamentals

That optimism comes with one important caveat.

Being AI native is a massive advantage. But it is not enough on its own.

AI amplifies what you already know. If you have strong product intuition, AI makes you faster at building the right thing. If you have no product intuition, AI helps you build the wrong thing faster. The convergence of roles only works if the person at the center has depth, not just breadth.

Kent Beck captured this tension perfectly: "The value of 90% of my skills just dropped to $0. The leverage for the remaining 10% went up 1000x."

The 90% are execution skills that AI can now match: syntax, boilerplate, even polished writing. The 10% are judgment skills: knowing what to build, why it matters, and whether the output is actually good. Those skills did not lose value. They became the highest leverage skills a builder can have.

Stanford Professor Subramani put it well: "AI is like having infinite interns. It gets you to the first 80% quickly, but it won't get you to the final 20%. The skill that will always be in demand is knowing what people want." Carnegie Mellon's research echoed this: vibe coding transforms workflows but does not replace the need for strong product thinking. The tools change. The underlying discipline does not.

AI also creates entirely new skills that did not exist before: prompt engineering, validating AI output, and debugging code you did not write. All three build on the same foundation of strong problem solving and critical thinking.

The young professionals who will thrive as AI Builders are those who invest in three things:

1. The ability to adapt and learn. Not mastering one tool, but developing the meta skill of learning new tools quickly and knowing when to switch.

2. Open mindedness without the old mindset. Seeing yourself as a "builder" first. Not a PM, not an engineer, not a designer. Someone who ships outcomes using whatever combination of skills the problem demands.

3. Strong fundamentals. Product thinking. Communication. System design. Critical thinking. These are the skills that let you evaluate whether AI output is actually good, and direct it toward the right problems.

The risk is leaning too heavily on AI without building the judgment to know when it is wrong. The opportunity is that those who pair AI fluency with genuine depth will be extraordinarily valuable.

The Path Forward

The walls between product, engineering, and design are converging. Not because companies decided to reorganize for fun, but because AI has made it possible for individuals to work across boundaries that used to require entire teams.

LinkedIn is building career ladders for this converged role. Shopify is basing hiring decisions on it. Figma is measuring it. Anthropic, PostHog, and Airbnb are already operating this way. Solo founders are living proof that one person can now ship what used to take a team.

The people best positioned for this convergence are those who never learned to think in silos. They are adaptable, open minded, and AI native. The ones who also invest in their fundamentals will not just fill these new builder roles. They will define them.

The AI Builder era is here. The builders are ready.