About the role
Responsibilities:
- Own discovery for your area. Run customer and prospect conversations every week, and turn what you learn into a clear view of who you are rebuilding for and why it matters to them.
- Make evidence-based calls. Instrument what you ship, state your confidence level upfront, and track whether you were right so your judgment keeps improving.
- Partner through the build, not just at kickoff. Work with engineering and design end to end, and give everyone in release, support, and sales- whoever's downstream- a real briefing instead of a surprise.
- De-risk before you build. Test your riskiest assumptions before you commit engineering time to them.
- Prioritise ruthlessly. Keep one ranked backlog sized against real customer demand, and be ready to defend the business case and trade-off behind every roadmap call.
- Ship iteratively. Deliver a working increment every sprint, each one tied to a real outcome or a learning.
What success looks like:
- A clear, prioritized roadmap for the area you own, with an explicit plan for how scope grows from there.
- Measurable reduction in time and friction from ready to negotiate to signed within your area.
- Issues resolved through the product, not through a standing support escalation queue.
Requirements:
- Product management experience owning a feature or workflow end-to-end to a measurable outcome.
- Years of experience matter less than the scope you've handled: tell us what you've owned, and we'll calibrate the role to it.
- Comfortable working in a high-usage, multi-stakeholder area where prioritization itself is a core skill, not just execution.
- Background in document collaboration, e-signature, contract/legal tech, or workflow automation products is a strong plus.
- Comfortable ramping quickly in a legal or contract-heavy domain if you don't already have that background.
Nice to have:
- Prior experience in a regulated domain where explainability/audit was a hard requirement rather than a nice-to-have.
- Exposure to agent-action protocols (e. g., MCP) or policy-engine design for agentic systems.