For generations of people entering the tech workforce, the expected career path looked something like this: Get an entry-level job, learn a specific role, and work your way up. Engineers fixed bugs before designing systems. Designers refined existing experiences before shaping new ones. Aspiring product managers supported research and analyzed usage before taking on bigger decisions.
Along the way, you learned from people who'd been doing the work longer. A senior engineer explained why your fix would create another problem. A designer pointed out an assumption you'd made about the user. Those smaller assignments gave you a chance to develop judgment before the consequences of getting something wrong grew larger.
Now AI is changing both the availability of that work and what newcomers can do without entry-level experience.
Experts have been sounding the alarm for years. Researcher Matthew Beane warned in 2024 that technology could let experienced workers accomplish more while leaving junior colleagues with fewer opportunities to participate and learn. More recent hiring figures underscore the pressure on that starting point: Entry-level job postings fell 7.5% between May 2025 and May 2026, while senior-level postings rose 14.7%. That shift has multiple causes, but it raises an urgent question about where newcomers get their start.
AI is giving newcomers to product a different starting point
Some are creating their starting point themselves. Young people are already launching businesses with AI's help. Transformative AI tech has changed the calculation for someone waiting for an employer to take a chance on them. With AI assistance, they can explore a customer problem, design an experience, and build an initial product. Work that once required assembling a team becomes something an individual can begin on their own.
It's also consistent with a broader change in product work. A product builder works across product, design, and engineering, using AI to bring ideas into a form people can try. Early-career people have an opportunity to develop that range from the start, including inside established companies.
Starting off with that broader view can be valuable for learning. A builder who conducts research and implements the result gets to see how their interpretation of a customer's problem holds up in practice. They can follow a decision through to its consequences, then use what they learn to improve the next version.
Why product judgment matters more than ever
AI lets early-career product builders take on research, design, and development sooner, but navigating those challenges successfully means cultivating product judgment faster.
Early-career employees need experience deciding which customer problems to solve, what to prioritize, and how to measure success. They also face a related challenge: the need to evaluate AI-generated work while losing opportunities to develop the experience that evaluation requires. A polished output can make it easy to overlook an assumption nobody has tested.
Building for real users gives newcomers a way to test those assumptions. Someone who abandons your onboarding flow or keeps using a spreadsheet instead of your app gives you a problem to investigate. You can ask what happened, change the experience, and see whether the change helps. Each iteration gives you something specific to learn from.
Product leader Cris Valerio developed her product intuition by working with small businesses on AI-assisted solutions, learning from their constraints and quick customer feedback. Emerging builders can undertake similar experiences to form part of a broader apprenticeship, with access to experienced people who can help them understand the results.
How product leaders can help new builders learn the craft
Product leaders have the power to create conditions to better support those new to the field. Give an early-career teammate a small customer problem to own through discovery, development, and iteration. Review the reasoning behind their choices. Ask which customer conversations and usage patterns informed the next change, and explain where you'd make a different call.
Make room for them to change their minds, too. If the first version gets little use, work through possible explanations together before asking for another feature. Understanding why an idea fell short and deciding what to try next gives a newcomer the practice they'll need on bigger initiatives.
That relationship can benefit both people. Microsoft's Katy George advocates two-way apprenticeships in which experienced colleagues contribute judgment and context while early-career employees contribute AI fluency and fresh approaches. Independent builders can seek that outside perspective through mentors and practitioner communities, too.
The next generation may take on broader responsibility much sooner. Helping them learn from it should be part of how we develop product talent.
Want practice making these type judgment calls? Take Mike Belsito's free Product Judgment course in the Pendo Learning Lab. You'll learn to combine customer signals, identify the underlying problem, and choose what matters when the information is incomplete.
