AI Product Manager || Remote

What this role actually is

You'll own one or more product areas end-to-end from "why are we building this" to "is it working." Not in a write-tickets-and-hand-off way. In a you-are-the-person-who-knows-this-area-better-than-anyone way.

You will:

• Own product strategy, roadmap, and execution for your area email sequencing, AI agents, dialer, CRM, or lead prospecting. You go deep.
• Write PRDs and specs that engineering can build from without a follow-up meeting to clarify what you meant.
• Use data, user research, and your own product instincts to decide what to build, what to kill, and what to ignore.
• Work directly with engineers, designers, support, and marketing not as a coordinator, but as the person with the clearest picture of where we're headed.
• Ship. Frequently. Then measure, learn, and iterate.
• Use modern tools — including LLMs and AI — to move faster. We don't care if you can write a perfect SQL query from memory. We care that you know exactly what question to ask and can get to the answer, using whatever tool gets you there.

How we work (and how we don't)

• You think before meetings, not during them. You come with a recommendation, a framework, or a decision to be made not an open-ended brainstorm with 8 people in the room.
• You communicate proactively. If someone messages you, they don't have to follow up. If something is blocked, you flag it before anyone asks.
• You balance vision with shipping. Knowing what to build is important. Actually building it is non-negotiable.
• You manage relationships deliberately. PMs are the connective tissue between teams. Your tone, your clarity, and your follow-through determine whether people trust you. We take that seriously.

If this sounds like how you already operate — keep reading.

You'll thrive here if you have

• 4–7 years of product management experience in B2B SaaS. You've shipped real products to real users and have the scar tissue to prove it.
• A strong technical foundation. You understand APIs, software architecture, and data flows well enough to have meaningful conversations with engineers — and to know when a "small change" isn't small.
• A sharp analytical mindset. You know what questions to ask of your data. You can define the right metrics, spot the right patterns, and use modern tools (SQL, LLMs, analytics platforms) to get to answers fast.
• Excellent communication and stakeholder skills. Written and verbal. Async and live. With engineers, with leadership, with customers. Clear, concise, no fluff.
• A startup operating system. High ownership, low ego. You don't wait for permission. You don't need hand-holding. You figure it out and move.