SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
OpenGov is hiring a Product Engineer III to own a domain within its ERP platform serving local and state governments across the U.S. This is a full-stack product ownership role where you will be the directly responsible individual (DRI) for a defined set of customers, problems, and measurable business outcomes.
You will own end-to-end product responsibilities: customer discovery, roadmap definition, user experience design, build coordination, launch, and adoption metrics. The role leverages AI-native tooling to handle execution work historically requiring three specialists (PM, designer, engineer), freeing you to focus on high-leverage judgment calls—the decisions that matter most, such as chart-of-accounts design choices that customers live with for a decade or reporting models that satisfy auditors.
Possible domains include:
- Financial Management: general ledger, chart of accounts, accounts payable/receivable, cash receipts, fixed assets, purchase card, requisitions, bank reconciliation, project accounting
- Budgeting & Performance: budget creation, worksheets, multi-period adoption, amendments, transfers, workforce planning, performance measures
- Reporting & Financial Statements: financial report engine, multi-hierarchy and multi-entity reporting, GASB-compliant statements, datasets, pipelines, and transparency surfaces
- Procurement: intake through solicitation, evaluation, award, contract management, and vendor records
You will coordinate with adjacent domains (payroll, HCM, utility billing, tax, permitting, asset management) and embed with Professional Services on implementations, spending roughly 20–25 hours per implementation (concentrated in discovery) capped at about a quarter of your time. The remaining three quarters focus on your domain.
Key responsibilities include defining and communicating product vision grounded in customer research; conducting discovery with government finance staff; owning the roadmap with ruthless prioritization; defining UX flows within the design system; building with AI-native tooling; writing precise acceptance criteria; partnering with engineering leads; embedding with implementations; tracking adoption and business outcomes; representing your domain in customer conversations and cross-functional reviews; and coordinating across domains when customer needs span multiple areas.
AI-native tooling handles spec writing (prototype-first, no PRD), UX design (AI generates screens from design system), research synthesis (AI clusters interview notes and call transcripts), release content, code review and test coverage, and competitive/regulatory monitoring. You are expected to improve the tooling itself by identifying gaps and surfacing platform investment requests.
REQUIREMENTS (Non-Negotiables, ranked by importance):
- Ownership under ambiguity: you make good decisions with incomplete information and iterate faster than waiting for certainty. You thrive as a sole DRI accountable for outcomes, not as part of a PM-designer-engineer trio.
- Demonstrated product ownership with a track record: product management, product design, or closely adjacent role where you shipped things customers use and can point precisely to what you owned versus what the team owned.
- Depth in a complex, workflow-heavy, compliance-bound B2B domain: financial software, ERP, accounting, or comparably regulated enterprise domain where being wrong had consequences beyond a churned subscription.
- Customer discovery you have actually run: you have conducted discovery, synthesized research yourself, and changed a roadmap or design because of what you learned (with a specific example).
- Written communication: you can articulate product decisions clearly enough that engineering, design, services, and leadership walk away aligned without a follow-up meeting.
- Willingness to build: code fluency must read as a career accelerator, not a threat. Experience in AI-native workflows is a plus; willingness to become proficient is required.
PREFERRED EXPERIENCE:
- Government finance, public sector accounting, or GovTech SaaS background, or direct experience as a finance officer, budget analyst, auditor, or controller
- Familiarity with fund accounting, chart-of-accounts design, GASB reporting, annual budget cycles, or external audit workflows
- Experience with data migration or platform replacement programs where the hard part was the customer's existing data
- Multi-entity or multi-organization data models, consolidated reporting, or component-unit structures
- Hands-on time with AI development tooling (Claude Code, Cursor, or similar) and with design systems and component libraries
