Cloud Adminstrator

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. We need to parse the posting. First, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. We need to preserve all substantive info. Let's extract: - Intro paragraph: "PAR Systems is seeking a Microsoft Cloud Administrator to help operate, secure, and strengthen the Microsoft cloud environment supporting our defense and regulated business. This role will have a particular focus on our Azure Government GCC High environment, where Controlled Unclassified Information (CUI) is stored, processed, and transmitted across Microsoft 365 services including SharePoint, Teams, OneDrive, Exchange Online, and Intune. You’ll work alongside our Senior IS Infrastructure Engineer and partner closely with our Governance, Risk, and Compliance (GRC) team to keep this environment secure, reliable, and aligned with NIST SP 800-171 and CMMC requirements. While GRC provides governance and compliance oversight, you’ll be hands-on with the technology, configuring, maintaining, hardening, troubleshooting, and continuously improving the systems and technical controls that support our compliance objectives. Beyond GCC High, you’ll also provide key support for our commercial Microsoft cloud environment and serve as backup across broader IS infrastructure needs, giving you exposure to PAR’s larger technology environment." That's about the role. Then "Success Criteria" paragraph: "Your experience administering Microsoft 365 and Azure/Entra ID environments will help you hit the ground running as you become a trusted technical resource for PAR’s GCC High environment. You’ll build a strong understanding of the environment, its security requirements, and the technical controls needed to protect CUI while helping ensure critical systems are not dependent on a single administrator. Success in this role means keeping our Microsoft cloud environment secure and well maintained, not simply configuring controls once, but ensuring they continue to work as our systems and business evolve. You’ll manage areas such as identity and access, conditional access, endpoint management, security tooling, configuration baselines, logging, patching, and recurring access reviews. You’ll use your technical judgment to identify issues, troubleshoot problems, and strengthen the environment over time. You’ll also help turn technical operations into clear, defensible evidence of how our controls are working. In partnership with GRC, you’ll maintain configuration records, logs, screenshots, exports, and other technical artifacts needed to support our System Security Plan (SSP), assessments, remediation efforts, and ongoing CMMC readiness. When gaps are identified, you’ll help translate them into technical actions and work with internal partners and managed service providers to drive them toward resolution. As you grow into the role, you’ll become a fully cross-trained administrator for the GCC High environment who can independently manage day-to-day needs, support changes and migration activities, and provide knowledgeable backup across critical systems. You’ll also look for opportunities to make the environment easier to manage through stronger documentation, repeatable processes, and automation." That's responsibilities. Then "Required Qualifications" bullet list: - 3+ years administering Microsoft 365 and Azure/Entra ID in a production environment, including Intune, Exchange Online, SharePoint, and Teams. - Hands-on experience with identity and security tooling — conditional access, MFA, endpoint management, and Microsoft Defender / Purview. - Working knowledge of security-control frameworks (NIST SP 800-171, NIST 800-53, or CMMC) and how technical settings map to control requirements. - Demonstrated discipline with change control, configuration baselines, logging, and access reviews. - U.S. Person and eligibility to work in a GCC High / ITAR-aware environment Then "Preferred Qualifications": - Direct experience with Azure Government / GCC High or another sovereign cloud (distinct from commercial M365). - Supporting a DFARS 252.204-7012 / NIST SP 800-171 or CMMC program in a defense-contractor setting. - Relevant certifications such as Microsoft SC-300, AZ-500, MS-102, or Security+. - Scripting/automation (PowerShell, Graph API) for control enforcement and evidence collection. Then benefits: "You’ve learned about what you'll be doing, here are the benefits you'll gain when you join our team: Global team recognized for their passion of inventing First-of-a-kind product culture and project exposure Training and development from industry-leading experts Cutting edge benefit programs that include: 401(k) & matching; Medical, Dental, Vision Insurance; Disability & Life Insurance; PTO, Paid Holidays, & Parental Leave for both Parents; Tuition Reimbursement" Then pay: "We offer market competitive pay and benefits based upon the candidate’s skills, experience, qualifications, and internal equity. Our starting rate of pay for this salaried position is targeted at $110,000-130,000 annually." Schedule: Not mentioned. So we should not include Schedule section. We also need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We have "Required Qualifications" and "Preferred Qualifications". Could combine into Requirements and Qualifications? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content. - About the role: intro paragraph. - Responsibilities: Success Criteria paragraph (maybe also some responsibilities from earlier? but we can put that). - Requirements: Required Qualifications. - Qualifications: Preferred Qualifications? Or maybe Skills? The instruction includes both Requirements and Qualifications as separate headings. We could put Required Qualifications under Requirements, and Preferred Qualifications under Qualifications. Or we could put Required under Requirements, and Preferred under Qualifications. Skills maybe we could extract any specific skills like scripting/automation, etc. But we already have those in Preferred. Could also create Skills section for things like "identity and security tooling", "conditional access", etc. But we might avoid duplication. Better: Use Requirements for mandatory, Qualifications for preferred, Skills maybe for technical skills like scripting, PowerShell, etc. However we have limited distinct content. We could do: - About the role: intro. - Responsibilities: Success Criteria paragraph. - Requirements: Required Qualifications list. - Qualifications: Preferred Qualifications list. - Skills: maybe we can extract "Scripting/automation (PowerShell, Graph API)" etc. But that's already in Preferred. Could still list under Skills. But we must not create sections with filler. If we put Skills, we need real content. We could list skills like "Identity and access management, Conditional access, MFA, Endpoint management, Microsoft Defender/Purview, Configuration baselines, Logging, Patch management, Access reviews, Change control, Documentation, Automation, PowerShell, Graph API". Those are derived from the text. That's substantive. But we must not invent details not present. Those are present in the text: identity and security tooling (conditional access, MFA, endpoint management, Microsoft Defender/Purview); change control, configuration baselines, logging, access reviews; scripting/automation (PowerShell, Graph API). So we can list those as skills. Thus we can have Skills section with a bullet list. Benefits: we have benefits paragraph. Pay: we have pay range. Schedule: none, so omit. Now we need to format with

for each section heading. Use

• for any list of duties/requirements/benefits, and

  for prose. Thus:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ...

  We need to ensure we don't repeat job title as heading. Good. We need to remove boilerplate: EEO statements, AI note, accommodation request, equal opportunity employer, etc. Also remove "#AreaOfInterest:Information-Systems". Also remove "You’ve learned about what you'll be doing, here are the benefits you'll gain when you join our team:" maybe keep as intro to benefits but we can incorporate into Benefits section prose. We need to preserve all substantive information. Let's craft the content. About the role paragraph: combine the first paragraph maybe also include the sentence about working alongside Senior IS Infrastructure Engineer etc. Already there. Let's write: PAR Systems is seeking a Microsoft Cloud Administrator to help operate, secure, and strengthen the Microsoft cloud environment supporting our defense and regulated business. This role will have a particular focus on our Azure Government GCC High environment, where Controlled Unclassified Information (CUI) is stored, processed, and transmitted across Microsoft 365 services including SharePoint, Teams, OneDrive, Exchange Online, and Intune. You’ll work alongside our Senior IS Infrastructure Engineer and partner closely with our Governance, Risk, and Compliance (GRC) team to keep this environment secure, reliable, and aligned with NIST SP 800-171 and CMMC requirements. While GRC provides governance and compliance oversight, you’ll be hands-on with the technology, configuring, maintaining, hardening, troubleshooting, and continuously improving the systems and technical controls that support our compliance objectives. Beyond GCC High, you’ll also provide key support for our commercial Microsoft cloud environment and serve as backup across broader IS infrastructure needs, giving you exposure to PAR’s larger technology environment. That's good. Responsibilities: Use the Success Criteria paragraph. Your experience administering Microsoft 365 and Azure/Entra ID environments will help you hit the ground running as you become a trusted technical resource for PAR’s GCC High environment. You’ll build a strong understanding of the environment, its security requirements, and the technical controls needed to protect CUI while helping ensure critical systems are not dependent on a single administrator. Success in this role means keeping our Microsoft cloud environment secure and well maintained, not simply configuring controls once, but ensuring they continue to work as our systems and business evolve. You’ll manage areas such as identity and access, conditional access, endpoint management, security tooling, configuration baselines, logging, patching, and recurring access reviews. You’ll use your technical judgment to identify issues, troubleshoot problems, and strengthen the environment over time. You’ll also help turn technical operations into clear, defensible evidence of how our controls are working. In partnership with GRC, you’ll maintain configuration records, logs, screenshots, exports, and other technical artifacts needed to support our System Security Plan (SSP), assessments, remediation efforts, and ongoing CMMC readiness. When gaps are identified, you’ll help translate them into technical actions and work with internal partners and managed service providers to drive them toward resolution. As you grow into the role, you’ll become a fully cross-trained administrator for the GCC High environment who can independently manage day-to-day needs, support changes and migration activities, and provide knowledgeable backup across critical systems. You’ll also look for opportunities to make the environment easier to manage through stronger documentation, repeatable processes, and automation. That's responsibilities. Requirements: Required Qualifications list. - 3+ years administering Microsoft 365 and Azure/Entra ID in a production environment, including Intune, Exchange Online, SharePoint, and Teams. - Hands-on experience with identity and security tooling — conditional access, MFA, endpoint management, and Microsoft Defender / Purview. - Working knowledge of security-control frameworks (NIST SP 800-171, NIST 800-53, or CMMC) and how technical settings map to control requirements. - Demonstrated discipline with change control, configuration baselines, logging, and access reviews