Head of Product Engineering

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the posting. Content: - Position: Head of Product Engineering (title, not heading) - The opportunity: description paragraph about role. - What you will own: list of responsibilities (multiple bullet-like sentences). - What you bring: qualifications/requirements. - Nice to have: optional qualifications. - What success looks like: maybe outcomes. - What We Offer: includes Mission-Driven Work, Flexibility, Comprehensive Benefits, Work Environment And Physical Requirements (maybe schedule?). - There's also mention of remote-eligible role, flexibility, benefits, work environment, travel. We need sections: About the role (maybe from "The opportunity" paragraph). Responsibilities (What you will own). Requirements/Qualifications (What you bring + Nice to have). Benefits (What We Offer includes benefits). Possibly Pay? Not specified. Schedule? Not specified (flexibility remote-eligible, but schedule not given. Travel mentioned but not schedule. So we should not create Pay or Schedule sections unless present. Benefits: we have comprehensive benefits listed. Also mission-driven work, flexibility, work environment. Could be part of Benefits section or separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We likely need About the role, Responsibilities, Requirements (or Qualifications), Benefits. Possibly Skills? Not explicit. Could combine Requirements and Qualifications. We'll include Requirements (covers what you bring and nice to have). Benefits (covers mission-driven work, flexibility, comprehensive benefits, work environment). We'll not include Skills unless we have explicit skills list; we have fluency across modern full-stack etc. That could be skills but we can put under Requirements. We must not create empty sections. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we list each bullet as
• . For requirements we list each bullet. For benefits we list each bullet. We need to preserve all substantive info; do not invent or summarize away detail. Must not omit details. Let's extract details. About the role: The opportunity paragraph: "Govineer is seeking a Head of Product Engineering who has built and shipped multiple customer-facing software products and knows how to create strong, lean engineering teams. You will lead engineers across established local government products and new experiences for staff and residents, improving the quality and pace of delivery while modernizing legacy systems deliberately. You will work closely with the Head of Product on customer outcomes and with the Head of Platform on shared infrastructure. We want a leader who can discuss architecture and code with engineers, product value with customers, and tradeoffs with executives. You should be comfortable using AI to improve engineering work while retaining clear human accountability for design, quality, security, and production behavior." That's the about. Responsibilities (What you will own): list each sentence starting with a verb. - Lead product engineering from discovery and prototyping through launch, operation, measurement, and iteration across multiple product lines. - Build small, accountable teams with clear missions, strong technical leads, rapid feedback loops, and an appropriate mix of in-house and partner capacity. - Modernize legacy applications incrementally, reducing fragile dependencies while continuing to serve existing customers. - Define engineering practices for architecture, code review, automated testing, CI/CD, observability, accessibility, security, and reliable releases. - Protect the accuracy of high-stakes workflows such as billing, payments, and financial reporting, with explicit attention to data migration, auditability, and safe rollout. - Deliver full-stack products and reusable APIs that work for both new experiences and existing consumers, including legacy applications. - Partner with Product, Design, Data, and customer-facing teams to turn real user problems into measurable product outcomes. - Set the approach for data and AI-enabled features, including evaluation, privacy, quality, monitoring, and human review where needed. - Hire, coach, and retain engineers and managers; create a culture of ownership, learning, and candid technical debate. That's all. Requirements (What you bring): list each bullet. - A strong software engineering foundation and senior leadership experience in teams that have repeatedly shipped and operated customer-facing products. - Evidence of building effective teams and improving delivery without sacrificing product quality or reliability. - Fluency across modern full-stack engineering, APIs, cloud systems, data architecture, and the practical use of AI/ML in products. - Experience modernizing legacy software through staged changes, integration patterns, and careful migration rather than abstract redesign alone. - Good product judgment and an ability to work directly with customers, product managers, designers, and commercial leaders. - Clear technical communication and the ability to make difficult tradeoffs visible. Nice to have: (optional) - GovTech, payments, financial software, or other regulated-product experience. - Demonstrated product engineering leadership matters most. (Actually that line is a statement; maybe treat as part of requirements? It says "Nice to have: GovTech, payments, financial software, or other regulated-product experience. Demonstrated product engineering leadership matters most." We'll include the first as nice to have bullet; second is a statement maybe not a bullet but we can include as a sentence under Requirements? It says "Nice to have: ... Demonstrated product engineering leadership matters most." Could treat as a note. We'll include as a bullet under Nice to have? But we don't have a Nice to have heading; we could incorporate into Requirements as optional. But instruction: we can have Requirements heading; we can include both required and nice-to-have items under that, maybe differentiate? Not required. We'll just include all under Requirements. But we must not invent or summarize away detail; we need to keep the nice-to-have line. We'll include as a bullet: "GovTech, payments, financial software, or other regulated-product experience." And maybe also include "Demonstrated product engineering leadership matters most." as a bullet? It's more a statement; but we can keep as bullet. What success looks like: maybe we could include as a section? Not in the list of headings but we could treat as "Outcomes" but not required. The instruction says we should include a section only when posting has real specific content for it; we could include a section like "Success Metrics" but not in the prescribed headings list. The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't include Success. So we should not create a section for success unless we map it to one of those headings. Could we treat success as part of About the role? Probably not. Better to omit success section, as not in allowed headings. But we must preserve all substantive information; if we omit success looks like, we lose info. However the instruction says we should not invent sections; but we can include success as part of About the role or Responsibilities? It's more about outcomes; maybe we can incorporate into About the role as additional paragraph. The About the role currently only has the opportunity paragraph; we could extend it to include success looks like. That would preserve info. Let's do that: after the opportunity paragraph, add a sentence: "Success looks like teams regularly ship useful customer improvements; legacy risk declines; quality and delivery speed improve together; architecture supports reuse across Govineer products." That is substantive. Now Benefits section: from What We Offer. - Mission-Driven Work: Support an organization whose technology and services help local governments serve their communities more effectively. - Flexibility: Remote-eligible role - Comprehensive Benefits: Competitive compensation, health/dental/vision insurance, 401(k), PTO, paid holidays, and professional development support. - Work Environment And Physical Requirements: This is a primarily office-based or remote role involving standard computer work. The position requires the ability to work independently, manage recurring deadlines, and maintain a high level of accuracy in a deadline-driven environment. Regular interaction with internal and external stakeholders is expected, with an emphasis on providing responsive, professional, and solution-oriented support. Primarily office-based or remote role with moderate travel (15-25% annually), consisting of on-site engagements, team meetings, and company events. Occasional weekend travel may be required to accommodate work and meeting schedules. We need to list these as bullet items. However some are sentences with colon. We'll treat each as a bullet. We must not include Pay section because compensation is mentioned under Comprehensive Benefits but not explicit pay range. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits is stated, so we can have Benefits. Pay is not explicitly stated as a range or salary; we have "Competitive compensation" which is a benefit but not explicit pay. The instruction says never create Pay section unless posting actually states them. It does state "Competitive compensation" but that's vague. Might be considered pay info? Safer to not create Pay section; we can include compensation under Benefits bullet. Schedule: not explicitly stated; we have flexibility remote-eligible role, but no schedule like full-time, part-time, hours. So we should not create Schedule section. Thus we will have sections: About the role, Responsibilities, Requirements, Benefits. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Benefits

  • ...
  ...
  Make sure to preserve all details exactly as in posting, but we can rephrase slightly? Must not invent or summarize away detail; we can keep the exact sentences. We'll copy them. Let's craft About the role paragraph: combine opportunity and success looks like. Opportunity paragraph: "Govineer is seeking a Head of Product Engineering who has built and shipped multiple customer-facing software products and knows how to create strong, lean engineering teams. You will lead engineers across established local government products and new experiences for staff and residents, improving the quality and pace of delivery while modernizing legacy systems deliberately. You will work closely with the Head of Product on customer outcomes and with the Head of Platform on shared infrastructure. We want a leader who can discuss architecture and code with engineers, product value with customers, and tradeoffs with executives. You should be comfortable using AI to improve engineering work while retaining clear human accountability for design, quality, security, and production behavior." Success looks like: "Teams regularly ship useful customer improvements; legacy risk declines; quality and delivery speed improve together; architecture supports reuse across Govineer products." We'll combine into one paragraph maybe two sentences. Now Responsibilities bullets: copy each exactly as in posting. Check each bullet for punctuation. - Lead product engineering from discovery and prototyping through launch, operation, measurement, and iteration across multiple product lines. - Build small, accountable teams with clear missions, strong technical leads, rapid feedback loops, and an appropriate mix of in-house and partner capacity. - Modernize legacy applications incrementally, reducing fragile dependencies while continuing to serve existing customers. - Define engineering practices for architecture, code review, automated testing, CI/CD, observability, accessibility, security, and reliable releases. - Protect the accuracy of high-stakes workflows such as billing, payments, and financial reporting, with explicit attention to data migration, auditability, and safe rollout. - Deliver full-stack products and reusable APIs that work for both new experiences and existing consumers, including legacy applications. - Partner with Product, Design, Data, and customer-facing teams to turn real user problems into measurable product outcomes. - Set the approach for data and AI-enabled features, including evaluation, privacy, quality, monitoring, and human review where needed. - Hire, coach, and retain engineers and managers; create a culture of ownership, learning, and candid technical debate.