The Builder PM
The AI-era product role, defined.
The short version
Builder PM is the AI-era successor to the Product Manager. Where a PM wrote specs, a Builder PM ships working prototypes (often with Claude Code or similar). Where a PM wrote PRDs, a Builder PM writes evals before code. Where a PM owned scope-timeline-headcount, a Builder PM owns cost-latency-quality per request. The job is not a rename; it's a different role with a different ladder, a different interview, and a different artifact. This page is the entry point to falkster's full body of work on the role, authored by Falk Gottlob (CPO with five exits).
Start with these three.
The thesis, the ladder, and the engineering counterpart. If you read nothing else, read these.
- 01
The PM Role Is Being Rewritten in Real Time. Are You Rewriting Yourself?
AI-forward companies are hiring for 'Product Builders.' This isn't a quirky experiment. It's the new standard. Here are the six skills that actually matter now.
- 02
The Product Builder Job Ladder: From L4 to Principal, Four JDs You Can Fork Today
A complete, fork-ready job-description ladder for Builder PMs. Four levels calibrated to scale from your first Builder hire to your most senior IC. Each level downloadable as its own file.
- 03
The AI Product Engineer: One Person Doing What Used to Take a Team
AI is blurring the lines between PM, design, and engineering. The people who can work across all three with AI tools are going to own the next decade of product.
From the handbook
Operating chapters that define what the role does, how to hire for it, and how to ramp into it.
Handbook
Your Weekly Playbook
What a week actually looks like when you're running the full handbook - discovery, prototyping, outcomes, and AI agents working together.
Handbook
The Builder PM 30/60/90
The 90-day plan for making the shift from traditional PM to product builder. Done in order. In 90 days, you have a different job.
Handbook
Hiring the Builder PM
Most PM hiring loops test skills the role no longer needs. Hire by what they can ship, not by how they talk about shipping.
Handbook
PM-as-Editor: Managing a Fleet of Agents
The 39-agent chapter told you what to deploy. This is the skill you need once they're running: great editing at volume.
Keep reading
The full Builder PM reading path. Career ladder, interview prep, hiring lens, the cases for and against.
Questions, answered
The seven things every PM, hiring manager, or curious engineer asks about the Builder PM role.
Q.What is a Builder PM?
A Builder PM is the AI-era successor to the Product Manager role. Where a PM wrote specs and ran rituals, a Builder PM ships working prototypes (often with Claude Code or similar), writes evals before code, owns one or more product surfaces end-to-end, can defend cost-per-request to finance, and treats AI agents as teammates with prompts, evals, and ship-readiness gates. The role is not a rename; it's a different job description.
Q.How is Builder PM different from Product Manager?
Five axes: (1) Builder PMs ship working surfaces, PMs write requirements; (2) Builder PMs write evals as the unit of work, PMs write PRDs; (3) Builder PMs own cost/latency/quality per request, PMs own scope/timeline/headcount; (4) Builder PMs hire agents as teammates, PMs hire engineers as resources; (5) Builder PM cycle time is days; PM cycle time is weeks. Companies that haven't made the switch are paying for both jobs and getting neither.
Q.Do I need to know how to code to be a Builder PM?
You need to be able to ship a working surface. Claude Code, v0, Cursor, and Replit make that achievable for anyone who can write a clear prompt and read a diff. The bar isn't 'senior engineer'; the bar is 'can take a hypothesis to a clickable thing in an afternoon without filing a ticket.' Most Builder PMs we work with started as non-coding PMs and learned by shipping inside their existing role.
Q.What's the Builder PM career ladder?
Falkster's ladder runs Builder PM I → Builder PM II → Senior Builder PM → Staff Builder PM → Principal Builder PM, with a head-of-product fork at Staff. Each rung adds scope (one surface → multiple surfaces → a portfolio), agent fleet ownership (running 1-3 agents → running a stack → designing the architecture), and influence (a team → a product area → an org). The full ladder lives at /blog/product-builder-job-ladder.
Q.How do I interview as a Builder PM?
Three things hiring managers screen for: (1) Can you ship? Bring a prototype you built yourself, walk the cost/latency/quality decisions. (2) Can you write evals? Show a real eval rubric you've shipped — pass/fail criteria, ground-truth set, sample size. (3) Can you do agent design? Whiteboard one agent end-to-end: trigger, prompt, eval, ship-readiness gate. Specs and frameworks are no longer credentials.
Q.How does a hiring manager spot a Builder PM vs a traditional PM?
Resume tells. (a) GitHub link on the resume, not just LinkedIn; (b) shipped surfaces named with metrics, not feature lists; (c) eval rubrics or agent prompts in a portfolio; (d) cost-per-request numbers in past roles; (e) talks fluently about LLM provider tradeoffs (Anthropic vs OpenAI vs open-weight) without prompting. The hiring guide lives at /handbook/hiring-the-builder-pm.
Q.What's the Builder PM 30/60/90?
Day 1-30: ship one prototype solo, no engineers attached. Day 31-60: stand up one production agent end-to-end with its eval harness. Day 61-90: own a cost/latency/quality scorecard for one product surface. By 90 you should have replaced at least one PM artifact (PRD, roadmap doc, status update) with a working surface or agent. Full playbook at /handbook/builder-pm-30-60-90.
If this was useful, the Monday Dispatch is where I share more of it.
One email, once a month. Five-minute read. No filler.
Unsubscribe anytime.