Head of Platform

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Preserve all substantive info. We need to parse the posting. Content: - Position: Head of Platform (title) - The opportunity: description about Govineer Solutions, what they do, looking for Head of Platform to build foundation, lead move from legacy to cloud, operate production, make easier for product teams, remit includes CloudOps, developer and product tooling, data and AI infrastructure, relationships with hyperscalers and other strategic tech partners. Hands-on leadership role with real ownership of migration plans and production outcomes. Work with product engineering, security, finance, business leaders to choose practical paths from today's systems to more scalable platform, while protecting customer continuity. That's likely "About the role" or maybe "Responsibilities". We'll decide. Then "What you will own": list of bullet points (Set the platform strategy..., Lead CloudOps..., Design for demands..., Build shared infrastructure..., Establish secure infrastructure..., Shape platform capabilities..., Own cloud architecture..., Build and coach...). Those are responsibilities. Then "What you bring": list of bullet points (Significant experience..., A record..., Depth..., Strong operational judgment..., Experience building internal platforms..., Working knowledge of AI/ML infrastructure..., Nice to have: GovTech..., We welcome strong platform leaders...). Those are qualifications/requirements/skills. Then "What Success Looks Like": bullet points (Product teams can ship safely..., migrations proceed..., critical services have clear ownership..., cloud and AI costs are visible...). Could be maybe "Outcomes" but not a required heading. Could be part of responsibilities or maybe "Expectations". Not in list of allowed headings; we could maybe put under Responsibilities or maybe not include as separate heading because not in allowed list. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples but we can use those headings. It doesn't forbid other headings, but likely we should stick to those. However we could include a section like "Success Metrics" but not in list; maybe better to incorporate into Responsibilities or maybe a separate "Outcomes" not needed. Safer to not create extra headings. Then "What We Offer": bullet points (Mission-Driven Work, Flexibility, Comprehensive Benefits, Work Environment And Physical Requirements). This includes benefits and maybe schedule? It mentions remote-eligible role, comprehensive benefits: competitive compensation, health/dental/vision insurance, 401(k), PTO, paid holidays, professional development support. Also work environment: primarily office-based or remote role involving standard computer work. Ability to work independently, manage deadlines, high accuracy. Regular interaction. Primarily office-based or remote role with moderate travel (15-25% annually), consisting of on-site engagements, team meetings, company events. Occasional weekend travel may be required. Thus we have Benefits: competitive compensation, health/dental/vision insurance, 401(k), PTO, paid holidays, professional development support. Also flexibility: remote-eligible role. Also maybe schedule: moderate travel 15-25% annually, occasional weekend travel. Could be schedule. Pay: "competitive compensation" is mentioned but not specific numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive compensation" which is a statement about pay, albeit not specific. Is that enough? It says "competitive compensation" - that is a statement about pay. It's not placeholder like "commensurate with experience" etc. It's a real statement. So we can include Pay section with that statement. Benefits: we have health/dental/vision insurance, 401(k), PTO, paid holidays, professional development support. Also mission-driven work maybe not a benefit but could be under Benefits? Might be better to have Benefits section with those items. Mission-driven work maybe could be under About the role? But we can include as a bullet under Benefits? It says "Mission-Driven Work: Support an organization whose technology and services help local governments serve their communities more effectively." That's more like a benefit/value proposition. Could be under Benefits. Flexibility: remote-eligible role could be under Benefits or Schedule? Probably Benefits. Schedule: moderate travel 15-25% annually, occasional weekend travel. That's schedule info. Thus we will have sections: - About the role (maybe summarizing the opportunity paragraph) - Responsibilities (What you will own) - Requirements (What you bring - required qualifications) - Skills (maybe separate? Could combine Requirements and Skills but we need to decide. The posting includes both experience and technical depth; we could put Requirements for experience, Skills for technical depth. But we can also combine. However we need to avoid thin sections. Let's think: "What you bring" includes both experience and technical depth. Could split into Requirements (experience) and Skills (technical). But we have also "Nice to have" which could be under Requirements as optional. Might be okay to have a single Requirements section covering all. But we need to follow instruction: prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. That's 6 sections. Could also include Qualifications but that's similar to Requirements. We'll stick to those. Thus:

About the role

... (the opportunity paragraph)

Responsibilities

• Set the platform strategy and phased migration roadmap, including architecture, application and data dependencies, cutover plans, rollback plans, and retirement of legacy infrastructure.
• Lead CloudOps and site reliability practices: service levels, observability, incident response, disaster recovery, capacity, performance, and operational learning.
• Design for the demands of public-service software: availability during critical operating periods, secure handling of financial and resident data, clear audit trails, and customer-specific configuration.
• Build shared infrastructure and self-service tools for environments, deployment, identity, secrets, CI/CD, testing, and developer productivity.
• Establish the secure infrastructure for AI-enabled products, including model access, data boundaries, evaluation and monitoring, usage controls, and cost visibility.
• Shape platform capabilities that product teams can reuse through clear APIs and well-documented services, including integrations with legacy applications.
• Own cloud architecture and commercial decisions with hyperscalers and vendors; make cost, resilience, security, and portability tradeoffs explicit.
• Build and coach a lean platform team and define ownership boundaries with product engineering and security.

Requirements

• Significant experience leading cloud platform, infrastructure, SRE, or engineering teams that support customer-facing products.
• A record of moving complex production workloads from legacy environments to cloud services without losing control of reliability, security, or customer experience.
• Depth in cloud architecture, infrastructure as code, networking, containers, observability, identity, data platforms, and modern delivery practices.
• Strong operational judgment: you have led incidents, improved systems afterward, and can explain reliability and cost choices to executives.
• Experience building internal platforms and developer tools that teams willingly adopt.
• Working knowledge of AI/ML infrastructure and the controls needed to operate it responsibly in production.
• Nice to have: GovTech or regulated-software experience, especially across multiple acquired or long-lived products.

Benefits

• 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.

Pay

Competitive compensation.

Schedule

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.

We need to ensure we didn't include any boilerplate like EEO statement, Work Environment And Physical Requirements (we partially used travel info). We omitted the detailed work environment description (ability to work independently, manage deadlines, high accuracy, regular interaction). That is substantive; maybe we should include that under Schedule or Benefits? It's about work environment. Could be part of About the role? But we already used About the role for opportunity paragraph. Could add a paragraph under About the role covering work environment? However the instruction: preserve ALL substantive information. So we need to include that info somewhere. We could add a

under About the role after the opportunity paragraph, or maybe under Responsibilities? But it's not a responsibility. Could be under a new section like "Work Environment" but not in allowed headings. Could incorporate into Benefits? Not really. Could incorporate into About the role as a second paragraph. Thus modify About the role to include two paragraphs: first the opportunity description, second the work environment details. Let's capture the work environment text: "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." But we already used travel info in Schedule section; we should avoid duplication. The schedule section already includes travel and occasional weekend travel. So we should not repeat that. The work environment paragraph includes also ability to work independently, manage deadlines, high accuracy, regular interaction. We'll keep that in About the role. Thus About the role will have two paragraphs: first about opportunity, second about work environment (excluding travel details). We'll need to ensure we don't repeat travel. Let's extract work environment without travel: "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." We'll put that as second paragraph. Now schedule section will contain travel info only: "Moderate travel (15-25% annually), consisting of on-site engagements, team meetings, and company events; occasional weekend travel may be required." But we also need to mention primarily office-based or remote role? That's already in work environment. So schedule can just be travel. Thus final HTML. Check for any other substantive info: "What Success Looks Like" bullet points: we omitted. That is substantive. Should we include? Could be under Responsibilities or maybe a separate section like "Expectations". Not in allowed headings but we could incorporate into Responsibilities as outcomes? However they are success metrics, not responsibilities. Could be included under a section like "Expectations" but not allowed. Perhaps we can add a section "Outcomes" but not in list; risk of violating instruction? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples but not exclusive. However they say "Prefer a few substantive sections over many thin ones." Adding a thin section for success metrics might be thin but still substantive. Could incorporate into Responsibilities as "What success looks like" but that's not