OpenGov is the leader in AI and ERP solutions for local and state governments in the U.S. More than 2,000 cities, counties, state agencies, school districts, and special districts rely on the OpenGov Public Service Platform to operate efficiently, adapt to change, and strengthen the public trust. Category-leading products include enterprise asset management, procurement and contract management, accounting and budgeting, billing and revenue management, permitting and licensing, and transparency and open data. These solutions come together in the OpenGov ERP, allowing public sector organizations to focus on priorities and deliver maximum ROI with every dollar and decision in sync. Learn about OpenGov’s mission to power more effective and accountable government and the vision of high-performance government for every community at OpenGov.com.
About the Role
OpenGov is hiring a Product Engineer to own a domain inside our ERP — the financial system of record for state and local government. You will own a product area end to end: customer discovery, the roadmap, the user experience,
the build, the launch, and the adoption number. This is a recent kind of role, born from AI's ability to handle execution work that once required three specialists. What AI cannot do is decide what matters, sit with a finance director through a budget cycle, make the right call in an ambiguous compliance question, or own whether a product succeeds. That is what Product Engineers do.
The shift to Product Engineering is primarily about owning the product — not becoming an engineer. The best Product Engineers are obsessed with the who and the why: who are these customers, what do they actually need, and what business outcomes depend on solving their problems. The how — writing code, building interfaces — is a skill you grow into using AI-native tooling. It is a career accelerator, not a job requirement on day one.
"Product Engineer" is two words — but the first word is the one that matters most. T
📌 Product Engineer III (Pune)
🏢 OpenGov
📍 Pune