Head of IT

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules carefully: 1. Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) 2. Use

• for lists of duties/requirements/benefits, and

  for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - "Responsibilities" section (but it's actually a mix of team intro and responsibilities) - "About the Team" section - "Team Intro" section - "Key Responsibilities" with subsections: - IT Service Delivery & Employee Experience - Office Technology - IT Engineering (In-House VDI) - Automation & Agentic AI - Department Leadership & Strategy - Reliability, Security & Operational Governance - "Qualifications" with: - Minimum Qualifications (list) - Preferred Qualifications (list) - "About USDS TikTok" section - "Why Join Us" section - "Diversity & Inclusion" section - "USDS Reasonable Accommodation" section - "Job Information" with pay transparency details (base salary range, benefits, etc.) I need to structure this into appropriate sections. The rules say to use specific heading names: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Looking at the content: - "About the Team" and "Team Intro" could be "About the role" or "About the team" - "Key Responsibilities" maps to "Responsibilities" - "Qualifications" with Minimum and Preferred maps to "Requirements" or "Qualifications" - "Job Information" has pay and benefits info, so "Pay" and "Benefits" sections - "Why Join Us" could be part of Benefits or separate - "Diversity & Inclusion" and "USDS Reasonable Accommodation" are boilerplate-ish but might be kept as they're specific to the company The rules say: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate". Diversity & Inclusion and Reasonable Accommodation might be considered EEO boilerplate, but they're specific to USDS. I'll include them as they're part of the job posting content. Also: "never create Pay/Schedule/Benefits sections unless the posting actually states them" - the posting does state pay range and benefits, so I should include Pay and Benefits sections. Schedule: The posting mentions "fully in-person schedule up to 5 days a week" - that's schedule info. Let me organize: 1. About the role (combining About the Team and Team Intro) 2. Responsibilities (Key Responsibilities with subsections) 3. Requirements (Minimum Qualifications) 4. Qualifications (Preferred Qualifications) - or combine with Requirements? The rules list both "Requirements" and "Qualifications" as possible headings. I'll use "Requirements" for minimum and "Qualifications" for preferred, or maybe combine into one "Qualifications" section with subsections. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So both Requirements and Qualifications are valid. I'll use "Requirements" for minimum and "Qualifications" for preferred. 5. Benefits (from Job Information) 6. Pay (from Job Information) 7. Schedule (from the in-person work model mention) Also "About USDS TikTok" could be "About the company" but not in the example headings. I'll include it as "About the company" or fold into About the role. The rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)" - "e.g." means examples, not exhaustive. But "Prefer a few substantive sections over many thin ones." So I'll keep it as a section. "Why Join Us" is marketing fluff but has some substance about culture. Could be part of Benefits or separate. "Diversity & Inclusion" and "USDS Reasonable Accommodation" - I'll include as separate sections or combine. Let me draft the HTML. First, About the role: combine About the Team and Team Intro prose. Responsibilities: the Key Responsibilities with subsections. I'll use nested lists or separate lists per subsection. Since it's HTML fragment, I can use

  for subsections? The rules only mention

  for section headings. It doesn't forbid

  for subsections. But to keep it simple, I'll use

  for main sections and maybe or

  for subsections. The rules: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other headings. But to be safe, I'll use

  only for the main sections, and for subsections within Responsibilities, I'll use

  or just bold text with lists. I think using

  is fine for subsections. But the output should be a fragment, so I can use any HTML. I'll use

  for subsections under Responsibilities. Similarly for Qualifications: Minimum and Preferred. Now, let's write. I'll start with

  About the role

  then prose paragraphs. Then

  Responsibilities

  then for each subsection:

  IT Service Delivery & Employee Experience

  • ...

  etc. But the Key Responsibilities have bullet points with colons and sub-bullets. For example: - IT Service Delivery & Employee Experience：Service & Lifecycle: Direct support operations...; Service Portfolio & Metrics: Establish service tiers... I need to parse these into list items. Each main bullet is a category with sub-items. I'll make each category a list item with a strong label and then sub-list. Better: For each main category, create an

  and then a

  of the sub-items. Let's extract: Key Responsibilities: 1. IT Service Delivery & Employee Experience - Service & Lifecycle: Direct support operations, service desk intake, knowledge management, and escalations; coordinate employee onboarding, moves, and offboarding with HR and IAM. - Service Portfolio & Metrics: Establish service tiers, asset inventories, and SLAs; track response/resolution times and user satisfaction to drive engineering improvements. 2. Office Technology - Endpoint & Security Agents: Oversee endpoint management (MDM/UEM), OS lifecycle, and security agent deployment/health (EDR, vulnerability scanning) across the fleet. - Office Networking: Lead design, operation, and access control for office LAN/WAN and Wi-Fi; support new site buildouts and network changes with Workplace teams. - Converged Physical Security: Own the lifecycle, network integration, and health of access control badges, cameras, and VMS platforms in partnership with Physical Security. 3. IT Engineering (In-House VDI) - VDI Platform Ownership: Lead architecture, software development, and operations for the proprietary VDI platform (Kubernetes controllers, session brokers, desktop images, IAM integrations). - Performance & Delivery: Optimize launch times and streaming responsiveness; establish staged rollouts, rollback protocols, capacity planning, and front-line to engineering escalations. 4. Automation & Agentic AI - Reusable Automation: Build API-first workflows, backend services, and IaC/CI/CD pipelines for self-service, provisioning, and automated remediation. - Production Agentic AI: Deploy support assistants, retrieval, and diagnostic agents with strict RBAC, data boundaries, and human-in-the-loop controls for high-risk actions. - AI-Assisted Development: Integrate AI coding/investigation tools while maintaining engineering accountability for code quality, reviews, and releases. 5. Department Leadership & Strategy - Set strategy and investment priorities. Build the department and its leadership pipeline. Lead company-level, cross-functional delivery 6. Reliability, Security & Operational Governance - Own service health and resilience: Establish service-level objectives, monitoring, on-call and escalation arrangements, incident command for IT service outages, and tested continuity and recovery plans. Use post-incident reviews to eliminate recurring failures, reduce operational toil, and maintain sustainable support coverage. I'll structure each as

  and

  • for each sub-point. For Department Leadership & Strategy, it's a single paragraph with multiple sentences. I'll split into list items. Now Qualifications: Minimum Qualifications (7 bullet points) Preferred Qualifications (7 bullet points) I'll make two sections:

    Requirements

    for minimum,

    Qualifications

    for preferred. Benefits: from Job Information: "Employees have day one access to medical, dental, and vision insurance, a 401(k) savings plan with company match, paid parental leave, short-term and long-term disability coverage, life insurance, wellbeing benefits, among others. Employees also receive 10 paid holidays per year, 10 paid sick days per year and 17 days of Paid Personal Time (prorated upon hire with increasing accruals by tenure)." Pay: "The base salary range for this position in the selected city is $257400 - $616000 annually. Compensation may vary outside of this range depending on a number of factors, including a candidate’s qualifications, skills, competencies and experience, and location. Base pay is one part of the Total Package that is provided to compensate and recognize employees for their work, and this role may be eligible for additional discretionary bonuses/incentives, and restricted stock units." Schedule: "On-site presence across teams allows the company to operate with greater speed, alignment, and agility — especially in areas like real-time decision-making, team development, and integrated execution. As such, the company is shifting from a hybrid work model to a fully in-person schedule up to 5 days a week." About USDS TikTok: prose. Why Join Us: prose. Diversity & Inclusion: prose. USDS Reasonable Accommodation: prose with link. I'll include all as sections. Now, the rules: "Do NOT repeat the job title as a heading (the page already shows it)" - the job title is "Head of IT" presumably, but not in the text provided. The user didn't give a title, but the posting starts with "Responsibilities About the Team". So no title to repeat. "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." There's no Job ID in the text. "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Diversity & Inclusion and Reasonable Accommodation might be considered EEO boilerplate, but they're specific to USDS. I'll keep them. "Pres