Product Manager - Core Management Platform

Job Summary

Required Qualifications

• •3+ years in product management, technical product ownership, or a closely adjacent role
• •Proven ownership of a product roadmap with measurable customer outcomes attached
• •Strong written and verbal communication
• •Direct, fact-based communication style
• •Ability to make a complex platform understandable to a customer executive
• •Ability to translate customer reality into language that lands with engineering
• •Ability to translate the technical reality of what you're building into language that lands with a customer exec
• •Comfortable getting on the phone with customers
• •Comfortable sitting inside a customer's workflow
• •Track record of identifying what to build next without being told
• •Ability to defend a call with evidence when challenged
• •Bias toward building things that do work for customers
• •Obsesses about ease of use as something you can measure
• •Counts clicks, page loads, and moments where the customer has to stop and ask 'what was I doing again'
• •Track record of shipping software improvements that current customers noticed and called out
• •Understands that removing friction is the highest-leverage thing the product can do
• •Partners with design as a peer
• •Believes happy customers using software that feels effortless is worth more than shiny features customers don't use
• •Treats API design as a product decision, not a backend concern
• •Understands how services connect, where boundaries belong, and how an API decision today shapes what is possible tomorrow
• •Has spec'd or owned APIs that other teams or integrations depend on
• •Knows what versioning, breaking changes, and durability actually cost
• •Can read an OpenAPI spec
• •Can push back on data model decisions
• •Can reason about how today's API decisions shape tomorrow's customer experience
• •Comfortable making the tradeoff call between a UI fix that ships today and an API fix that takes longer but compounds
• •Experience speccing or building agentic workflows
• •Understands what a tool call is
• •Understands how agents chain actions
• •Understands how to define success at the workflow level
• •Understands how failure handling shapes the customer experience
• •Can tell when a workflow should be replaced by an agent
• •Can tell when a workflow should not be replaced by an agent
• •Demonstrated ability to use AI tools (Claude, Claude Code, Cursor, v0, Lovable, etc.) as your primary product workflow
• •Uses AI tools for discovery, prototyping, spec generation, and working closer to the code
• •Track record of shipping AI-powered features with real success metrics
• •Has built something on the side (a personal project, an open-source tool, a deployed web service) that demonstrates your AI instincts are genuine

Desired Qualifications

• •A discovery method that's distinctly yours
• •Ability to walk through how you decide what to build and why
• •Track record of identifying what to build next without being told
• •Bias toward building things that do work for customers, not things that give customers more work to do
• •Obsesses about ease of use as something you can measure
• •Counts clicks, counts page loads, counts moments where the customer has to stop and ask 'what was I doing again'
• •Track record of shipping software improvements that current customers noticed and called out, not just internal-facing changes
• •Understands that for customers using a tool every day, removing friction is the highest-leverage thing the product can do, and the surest path to happier customers
• •Partners with design as a peer, not a consumer of design work
• •Believes happy customers using software that feels effortless is worth more than shiny features customers don't use
• •Treats API design as a product decision, not a backend concern
• •Understands how services connect, where boundaries belong, and how an API decision today shapes what is possible tomorrow
• •Has spec'd or owned APIs that other teams or integrations depend on
• •Knows what versioning, breaking changes, and durability actually cost
• •Can read an OpenAPI spec, push back on data model decisions, and reason about how today's API decisions shape tomorrow's customer experience
• •Comfortable making the tradeoff call between a UI fix that ships today and an API fix that takes longer but compounds for every customer surface that comes after
• •Experience speccing or building agentic workflows
• •You understand what a tool call is, how agents chain actions, how to define success at the workflow level, and how failure handling shapes the customer experience
• •You can tell when a workflow should be replaced by an agent, and just as importantly, when it shouldn't
• •Sometimes the answer is a UX fix or an API change, not an agent
• •Demonstrated ability to use AI tools (Claude, Claude Code, Cursor, v0, Lovable, etc.) as your primary product workflow
• •Not just for productivity, but for discovery, prototyping, spec generation, and working closer to the code
• •Track record of shipping AI-powered features with real success metrics
• •Not just launched, but measured against adoption, workflow reliability, or customer outcome
• •Has built something on the side (a personal project, an open-source tool, a deployed web service) that demonstrates your AI instincts are genuine, not just professional