Staff Product Manager

The Role: This is our first PM hire. Product at Dioptra has been owned by the founders. The goal is to have you work very closely with them. You’ll take it over: set the direction for Contract OS, decide what we build and what we don't, and stay with it until enterprise teams are actually running their contracting work on it. Our customers are very good at telling us what hurts today. Your job is to figure out what they'll need a year from now and make the case for building it now. We think of this as a revenue role. What you choose to build determines which deals we win, which customers expand, and how quickly agents take over work that legal, procurement, and GTM ops teams still do by hand — and you'll be measured on that, not on features shipped. Above all, we're looking for a founder's instinct. You own the outcome from end to end. You have strong opinions, back them with evidence, change your mind when someone has a better one, and then commit. You move with urgency when the problem is half-defined, and you know when to trust what customers are asking for and when your own judgement has to override it. Here's what that looks like day to day, and what it takes to do it well: Own Contract OS end to end. Strategy, a rolling 3–6 month roadmap, and a point of view on where the platform goes over the next year — from the first customer conversation through launch, adoption, and iteration. You decide what matters next and what can wait, and you can explain why you said no, not just what you said yes to. Live with customers. Sit on calls, watch legal, procurement, and GTM ops teams move a contract across Word, SharePoint, SAP, and Icertis, and dig through transcripts and tickets. Separate signal from noise, and turn what you learn into product direction — not a backlog of feature requests. Prototype before the meeting. Use Claude Code, Cursor, or whatever is fastest to turn an idea into something people can click and put it in front of customers and engineers. Show, don't tell. This means you've actually built with these tools, not just watched a demo. Know how agents actually work. Understand our agent architecture well enough to talk tradeoffs with engineering — context, evals, latency, model behavior, where a step should be deterministic vs. probabilistic, why a prompt breaks — and to explain to a customer what's possible and what isn't. Challenge engineering assumptions; don't just relay them. Design for trust. Contracts are high-stakes, regulated work. Treat evidence, auditability, permissions, and human review as core product, not afterthoughts. Our buyers won't hand work to an agent they can't verify. Ship features that land, not features that launch. Partner with sales, marketing, and customer success on positioning, launches, and enablement, and sequence releases against the enterprise go-to-market calendar. Define success before you ship, pull your own numbers, and go back to check whether you were right. Be the connective tissue. Sit between the founders, engineering, customer success, and sales, and make complicated things clear to people who aren't in the weeds with you. Your specs and decision docs should be clear enough for one engineer to ship from — and should reduce meetings, not create them. Build the product function. How we prioritize, how we document, how we run launches, and how we measure what worked. The frameworks you set up are the ones the product team will grow into. You'll have an edge if: You have 4+ years in product management at B2B SaaS or AI-native companies, including something you personally took from a vague idea to a product customers rely on — and you can explain what you shipped, why, and what happened afterward. You've shipped AI or LLM-based products into production, where AI is the core of the product, not a bolt-on. You've worked at an early-stage startup (seed to Series B), you're a past founder, or you've been the first PM somewhere — and you have opinions about what you'd do differently the second time. You've built for enterprise buyers — legal, procurement, finance, or another regulated team with a sophisticated buyer and a long trust curve. You know the contracting world — CLM, ERP, procurement systems, or legal ops. You don't need a legal background, but you should care how these teams think and what makes them trust a new tool. You're self-sufficient with data: comfortable with funnels and cohorts, pulling your own numbers with SQL or coding agents, and questioning how a metric is defined. The Team You'll Work WithYou'll work directly with the founders of Dioptra, who have owned product until now — expect a real handoff, and expect them to argue with you. You'll work shoulder to shoulder with an engineering team that holds a high bar — clean, deliberate work, iterative — and you'll be expected to bring the same rigor to product decisions. You'll also partner closely with sales, customer success, and marketing, and with product and field teams across Icertis. Given how early this seat is, you'll be the person setting the tone for how “product” gets done here going forward.

Equal Opportunity: Icertis is an equal opportunity employer. We consider all qualified applicants without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability, veteran status or any other characteristic protected by law. If you need accommodation at any stage of the process, tell us and we'll arrange it.