Zevi Arnovitz
The complete AI workflow that lets non-technical people build real products in Cursor.
Episode
The non-technical PM’s guide to building with Cursor | Zevi Arnovitz (Meta)
Summary
Zevi Arnovitz, a non-technical PM at Meta, shares his complete workflow for shipping real products using Cursor with Claude Code, having built functional internal tools without engineering background. He covers his system for reviewing AI-generated code by having multiple AI tools review each other's work, how he uses vibe coding as an exploratory prototyping tool before handing off to engineers, and his view that product management as a title is collapsing as builders can now ship end-to-end.
Key Takeaways
Have multiple AI tools review each other's code — run /review in Cursor and simultaneously ask Codex to review the same output — to catch mistakes you can't catch yourself as a non-technical builder.
Use AI-built prototypes as communication tools with your engineering team, not as production code: build a prototype of the feature you want, send it to engineers as a spec.
Treat vibe coding as rapid exploration to validate ideas before committing resources — if the prototype doesn't feel magical, the idea may not be worth pursuing.
Product titles are collapsing: the PM who can prototype, the designer who can ship, and the engineer who thinks about UX are converging into a single role.
Non-technical people who are not afraid of AI tools have a structural advantage: they don't know what's impossible, so they attempt things technical people self-filter out.
Notable Quotes
“And it was like a crazy moment for me because I was watching this and it basically felt like someone came up to me and said, "Hey Zevi, there's this cool new technology you should check out. You should really give it a try. Oh, and by the way, you have superpowers now." And the second I got home from Japan, I didn't even unpack my bags, ran to my computer, opened Bolt, opened an account, and for the past year I've been building.”
“It's very difficult for me to catch mistakes. What I'll do is basically /review. This tells Claude to start reviewing its own code, but what's even cooler is I have Codex as well as Cursor open. I will have each of them review the code.”
“The first thing I noticed was that these products were built in a way where, and when I say these products, I mean Bolt and Lovable, were built in a way where they were super eager to write code. So their system prompt was you're a coding agent. So when you'd write something, they'd straight away start coding. So at the beginning of a project, this was super fun and exciting because they just go and start building your app.”