About the role

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 http://OpenGov.com. ABOUT THE ROLE OpenGov is seeking a Product Engineer II to take on increasing ownership of a product area with cross-functional exposure. This role is for developing practitioners who can contribute to discovery, roadmap input, and delivery with general direction from a lead, while growing their ability to operate independently. AI-native tooling accelerates execution — your job is to direct it toward the right outcomes for customers. HOW AI WORKS IN THIS ROLE AI-native tooling handles a significant portion of what product managers and UX designers have historically spent their time on. That time is yours to redirect toward higher-leverage work. Specifically: - Spec writing: AI drafts the first spec from your intent statement. You review, sharpen, and own what gets built. - UX design: AI generates mockups from the design system based on your flow definitions. Experience Architects maintain the system itself. You make the product decisions within it. - Research synthesis: AI clusters and themes interview notes, call transcripts, and support data. You interpret what it means for the roadmap and make the call. - Release content: AI generates release notes, in-app announcements, and enablement materials from your shipped features. - Code review: Automated review catches style, security, and regression issues. You stay accountable for quality outcomes — not the review queue. - Test coverage: AI generates test cases from the acceptance criteria you write. Your job is to write criteria that are precise enough to verify. - Competitive intelligence: AI monitors competitor moves and surfaces market signals. You form the point of view and decide what it means for your roadmap. What AI does not do: understand your customers, make the call on what matters, own the outcome, or build the cross-functional trust that makes things ship. That is the job. WHAT YOU'LL OWN - Define and communicate the product vision for your area — grounded in customer research, competitive context, and business goals; not inherited from committee. - Conduct and synthesize customer discovery: translate what you hear into clear, defensible decisions about what to build and what to cut. - Own the product roadmap: prioritize ruthlessly, explain your reasoning publicly, and revise it when new facts warrant it. - Define user experience flows and interaction patterns within the design system; escalate to Experience Architects when genuinely new system-level patterns are required. - Write clear intent documents that AI tooling can execute against; review and own AI-generated specs for accuracy, completeness, and correctness. - Partner with engineering to unblock builds, resolve ambiguity in real time, and make decisions during the development cycle without becoming a bottleneck. - Track adoption, usage, and business outcome metrics; use them to drive the next iteration, not just to report status. - Represent your product in customer conversations, QBRs, and cross-functional reviews — the full commercial picture, not just the feature set. - Identify gaps in AI harnesses