The RoleCentralSquare builds Hero-Grade™ technology for the people who answer the call when everything is on the line. This Product Manager will own execution of the roadmap for Vertex, our NG911 call handling solution, and the connectivity work that keeps Vertex ahead of Next Generation 911 (NG911) and ESInet standards. This is the day-to-day owner of one of our most mission-critical product lines - these systems cannot tolerate downtime, and the person in this role treats that responsibility as personal.
We're looking for genuine customer obsession: a PM who understands the jobs-to-be-done of a 911 telecommunicator, a dispatcher, and the agencies that depend on reliable call handling as well as they understand it themselves, and who turns that understanding into a roadmap the field trusts before it ever reaches a release note. We want a bias to action over a bias to process, and a partner who represents product with equal conviction in an engineering standup and in front of a customer.
What You'll Own- Vertex roadmap execution: own and drive the day-to-day roadmap for Vertex, prioritizing ruthlessly against agency outcomes, not internal noise.
- NG911 & connectivity fluency: bring current, working fluency in NG911 and ESInet architecture to every roadmap and prioritization decision, positioning Vertex connectivity ahead of NG911 standards rather than reacting to them.
- Customer obsession: know the jobs-to-be-done of call-takers and dispatchers at real depth. Spend time in the field, let it override assumptions when the data and the field disagree, and build a roadmap the field recognizes as their own.
- Time to value: treat faster time to value as a first-order outcome - shrink the gap between contract signature and first meaningful outcome for Vertex, and treat onboarding/activation speed as a roadmap priority, not a services afterthought.
- Bias to action: default to shipping and course-correcting over lengthy analysis. Make the call, own the outcome, and move the roadmap forward on a weekly cadence.
- Cross-functional execution: partner tightly with engineering, sales, services, and support so that connectivity, reliability, and cloud migration work on Vertex is sequenced against real customer risk, not just backlog age.
- Operational visibility & follow-through: track roadmap items, support requests, and open commitments proactively, and surface progress - or misalignment with stated goals - to leadership before it becomes a surprise, rather than waiting to be asked.
- Stakeholder presence: stay genuinely available and responsive across internal (engineering, sales, support) and external (agency, field) stakeholders at once - this role doesn't get to go quiet on one group while focused on another.
- Market and competitive intelligence: track competitive and market movement in NG911 and call handling (Carbyne, Motorola, Tyler, RapidSOS, and others) and translate it into specific roadmap and packaging recommendations.
- Portfolio alignment: feed field insight, roadmap trade-offs, and NG911 standards developments into broader portfolio strategy across Vertex, Enterprise, OneSolution, and ProSuite Mobiles/RMS/JMS.
What Success Looks like in the First 12 Months- Agencies describe this PM as someone who understands their world, not someone who reads it back to them from a deck.
- The Vertex roadmap reflects NG911 readiness and connectivity resilience and compliance as first-order priorities, not backlog items.
- Agencies see tangible, measurable value from Vertex early - faster time to first value, not just discussed in QBRs.
- Cross-functional partners treat this PM as the trusted owner of the Vertex/NG911 space, not someone who needs the roadmap re-explained.
- Engineering and support trust this PM's work without re-checking it - when this PM digs into a client issue or reproduction steps, the write-up is treated as reliable enough to act on directly, not re-verified from scratch.
- Leadership can state roadmap status and risk without pinging this PM first - tracking and upward communication are proactive enough that leadership isn't the one initiating the check-in.
- Roadmap docs and release notes are trusted and acted on by people who weren't in the room - written artifacts carry enough clarity and weight that they don't need a live follow-up conversation to be understood or executed against.
Skills & Requirements
Requirements:- 4+ years in product management, ideally including enterprise or mission-critical software.
- Required: direct, hands-on experience with 911 call handling.
- Working knowledge of NG911 and ESInet architecture.
- AI DLC fluency: working familiarity with the artificial intelligence development lifecycle and release cadence, enough to sequence roadmap decisions realistically against engineering capacity and release timing.
- Ticket-level investigative instinct: comfort digging into "what happened" on a client-reported issue - gathering the right information, separating signal from noise, drawing themes from individually reported items, and working with engineering to reproduce a defect rather than relaying it secondhand.
- Product adherence & configurability fluency: ability to explain, internally and externally, how Vertex actually works, why it's built that way, and what's configurable - separate from the "voice of the customer" side of the role; this is the "voice of the product" side.
- Self-directed problem ownership: willingness to build the full story of an issue independently - who, what, where, when, why, how - and either define a path forward or defend current functionality, without waiting for someone else to frame the problem first.
- A track record, not just a claim, of customer obsession: specific examples of building deep enough fluency in your customers' jobs-to-be-done that it changed a roadmap decision.
- A proven bias to action: specific examples of decisions you made quickly with incomplete information, and how they played out.
- Comfort partnering with engineering, sales, and services leadership, and representing the roadmap to customers directly.
- Written communication: able to put a roadmap decision or trade-off in writing clearly enough that it stands on its own in a release note, a roadmap doc, or a leadership update - not just defensible live in the room.
- Working knowledge of cloud architecture (AWS or Azure); applied AI or machine learning exposure is a plus.
- Good judgment under ambiguity, and the confidence to make and defend a call without waiting for a perfect data set.
- Remote work discipline: proven ability to engage and deliver independently outside an office setting.
Qualifications