# Product Builder **Level:** IC ยท L4 equivalent **Team:** Product **Reports to:** Senior Product Builder or Head of Product **Type:** Full-time **Location:** Remote (Global) with meaningful overlap in your primary product area's timezone. --- ## The Short Version This is not a traditional PM role. We are not looking for someone who writes requirements and waits for engineering. We are looking for someone who builds. You will take a workflow from concept to working prototype before a sprint starts. You will design AI systems, not just describe them. You will validate with real users, not decks. And you will own the full arc from insight to production for one product area. If that sounds like the job you have been trying to do inside a traditional PM role, this is the upgrade. --- ## What You Will Actually Do - **Prototype before planning.** When a new product opportunity surfaces, your first output is a working prototype, not a spec. You use Claude Code, Cursor, v0, or equivalent to build fast enough that engineering validation happens on something real. - **Design AI workflows end-to-end.** Input, reasoning, output, action. You decide where AI belongs, where rules are more reliable, and how to structure context so the system behaves predictably. - **Own the evaluation layer for your area.** You define what good output looks like before shipping. You build evals, monitor for drift, and create the feedback loops that keep AI features working after the demo. - **Reason about cost and latency.** You treat token usage, response time, and model selection as product decisions. You understand the unit economics of every feature you ship. - **Validate with users.** You put working things in front of real users early and often. You design feedback loops that generate signal, not sentiment. - **Ship.** Not someday. Fast. --- ## What We Are Looking For ### Must-haves - 4+ years in a product role, with at least 2 years working directly on AI-powered products - Demonstrated ability to build working prototypes using AI development tools (Claude Code, Cursor, v0, or equivalent) - Hands-on experience designing agentic workflows, including tool use, memory, and multi-step reasoning - Clear understanding of RAG, prompt architecture, and when to use models versus rules - Experience defining and running evals for AI features in production - Track record of shipping products, not just planning them ### Strong signal - You have built something on your own, outside of a job, using AI tools - You can walk through the cost and latency tradeoffs of a feature you shipped - You have worked in a paired product-engineering model where prototypes precede specs - You have owned a feature from zero to production, including the parts no one assigned to you ### Not required - Computer science degree - Ability to write production-ready backend code - Experience at a large company (small team instincts are a plus) --- ## What You Will Not Do - Write long PRDs that sit in Notion waiting for an engineering sprint - Coordinate meetings between functions that should be talking directly - Manage backlogs in isolation from the users they are supposed to serve - Treat AI as a feature category rather than a design medium --- ## How We Work We eliminated traditional PRDs. Product and engineering work in paired ownership, with prototypes expected within hours of a new idea. Reviews are outcome-based, not output-based. This is a high-trust, high-accountability model. You will have significant autonomy over what you build and how you build it. You will also be expected to show your work, early and often, in the form of working artifacts. --- ## Compensation and Benefits - Competitive base salary commensurate with experience - Equity participation - Remote-first, async-friendly team with significant overlap flexibility - Direct access to senior leadership and real ownership of a consequential product area - Learning budget with a strong bias toward hands-on tools over passive content --- ## How to Apply Skip the cover letter. Instead, send us: 1. **One example of a prototype or working artifact you built using AI tools.** A link, a demo, a repo, anything real. 2. **Two to three sentences on the workflow it automated or the problem it solved.** 3. **The cost or latency tradeoff you had to navigate** to make it work in practice, even if it was a side project. We will respond to every submission that includes all three.