Coaching for career switchers, early-career professionals, and analysts who want the PM title. I spent years as a senior technical PM at Amazon and sat in the hiring loops. Today I build my own AI agents, which is exactly the bar the market now sets for new PMs. The work ends with shipped proof, not a pile of sessions.
Three things changed the entry rules. The résumé stopped being evidence, because anyone can generate a polished one in thirty seconds. AI went from bonus to baseline: about 61% of PM postings now mention it, up from 12% two years ago. And the role split into specialties, so a generic PM pitch is a shrinking category.
Put those together and you get the ladder I draw for every candidate. It is where a skeptical hiring manager places you after ten minutes.
Move into product where you already work. Three to nine months, typically. Highest probability, because you already have context and trust. Your gap is usually translation, not experience.
Analyst, growth, strategy, UX research, solutions. Roles that build product muscles while paying you. Convert in twelve to eighteen months. The honest answer for most new grads.
Evidence plus a domain specialty plus warm networking. Six to twelve months, and the hardest, because it demands rung-4 proof before anyone will talk to you.
None of them start with the application. They start with one sentence you can say without flinching: "I am moving into [specialty] product, in [domain], because [the thing I have done that a PM there would recognize as their own work]." If you cannot fill in the brackets yet, that is what the first call is for.
Every package starts by defining what success looks like, and ends with a written summary you keep. Pick by where you are on the ladder.
Already interviewing and need the loop, not the portfolio? The Amazon Leadership Principles Interview Intensive (three sessions) rebuilds your story bank around the principles hiring managers actually score. Pricing is shared on the call, in writing, before you decide anything. The same programs are also on Leland, with their platform guarantee.
A full four-page PM case study, page by page, so you can see what "reasoning, not mockups" looks like. Fictional product and data, real structure. Page two is the one that gets people hired.
Open the example (PDF) →A guided exercise from my Self-Discovery Library that builds your interview story bank. The best answer in the room is rarely the most polished. It is the most honest one, told well.
Open The Story Vault →Five posts: what changed, the three paths in, the portfolio, how the interview changed, and a 30-day plan with the five traps I watch people fall into every cohort.
Read the series →No. Nobody is asking a PM to write production code or design the architecture. They are asking you to make tradeoffs out loud: cost, latency, accuracy, and what a human still has to approve. The tools that let a non-engineer build a working prototype in a weekend exist now, and part of the Sprint is learning to use one well enough to test an idea with real people. I use them every day in my own practice.
Usually the opposite. Your domain is the unfair advantage, if you name it. Most experienced switchers are standing on the internal path and do not know it; their gap is translation, not experience. The Diagnosis exists for exactly this question.
No, and be careful with anyone who does. What I can promise is that you will leave with shipped evidence, a clear path, and a story that hiring managers recognize as their own work. Timelines on the three paths above are typical, not promised.
The bar is higher and more specific: the recruiter screen is often a technical screen now, and the loop includes system design for AI features. The Program covers it, and because I build agents myself, we practice on real diagrams, not vocabulary. If you are targeting a general PM role, we keep it proportionate.
Same coach, same programs. Booking directly is simpler and skips the marketplace fee; Leland adds a platform guarantee and its own discovery process. Choose whichever you are more comfortable with.
Bring your current résumé and one honest sentence about where you want to go. You leave with your rung, your likely path, and a straight answer about whether I am the right coach for it.