The opportunity
You're comfortable in front of enterprise customers, and you go looking for those conversations rather than waiting for them to be scheduled. You can tell the difference between a request that will block a deal and a request that's a minor annoyance, and you can explain how you reached that conclusion.
What you'll do
Run a continuous rhythm of customer conversations: discovery calls, renewals, and support signal
Turn enterprise requirements into clear specs engineering can build from,: with the underlying problem attached, so the team can make good calls without you in the room
Maintain one prioritized roadmap that shows what's shipping, what got moved to make room, and why
Attach an expected business impact to significant roadmap items so tradeoffs can be argued with evidence
Assess incoming enterprise requests for criticality and pattern: is this one customer, or the first of many
Manage expectations across sales, leadership, and customers when priorities change
What they're looking for
- + years in product management, including recent hands-on IC work. You've: owned a roadmap yourself, not only through a team
- Experience with enterprise customers: discovery, requirements gathering, and expectation management with large accounts
- Track record of quantifying the business impact of roadmap decisions and: defending prioritization to stakeholders who disagree
- Comfortable in a technically deep domain such as databases, data: infrastructure, distributed systems, or developer tools. You don't need an engineering background, but you do need to hold your own with tech leads
- Experience running product process in Linear or a comparable tool, with a: clear opinion on how it should be set up
- Strong written communication. Most of our decision-making happens in docs
- Some people management experience, or clear readiness to take that step with a team of one to three
- Working hours between GMT and ET, with flexibility for an occasional early or late call.
