IT System Administrator

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, visa sponsorship, etc. Also remove application instructions. We need to preserve all substantive info. Let's parse content: TL;DR: Imubit is looking for a top-notch System Administrator to help support a growing global team of engineers who are disrupting the refining and chemical industries with breakthrough machine learning technologies. About us: paragraph about Imubit. We are looking for: description of candidate. In this position, you will: list of duties. Qualifications: bullet list. You have experience with: list. Nice to have: list. Imubit provides equal employment opportunities ... (remove) Imubit does not accept or retain unsolicited CVs ... (remove) No visa sponsorship is available for this position. (remove) We need sections: About the role (maybe combine TL;DR and About us?), Responsibilities (duties), Requirements (maybe qualifications?), Qualifications (maybe education?), Skills (experience with), Benefits (none mentioned), Pay (none), Schedule (none). So we will include only sections with content: About the role, Responsibilities, Requirements, Qualifications, Skills. But we need to decide mapping: The posting has "About us" which is about company, not role. Could be "About the role" includes TL;DR and maybe description of role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections accordingly. We need to decide what goes where. - About the role: could include TL;DR and maybe "We are looking for:" description? But that's more about candidate. However typical job posting: About the role describes the position. We have TL;DR and maybe "In this position, you will:" is responsibilities. So About the role could be the TL;DR plus maybe the "We are looking for:" paragraph? But that's more about candidate qualifications. Might be better to put TL;DR in About the role, and "We are looking for:" as part of Requirements or Qualifications? Actually "We are looking for: You, a resourceful, proactive, and hard-working system administrator with 7 years of technical expertise! ..." That's describing desired candidate traits. Could go under Requirements or Qualifications. Let's structure: About the role: TL;DR paragraph. Responsibilities: the list under "In this position, you will:" (the bullet list of duties). Requirements: maybe the "Qualifications:" bullet list (7+ years experience, degree plus, certifications, problem solving, etc.) That seems like requirements. Qualifications: maybe the "You have experience with:" list (specific technologies). That's qualifications/skills. Skills: maybe the "Nice to have:" list (security ops, additional scripting, AWS/GCP). Could be Skills or maybe we treat as Skills. But we have both Requirements and Qualifications sections; we need to avoid duplication. Could combine: Requirements = mandatory qualifications (7+ years, degree, certifications, problem solving, etc.) Qualifications = specific experience with tools (Okta, M365, etc.) Skills = nice to have. Alternatively, we could have Requirements = the "Qualifications:" bullet list, and Skills = the "You have experience with:" list, and maybe omit Qualifications section. But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we can decide which sections to include based on content. We have content for: - About the role (TL;DR) - Responsibilities (duties) - Requirements (the "Qualifications:" bullet list) - Skills (the "You have experience with:" list) maybe also "Nice to have:" could be part of Skills or separate but we could include as Skills (including nice to have). However we need to avoid filler. We also have "Nice to have:" which is additional desirable skills; could be part of Skills section as sublist. We have no explicit Benefits, Pay, Schedule. Thus output sections: About the role, Responsibilities, Requirements, Skills. We need to use

for each heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate removed. Let's extract substantive content: TL;DR: "Imubit is looking for a top-notch System Administrator to help support a growing global team of engineers who are disrupting the refining and chemical industries with breakthrough machine learning technologies." About us paragraph: multiple sentences. Should we include in About the role? The instruction says About the role heading; we could put TL;DR there, but maybe also include About us as part of About the role? The heading is About the role, not About the company. However the posting includes "About us:" which is company description. Could we treat that as About the role? Might be okay to include as part of About the role (since it's about the company context). But we must not invent headings; we can include About the role with both TL;DR and About us? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid adding extra prose inside that section. So we can put TL;DR and About us paragraphs inside About the role. Thus About the role section will contain two paragraphs: TL;DR and About us. Now Responsibilities: list of duties from "In this position, you will:" each line starts with a verb. We need to preserve all details. Let's extract each bullet: - Serve as the primary administrator for Okta SSO, including Okta Workflows scripting and automation - Manage user lifecycle (provisioning, deprovisioning, group policies, permissions) - Administer Microsoft 365, AzureAD, and Intune for patching, application deployment, and device compliance - Administer Kandji (Apple MDM) for macOS/iOS device management - Support and maintain both Windows and macOS endpoints - Manage Google Workspace (email, calendar, accounts, policies) - Administer Jira, Confluence, Atlassian tools, and Slack for user setup, troubleshooting, and configuration - Provide support for VPN access (Perm81) - Support Cloudflare DNS for customer/user-facing configurations - Provide administration and support within AWS and GCP environments - Write and maintain automation scripts (Okta Workflows, PowerShell, Python, Bash) to streamline IT operations - Manage IT hardware/software lifecycle: ordering, provisioning, shipping, and decommissioning devices - Work with vendors (Dell, Amazon, others) to procure laptops, parts, and accessories - Maintain IT inventory and lifecycle records - Proactively manage the IT service desk queue to ensure SLA targets are met or exceeded - Perform audits on system access, collaborating with compliance and security teams to ensure policy adherence - Assist with large IT projects, including deployment of new IT systems and services - Ensure internal customer satisfaction by maintaining clear, timely communication on open IT requests We need to keep them as

  • . Now Requirements: from "Qualifications:" bullet list: - 7+ years proven experience as a System Administrator or similar role - Bachelor's degree in computer science, information technology, or a related field is a plus - Relevant certifications (Okta, Microsoft, Apple, CompTIA, etc.) - Excellent problem-solving skills and attention to detail - Ability to work independently and prioritize tasks in a fast-paced environment - Effective communication and interpersonal skills Note: "Bachelor's degree ... is a plus" is not a strict requirement but still content. We'll keep. Now Skills: from "You have experience with:" list: - Okta SSO and Okta Workflows scripting/automation - Microsoft Intune, AzureAD, Microsoft 365, and Autopilot - Google Workspace administration - Kandji (Apple MDM) or similar Apple device management platforms - Jira, Confluence, Atlassian tools, and Slack administration - Cloudflare DNS management - Vendor procurement and lifecycle management (Dell, Amazon, etc.) - Windows and macOS workstation administration - Strong scripting skills (PowerShell, Python, Bash) Also "Nice to have:" list: - Security operations background (endpoint protection, compliance, access reviews) - Additional scripting or workflow automation expertise - AWS and GCP cloud environments We could combine these under Skills section, maybe separate subheadings? But we only allowed headings as listed; we could just put all under Skills, maybe separate lists for required experience and nice-to-have. But we must not invent headings beyond those. Could we include two
    lists under Skills, one for required experience and one for nice-to-have? We could add a

    preceding each list to differentiate. That's acceptable. Thus Skills section will contain:

    Required experience:

    ... list of required experience

    Nice to have:

    ... list of nice to have
    Now we must ensure we do not include any boilerplate: EEO, visa sponsorship, unsolicited CVs, etc. Remove. Now check for any duplicated lines: The posting had some repeated content? Not seeing duplicates besides maybe overlapping between responsibilities and experience lists. But we must preserve all substantive info; we can keep both even if similar. Now ensure we do not include any placeholder like "commensurate with experience" etc. Not present. Now output HTML fragment: start with

    About the role

    then paragraphs. We need to wrap paragraphs in

    . For lists,

    • . Let's craft. About the role: two paragraphs. First paragraph: TL;DR. Second paragraph: About us content (the long paragraph). We need to preserve all sentences exactly? We can copy as is, but ensure no extra formatting. About us text: "At Imubit, we’re not just optimizing industrial processes - we’re redefining how entire industries operate. As the pioneer of Closed Loop AI Optimization (AIO), we are leading the charge in transforming refining, chemical, cement, and mineral mining plants with AI-driven automation. Our Optimizing Brain™ Solution puts the power of AI directly into the hands of engineers, enabling them to build and deploy their own multipurpose models to unlock new levels of efficiency, profitability, and sustainability. Seven of the top ten U.S. refiners trust Imubit, with our solution deployed in over 90 high-value applications, delivering real-time process optimization that drives margins, reduces emissions, and builds the AI-savvy workforce of the future. Co-founded by a Google Fellow and award-winning data scientist, Imubit brings together domain experts from industry leaders like Exxon, Shell, Holcim, and FLSmidth. Backed by tier-1 venture capital firms such as Insight Partners and Alpha Wave, we are setting a new standard for industrial AI. Our mission is simple but bold: helping the world’s leading industrial companies solve their most complex challenges, maximize long-term profitability, and future-proof their operations in an era of rapid change." We need to keep punctuation exactly. Now Responsibilities heading:

      Responsibilities

      then
      with each duty. Now Requirements heading:

      Requirements

      then
      with each qualification. Now Skills heading:

      Skills

      then

      Required experience:

      then
      list, then

      Nice to have:

      then
      list. Check that we didn't miss any substantive info: The "We are looking for:" paragraph describing candidate traits: "You, a resourceful, proactive, and hard-working system administrator with 7 years of technical expertise! You strive to improve customer experience, optimize