Product Engineer III

Overview

Own a domain within OpenGov's ERP for state and local government as a Product Engineer. Drive the product vision, customer discovery, roadmap, user experience, build, launch, adoption, and business outcomes for that domain as a directly responsible individual.

What you'll do

• Define and communicate the product vision for your domain, grounded in customer research, competitive context, and business goals.
• Conduct and synthesize discovery with government finance staff and translate findings into decisions about what to build and what to cut.
• Own the roadmap, prioritize work, explain your reasoning publicly, and revise it when new facts warrant it.
• Define user experience flows and interaction patterns within the design system and escalate genuinely new system-level patterns.
• Use AI-native tooling to move from intent to working software in the product repo, validate with customers, iterate, and own your PRs through review.
• Write acceptance criteria precise enough for automated tests to verify and own quality outcomes.
• Partner with engineering leads and squad engineers to unblock builds and resolve ambiguity.
• Embed with Professional Services on implementations and migrations, run discovery, close product-configuration gaps, and feed findings into the roadmap.
• Track adoption, usage, go-live health, and business outcomes to drive iteration.
• Represent your domain in customer conversations, QBRs, steering committees, and cross-functional reviews.
• Coordinate directly with adjacent domains when customer needs span more than one domain and bring a recommendation.
• Improve AI tooling by identifying gaps in AI harnesses, skills, and design system coverage and surfacing platform investment requests with a clear business case.
• Spend roughly 20–25 hours per implementation, concentrated in discovery with lighter oversight through configuration and training, capped at about a quarter of your time.
• Fix bugs on site rather than filing a ticket and waiting.

What you'll need

• Ownership under ambiguity, including making good decisions with incomplete information and iterating faster than waiting for certainty.
• Demonstrated product ownership with a track record in product management, product design, or a closely adjacent role, including shipped products customers actually use and a precise account of what you owned versus what the team owned.
• Depth in a complex, workflow-heavy, compliance-bound B2B domain, such as financial software, ERP, accounting, or a comparably regulated enterprise domain.
• Customer discovery experience, including conducting discovery, synthesizing research yourself, and changing a roadmap or design because of what you learned.
• Written communication sufficient to articulate product decisions clearly to engineering, design, services, and leadership.
• Willingness to build and become proficient in AI-native workflows; you do not need to arrive as a developer.
• This is an individual-contributor role, not a management role.

Nice to have

• Government finance, public sector accounting, or GovTech SaaS experience, or direct experience as a finance officer, budget analyst, auditor, or controller.
• Familiarity with fund accounting, chart-of-accounts design, GASB reporting, the annual budget cycle, or external audit workflows.
• Experience with data migration or platform replacement programs where the hard part was the customer's existing data.
• Experience with multi-entity or multi-organization data models, consolidated reporting, or component-unit structures.
• Hands-on experience with AI development tooling such as Claude Code, Cursor, or similar, and with design systems and component libraries.
• Experience in AI-native workflows.

Details

• Location: Pune, India.
• The role owns a domain within OpenGov's ERP, depending on fit: Financial Management; Budgeting & Performance; Reporting & Financial Statements; or Procurement.
• Adjacent domains include payroll and HCM, utility billing, tax and revenue, permitting, and asset management; the role coordinates with them but does not own them.
• Product Engineers are members of Customer Product Squads alongside an Engagement Lead and a Solution Architect and stay on accounts after go-live.
• The role is an individual-contributor position.