Claude PM Masterclass from Former FAANG AI PM Jyothi Nookula - The Growth Podcast | Lyssna här

Today’s episode

“This one’s too complex. I’m still stuck on ChatGPT.”

I get some version of that DM every week, usually right after I publish something on the PM OS or the Team OS. And every time, I feel it, because those guides do assume you’re already up and running.

So I made this episode for the person sending the message. Jyothi Nookula has been an AI PM since before that was a title, through Netflix, Meta, and Amazon, and I asked her to take a PM from zero to eighty on the entire Claude stack in one sitting.

She walks through:

The five-layer Claude stack, so you finally know which surface and which model to reach for and when

A chief of staff you build in Claude Code that reads your meetings and quietly learns your org, your people, and your politics

The self-improving agent loop she used to beat 30 engineering teams at an internal hackathon, as a PM

Everything she shows is something she runs at work, which is the only reason any of it holds up.

Send this to the PM in your life who keeps saying they’re behind. Two hours from now, they won’t be.

----

Brought to you by:

Hyper Agent: Turn your recurring PM work into reusable agents

----

If you want access to my AI tool stack - Dovetail, Arize, Linear, Descript, Reforge Build, Relay.app, Magic Patterns, Speechify, Bolt.new and Mobbin - become an annual subscriber ($150), and grab Aakash’s bundle.

If you want access to my AI PM customizations - PM OS, Job Search OS, and Prompt Library - become a founding subscriber ($250).

----

Key Takeaways:

1. Match the model to the job - Sonnet handles ninety percent of PM work at the best cost. Save Opus for genuinely hard reasoning, and hand fast bulk jobs to Haiku. Defaulting to the smartest model for everything just burns time and money.

2. Stop skipping the knowledge layer - Projects, skills, and memory are what make Claude know your actual work instead of guessing from a blank slate. Almost everyone underinvests here, and it is the difference between a chatbot and an assistant that knows you.

3. A skill beats a prompt - A skill is a saved playbook Claude picks up on its own when it fits the task. It only loads when needed, so it never clogs the context window. Build one once and stop re-explaining the same task forever.

4. Write your skills yourself - Human-written skill files consistently beat AI-written ones. Draft with Claude to move fast, then layer in the domain knowledge only you have. That last step is what makes it actually work.

5. Automate your time based work - A morning brief, a standup summary, and an end-of-day wrap can all run on a schedule while you sleep. You walk in already knowing what needs your attention. It clears the busywork that eats your mornings.

6. Give your automations guardrails - Cap the length, tell them to stick to facts, and never let them hallucinate. Left unchecked, an AI brief will pad itself and invent things. A few hard rules keep it sharp and trustworthy.

7. Build a chief of staff that learns your org - Point Claude at your meeting notes and let it build a picture of your people, your priorities, and your politics over time. Feed it transcripts first, since they carry the richest signal. It compounds into something no generic chatbot can match.

8. Keep that knowledge base on your own laptop - Your most personal work data does not belong in someone else's cloud. When you leave a company, it walks out with you. You keep full control of your most sensitive context.

9. The PM job is changing fast - The ratio is shifting from one PM per eight engineers toward two PMs per one. Building is becoming part of the role, and the PMs who can ship are pulling ahead.

10. Building is easy now, taste is scarce - When anyone can build, the edge moves to knowing what is worth building and what good actually looks like. That judgment is the one skill you cannot download.

----