Recording intelligenceAI-generated brief · check the source for context

How a Meta PM ships products without ever writing code | Zevi Arnovitz

1:15:12 recording · AUTO · 2 speakers

Watch the original

Executive Summary AI
  • Lenny introduces Zevi Arnowitz, a PM at Meta who was previously a PM at Wix, as a non-technical product person who taught himself to build real products with Cursor and Claude Code.
  • Zevi explains that a year ago, travelling in Asia when Sonnet 3.5 came out, he watched a YouTube video of people building apps with Bolt or Lovable and started building the day he got home from Japan.
  • Because Bolt and Lovable rushed into code, he built a 'CTO' as a ChatGPT project with a custom prompt that owns the technical side, challenges him and refuses to be a people pleaser.
  • His current workflow is a chain of Claude Code slash commands — create issue into Linear, exploration phase, create plan as a markdown file, execute, review, peer review and update the docs — demonstrated live by adding fill-in-the-blank questions to his side product StudyMate.
  • For review he runs Claude, Codex and Cursor's Composer over the same branch and then feeds their findings back through a peer review command that makes the lead agent defend or fix its code, plus constant postmortems that update documentation and tooling.

Brief overview

A non-technical PM ships real products by running Claude and Cursor through a disciplined slash-command workflow.

  1. Plan before any code is writtenLetting an eager coding agent start writing immediately caused the gnarliest bugs, so exploration and a written plan come first.
  2. Let rival models review each otherClaude, Codex and Composer each catch different issues, and the peer review command makes the lead agent defend or fix them.
  3. Ease in gradually, then keep learningStart with a GPT project, graduate to Bolt or Lovable, then Cursor — and use a learning opportunity command whenever something is unclear.

Questions this recording answers

10 questions, each answered where it is said
Which tools does a non-technical PM actually build with today?

He uses Claude Code running inside Cursor, having graduated from Bolt when connecting payments broke down. He also keeps Codex and Cursor's Composer open, and uses Gemini 3 for front-end work. Code is just files, he says, so a project carries from app to app.

What slash commands make up the full build workflow?

Seven reusable prompts: create issue, which files a Linear ticket via MCP; exploration phase, where Claude reads the code base and asks clarifying questions; create plan, producing a markdown plan with status trackers; execute plan; review; peer review; and finally update the docs so agents write better code later.

How do you review code you cannot read yourself?

After Claude reviews its own code, he has Codex and Cursor's Composer review the same branch, then runs slash peer review, pasting each as 'dev lead one' and 'dev lead two'. Claude is told not to take them at face value, but explain why they're wrong or fix them.

Why create a "CTO" project instead of just prompting the tool?

Bolt and Lovable were built to write code immediately, which caused gnarly bugs once things got complex. So he created a CTO project with a custom prompt: it owns how things get built, he owns the problem, and it must challenge him rather than please him.

Where should someone with zero technical background start?

Start slowly with a GPT project, beautiful UI and super simple, then graduate to Bolt or Lovable, then Cursor in light mode, and only gradually open a terminal and go full dark mode. He calls it exposure therapy, because code is terrifying to a non-technical person.

What really separates Cursor and Claude Code from Bolt or Lovable?

The models are the same; Claude underlies Bolt and Lovable too. The difference is the harness: Bolt, Lovable, Replit, Base44 and v0 add layers that take hard decisions out for you, while Claude Code hands you the raw model, full tools, and every decision.

How do you learn the technical side while building?

Slash learning opportunity. When something is hard to grasp, he runs it and describes what he wants to learn. It primes Claude with 'I am a technical PM in the making, I have mid-level engineering knowledge', and asks it to explain the current work using the 80-20 rule.

How do you stop the AI repeating the same mistakes?

He treats documentation and tooling as the biggest productivity hack. When Claude fails or ships a bad bug, he asks what in its system prompt or tooling caused the mistake, then has it update the tooling, docs or slash commands so that mistake never happens again.

Can this workflow work for a PM at a large company?

First make the code base AI native, with markdown files that explain to agents how to work in each area, and technical people should do that. He would not have PMs shipping heavy database migrations, but contained UI projects, with a PR handed to a dev for finishing, are realistic.

How did he use AI to prepare for the Meta interviews?

When Meta reached out he opened a Claude project as his coach, filled with frameworks from Ben Erez, and mock interviewed against it. He also built a segmentation quiz game in Base44 to play on the bus. The biggest change, though, was human mocks from cold LinkedIn outreach.

Key Quote

“I have zero technical background.”

— Zevi Arnowitz, How a Meta PM ships products without ever writing code | Zevi Arnovitz, at 6:06▶ watch at 6:06
Key Quote

“So let's say Claude, she would be the perfect CTO.”

— Zevi Arnowitz, How a Meta PM ships products without ever writing code | Zevi Arnovitz, at 40:58▶ watch at 40:58
Key Quote

“And I think the only way that AI makes you worse at your job is if you're using it wrong.”

— Zevi Arnowitz, How a Meta PM ships products without ever writing code | Zevi Arnovitz, at 56:58▶ watch at 56:58
Key Quote

“And I think, contrary to what a lot of people think, it's the best time to be a junior.”

— Zevi Arnowitz, How a Meta PM ships products without ever writing code | Zevi Arnovitz, at 1:07:13▶ watch at 1:07:13

Cite this

“How a Meta PM ships products without ever writing code | Zevi Arnovitz.” https://www.youtube.com/watch?v=1em64iUFt3U. Transcript summary by WhipScribe, https://whipscribe.com/transcript-pages/how-a-meta-pm-ships-products-without-ever-writing-code-zevi-.html.

Report this page
What is wrong with this page?