What Youâll Learn
đĄ What it actually feels like to go from engineer to PM to AI PM and builder.
đĄ How to test a career move with evidence before we quit.
đĄ How to check a new job after we do the move.
đĄ Why the scarce skill is not the role. It is deciding what deserves to exist.
đ Checklist to support your role transition.
đ 40% discount to AI Native Practitioner Program to practice transitions and AI.
What is the Career Discovery Track
When I started WonderLead, I promised we would expand our horizons with diverse tech career paths and roles. But not a catalog of job descriptions or repository of open roles. As real people sharing why we moved, what we were afraid of, and what we would tell the version of ourselves who was still sitting on the fence to take the next move.
This is the first post of that Discovery track.
I used to not completely own my career. I depended on my managerâs guidance because I didnât know all the paths available to me. Many of us are in that same place right now. A decent title. Real responsibility. Fear to failure or layoffs.
We wait for permission. We wait to feel ready. We wait for the market to tell us who we are allowed to become. While deeply inside there is something that tells us that we need to make a change. And sometimes unconsciously we self-sabotage ourselves. With the posts in this track we wonât ship the journey of our careers alone.
From Product Manager to AI PM | Builder
Elena | AI Product Leader did not wait.
Elena is a Product Manager who stopped asking for permission to build. She is an AI Product Manager turned builder, founder of DraftKit and AIAdventChallenge, and the writer behind Prompt-Led Product | For PMs Building in the AI Era.
She went from software engineer to PM in healthcare, from PM to AI PM, from AI PM to builder and founder. The metric that made her decide to leave her corporate job was her AI Advent Challenge app 900 users she got after working for a month at night and weekends.
If we are undecided, this post is not here to push us to quit. It is here to help us step up with evidence, self-awareness, a plan, and a way to check whether we are in the place we genuinely want to be. Elena tested to be a founder and now she is looking for a job back at corporate.
Elena, over to you.
1. The Starting Point
On paper I had the good version of the job. Software engineer first, building the whole stack from scratch, then Product Manager from 2019 on, mostly in healthcare. Technical role, decent title, real responsibility.
The honest version: I was becoming a ticket mover. I managed backlogs, ran stakeholder meetings, and defined products I never got to touch. I knew exactly what to build and my actual output was documents about it. The distance between having an idea and seeing it live kept growing, and it wasnât because I lacked the skills. The role just didnât let me use them.
I remember the specific feeling: sitting in a refinement session, watching a feature I had specced three months earlier still waiting in a queue, thinking âI could have built this myself by now.â That thought stopped being an exaggeration somewhere in 2025. Thatâs when I knew.
It wasnât a daily unhappiness, and I donât want to oversell it. It was quieter than that, more like a slow drift I only noticed in specific moments, that refinement session being one of them. And it wasnât 100% alignment from the first day I started building either. I discovered how aligned it was by doing it, not before I started.
2. The Blockers
Two fears, and they took turns.
The loud one was money. I had a stable corporate salary and I was about to trade it for apps that didnât exist yet and a newsletter that paid nothing.
The quiet one was worse: looking unprofessional. I had spent years building a âserious PMâ reputation, and rebranding myself around prompting AI tools felt risky. What would recruiters think if this failed and I had to go back? I almost stayed generic and palatable because of that fear. Choosing to be specific and weird instead was the single scariest part, more than the money.
The reality after.
If you want to continue reading the experiences and recommendations from Elena and get the Builder Transitioning Checklist:
How to Practice Your Role as AI Native
You didnât read Elenaâs post yet because you didnât subscribe. But Elena strongly recommended to practice your next role before leaving your current job as a first experiment. In her case, Elena built at night, on weekends, and without a team. That path is real, and it is lonely.
If you want to practice your next role or builder role with other people and agents instead of doing it alone:
Join the AI Native Practitioner Programme Cohort 2
The AI Native Practitioner Programme allows you to practice your next role with humans and AI agents, in a cross-functional team, shipping a real product with big tech methodologies while being coached by senior professionals during 10 weeks, or 5 weeks at an intensive pace. In Cohort 1, a Product Manager, an engineer, and a designer shipped a real product reviewed by professionals in big tech while transitioning roles: Business Analyst to PM, UX Designer to Researcher, Frontend Engineer to AI Engineer. All of them to AI Native and Builders.
Setup week starts Tuesday 1 September. Roles are assigned as the team fills. Apply free in about two minutes. Payment only after your place is confirmed in a 10-min call.
With the launch of this track, Iâm giving you a discount of 40% for the next 48h to all readers. Use the code: WONDERLEAD40
This is the start of our career Discovery track. More wonder leaders will share what drove them to make their bold career transitions. If you have any questions about transitioning for future posts, feel free to DM me too.
Do you want to join and do this journey with us? Help to build our community, đ and Share. Discover, Own, and Thrive as a leader in your career with WonderLead posts and community.
I am looking for more guest posts from different tech role writers, to help more people discover their path. If that is you, send me a note.
Get in Touch: LinkedIn and X. If you wish to make a request on a particular topic you would like to read, you can reply or send me an email to patri@wonderlead.tech.