IT Manager

We need to output HTML fragment with sections: About the role? Actually the posting includes "THE ROLE" heading. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. The posting includes: About Olipop (company description) - maybe we treat as "About the role"? Actually "About Olipop" is company overview, not role. The role description is under "THE ROLE". Could map to "About the role". We'll include that. Responsibilities: there is a big block under "Responsibilities" with subheadings: Leadership & Strategy, Systems & Operations, Security & Compliance, Project & Vendor Management, User Experience & Support. We need to output a

• list of duties. Should we preserve subheadings? Probably we can include them as part of list items or maybe we can keep subheadings as plain text within li? The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. So we need to convert the responsibilities into list items. Could keep subheadings as bold? Not allowed? We can just include them as part of li text. Requirements: there is a "Requirements" section with bullet-like sentences. We'll output as

    • . Qualifications: Not separate; maybe "Bonus Points" could be considered qualifications? But we have "Bonus Points" after Requirements. Could treat as "Qualifications" or "Skills". The instruction: Use headings for Qualifications, Skills, Benefits, Pay, Schedule. We have "Compensation" line: "$130,000 - $150,000 + Bonus". That's Pay. So we need a Pay section with that info. Also we have "How We Work", "What We Value", "What We’re Looking For", "Startup life at OLIPOP". Those could be considered Skills or Benefits? Not exactly. Benefits not explicitly listed. There's no explicit benefits section. So we should not create Benefits unless posting actually states them. There's no benefits like health insurance etc. So we omit Benefits. Schedule: Not mentioned. So omit. Skills: Could we extract skills from responsibilities? Might be too thin. Better to not create Skills unless explicit. The posting does not have a dedicated Skills section. So we omit. Qualifications: Could combine Requirements and Bonus Points as qualifications? The instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have Requirements heading. Qualifications could be separate if there is distinct qualifications content. The posting has "Requirements" and then "Bonus Points". Bonus Points could be considered qualifications. But we could treat Bonus Points as part of Requirements or as Qualifications. Since we have a Qualifications heading available, we could put Bonus Points there. However we must not create a heading with filler. Bonus Points has concrete items: Experience supporting audit readiness and compliance programs (SOX, SOC 2). Background managing or scaling small IT teams in high-growth environments. That's substantive. So we can make a Qualifications section with those two items. Thus sections: About the role (company overview + role intro), Responsibilities, Requirements, Qualifications, Pay. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, accommodation request, equal opportunity employer, submission of application materials, unsolicited materials, etc. Also remove "We are committed to providing reasonable accommodations..." etc. Also remove "We are proud to be an Equal Opportunity Employer..." etc. Also remove "Submission of Application Materials" etc. Also remove "Start up life at OLIPOP is equally fun and fast-paced..." maybe that's not boilerplate but could be considered part of culture; but it's not a specific section heading; we could keep as prose under About the role? Might be considered part of "How We Work" etc. But we have no heading for that. We could incorporate into About the role as prose. However we must not invent sections. We can just include that as a

      under About the role? But About the role currently is company overview and role intro. Could add a paragraph about culture. We need to preserve all substantive information: The company mission description (About Olipop) is substantive. The role description under THE ROLE is substantive. Responsibilities block is substantive. Requirements block is substantive. Bonus Points is substantive. Compensation line is substantive. Also "How We Work", "What We Value", "What We’re Looking For", "Startup life at OLIPOP" are substantive cultural info. We should preserve them somewhere. Since we don't have specific headings for them, we could incorporate them into About the role as additional paragraphs. Or we could create a section "Culture" but not allowed headings list; we could use

      without heading. The instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could add other headings if we want, but better to stick to allowed ones. We can just put the cultural info as

      under About the role or maybe as a separate

      without heading. The instruction says output ONLY the HTML fragment — no /. So we can have multiple

      sections and

      and

      . Thus structure:

      About the role

      Olipop mission description ... plus THE ROLE intro paragraph ... plus maybe culture paragraphs.

      Then

      Responsibilities

      • ... each duty.
      Then

      Requirements

      • ... each requirement.
      Then

      Qualifications

      • ... bonus points.
      Then

      Pay

      $130,000 - $150,000 + Bonus

      We must not include Benefits, Schedule, Skills. Now we need to extract the content precisely. Let's parse the posting. About Olipop paragraph(s): "About Olipop At OLIPOP, we’re on a mission to positively impact consumer health at scale. And we’re doing it through something simple: soda. But not just any soda, a new kind of soda: one that’s delicious, refreshing, and actually good for you. This mission is deeply personal for our CEO, Co-Founder, and Formulator, Ben Goodwin. Like many of us, Ben grew up consuming the Standard American Diet: lots of soda and processed foods that prioritized convenience over nutrition. But at 14, he took his health into his own hands. After making significant changes to his nutrition and exercise, he lost 50 pounds and saw a transformation in his energy, mood, and emotional clarity. Those changes sparked a deep curiosity about the connection between nutrition and health. Ben became a relentless student of the gut microbiome and the ways it supports overall wellness. The more he discovered, the more passionate he became about finding credible, science-backed ways to make consumer health accessible to everyone. The mission was clear. The vehicle? Less so. After exploring the possibilities, Ben landed on an unexpected yet familiar choice: soda. It was something he loved as a kid, and he knew millions shared that same nostalgia. But this wouldn’t be just any soda. With most Americans falling short on daily fiber, Ben set out to create a version with more fiber and less sugar, one that was perfectly balanced. The result? A deliciously refreshing soda with 6 to 9 grams of fiber and 2 to 5 grams of sugar, delivering science-backed benefits without sacrificing the classic taste people crave. In 2018, the first OLIPOP cans hit the shelves, bringing Ben’s vision to life with a functional soda that anyone could enjoy. And by reimagining soda, we’re also reshaping culture. That means creating products that support health for all and building a business grounded in humanistic values: empathy, integrity, and a belief in better for everyone. From the ingredients we source to the culture we foster, we’re committed to proving that business (and beverage!) can be a force for good, and that soda has the power to bring people together. So join us, and let’s write a new American soda story together. One we can all feel good about. One OLIPOP at a time." Then "THE ROLE OLIPOP is looking for an IT Manager who's passionate about empowering teams through technology and ensuring our systems are secure, scalable, and easy to use. This role is both strategic and hands-on, leading key IT initiatives while diving deep into tools like Microsoft 365, Zscaler, Okta, Arctic Wolf, and Abnormal. You'll drive IT policy, governance, and vendor management while helping shape how technology supports OLIPOP's next stage of growth." That is the role intro. Then Responsibilities section with subheadings: Leadership & Strategy - Partner with the IT Director and company leadership to define and execute OLIPOP's IT strategy, roadmap, and annual priorities. - Establish, document, and enforce IT policies, standards, and best practices across the organization. - Own IT vendor management from sourcing to contract negotiation, renewals, and ongoing performance. - Manage IT budget planning, spend optimization, and technology ROI reporting. Systems & Operations - Oversee daily IT operations across cloud platforms, networking, endpoint management, and security infrastructure. - Manage upgrades, new deployments, and migrations ensuring minimal disruption and clear communication across teams. - Drive SaaS lifecycle management: onboarding, access control, renewals, and integrations. - Partner with internal teams and external vendors to ensure uptime, system performance, and timely resolution of issues. Security & Compliance - Lead information security initiatives, including SSO/MFA, identity governance, and zero-trust architecture through Okta and Zscaler. - Maintain and continually improve endpoint protection, threat detection, and email security using tools like Arctic Wolf and Abnormal. - Conduct regular IT risk assessments, user-access reviews, and incident-response exercises. - Ensure audit readiness for ITGC, SOC 2, and SOX-related controls, and support compliance with company security policies. Project & Vendor Management - Lead cross-functional IT projects including migrations, implementations, and automation initiatives from scoping through delivery. - Build and maintain strong relationships with SaaS providers and technology partners. - Deliver clear project documentation, timelines, and stakeholder communication. User Experience & Support - Provide hands-on support and mentorship to IT staff and end-users, ensuring smooth day-to-day operations. - Oversee the IT helpdesk, establishing SLAs, processes, and escalation paths. - Oversee the employee onboarding and offboarding process, ensuring proper provisioning, deprovisioning, and access governance. - Design and deliver internal training and self-service resources to promote productivity and security awareness. - Support the rollout and adoption of new security tools and endpoint-management platforms. - Continuously assess and enhance IT service delivery through automation, monitoring, and user feedback loops. Then Requirements: "Requirements 8+ years of progressive experience managing IT operations in a cloud-first, SaaS-heavy environment. Strong working knowledge of Microsoft 365, Zscaler, Okta, Arctic Wolf, Abnormal, and related modern IT and security tools. Proven experience leading cross-functional IT projects and vendor management from negotiation through delivery. Strong understanding of