Staff Product Manager (US)
Dioptra, an Icertis Company • New York City Metropolitan Area
Company
Dioptra, an Icertis Company
Annual salary
$180k – $250k/yr
Location
New York City Metropolitan Area
Listed
38d ago
- Experience:
- 5 to 10 years
- Workplace:
- 5 days in-office in New York City, NY (must be NYC-based or already moving here; no relocation support)
- Equity:
- None
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in New York City Metropolitan Area.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
We are looking for a Staff Product Manager with 5+ years of experience to become Dioptra's first PM hire and own product for Contract OS, our agentic AI platform for enterprise contracting. You'll take over product leadership from our founder (a PM by trade) and decide what gets built, taking the product from zero to one. We want a technical PM from an AI-native team, ideally the AI platform or recommendation teams at companies like Netflix or Spotify, or an AI-first startup. You should have worked closely with engineers and understand how long it takes to build. This is a founding-level seat with real ownership from day one, backed by Icertis's enterprise customer base.
What will you be doing?
- Owning the Contract OS product strategy and roadmap, deciding what gets built, what waits and why.
- Collecting and combining customer feedback from our forward-deployed legal engineers (lawyers working directly with customers) to set product direction.
- Working with engineering to plan and scope deliverables, adjusting sprint pace for AI-assisted development where work can ship in days instead of weeks.
- Talking through AI and agent architecture tradeoffs with engineers and prototyping ideas quickly with tools like Claude Code or Cursor.
- Building the product function from scratch: how we prioritize, write docs, run launches and measure success.
Common questions
How do I apply for the Staff Product Manager (US) role at Dioptra, an Icertis Company? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Dioptra, an Icertis Company role pay? +
The listing gives $180k – $250k/yr.
Is this role remote? +
The listing gives the location as New York City Metropolitan Area. 5 days in-office in New York City, NY (must be NYC-based or already moving here; no relocation support).
Product Manager interview prep
Questions Product Manager interviewers often ask. They aren't taken from this listing.
How do you rank competing feature requests when every stakeholder believes theirs is the most urgent one on the list?
I score each request against the outcome the team has committed to for the quarter, then weigh expected impact against the effort engineering estimates. That gives me a defensible order to show stakeholders, and when someone disagrees we argue about the inputs rather than about whose request matters more.
How do you structure a roadmap so it communicates direction without promising dates the team cannot keep?
I organize the roadmap around problems to solve in rough time horizons, now, next and later, instead of a dated list of features. Commitments get firmer as work gets closer, and I state plainly which items are bets and which are committed, so sales and leadership know what they can promise to customers.
How do you plan a round of user interviews so the findings change what you build rather than confirming what you hoped?
I write the riskiest assumption down first and design questions around past behavior, not opinions about a feature idea. Asking people what they did last time the problem came up produces evidence, while asking whether they would use something produces polite agreement that tells me nothing.
How do you combine quantitative usage data with qualitative interview findings when the two seem to disagree?
I treat the numbers as telling me what is happening and the interviews as telling me why, so a disagreement usually means I am measuring the wrong thing or talking to the wrong segment. I go back and check who is in each sample before drawing a conclusion, because resolving that mismatch is often the most useful finding of the whole study.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →