Platform Administrator — M365/Azure

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes a description about company and mission. Could treat that as "About the role" or maybe "About the company". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. The posting includes Position Summary, Key Duties & Responsibilities, Qualifications (Education & Experience, Core Skills, Computer Skills, Preferred Certifications, Core Competencies), Work Environment, Requirements (export control etc), Physical Requirements, Equipment and Machines, EEO statement (to remove). Also there is a mission description at top. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we drop the EEO paragraph at end. Also drop "For more information about Axiom Space, visit www.axiomspace.com." maybe not needed but it's not boilerplate? It's informational but could be considered part of About the company. Might keep as part of About the role? Probably we can include a brief About the role paragraph summarizing mission. We need to preserve all substantive information. So we need to include details: Position Summary paragraph, Key Duties & Responsibilities list items, Qualifications sections (Education & Experience, Core Skills, Computer Skills, Preferred Certifications, Core Competencies). Also Work Environment, Requirements (export control etc), Physical Requirements, Equipment and Machines. We should not repeat job title as heading. The page already shows it, so we don't add heading for Platform Engineer II. We need to use

for section headings. Use

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

  for prose. We need to decide which sections to include: About the role (maybe from mission description), Responsibilities (Key Duties & Responsibilities), Qualifications (maybe combine Education & Experience, Core Skills, Computer Skills, Preferred Certifications, Core Competencies). Could also have separate sections: Education & Experience, Core Skills, Computer Skills, Preferred Certifications, Core Competencies. But instruction: prefer a few substantive sections over many thin ones. So we could combine Qualifications into one section with subheadings? But we only allowed h3 for section headings; we could still have multiple h3 sections. However "prefer a few substantive sections over many thin ones" suggests we should not create many sections with little content. But we have a lot of content; we could have sections: About the role, Responsibilities, Qualifications, Work Environment, Requirements (export control), Physical Requirements & Equipment. Could combine Physical Requirements and Equipment into one section maybe "Work Details". But better to keep separate if they have content. We need to avoid filler like "commensurate with experience". Not present. We must not include Pay/Schedule/Benefits unless posting states them. Not present, so omit those sections. Now craft HTML. We'll start with

  About the role

  then

  containing mission description and position summary. Mission description: "Axiom Space is a human space exploration company, building era-defining space infrastructure and delivering technology-driven solutions that will empower civilization to transcend Earth. Beginning with Axiom Station, successor to the International Space Station, the company is pioneering a next-generation orbital settlement that will foster groundbreaking innovation and research in microgravity and drive the global space economy of tomorrow. Today, guided by the vision of leading humanity's expansion off planet, Axiom Space is the principal provider of commercial human spaceflight services and developer of advanced spacesuits for the Moon and beyond." Then maybe also "Our mission-driven team is seeking a bold and dynamic Platform Engineer II (M365/Azure Administrator) who is fueled by high accountability, execution horsepower, and driven to understand our world, science/technology, and life itself, for the benefit of all on Earth and beyond." That's part of position summary but we can include. Then Position Summary paragraph: "Since Axiom Space is a very complex work environment, we are looking for a resilient, high-energy Platform Administrator II (M365/Azure Administrator), who designs, builds, and operates the Microsoft 365 tenant and Azure infrastructure that Axiom's engineering and business teams run on. This person drives automation, identity governance, and platform reliability practices that let internal teams work faster and more safely, while maintaining working familiarity with AWS to support occasional cross-platform workloads. This role serves as an escalation point for platform architecture and technical issues beyond the scope of entry-level engineers, and contributes to the continuous improvement of Axiom's enterprise cyber security program under the direction of senior IT leadership." We can combine. Now Responsibilities: list each duty as

• . Need to preserve all duties. Let's extract list from "Key Duties & Responsibilities". They are sentences each starting with a verb. We'll make each a list item. List: - Administers and evolves Axiom's Microsoft 365 tenant (including SharePoint Online and OneDrive for Business) and Azure environment — identity, networking, and compute — as a primary, day-to-day platform - Administers SharePoint Online (site collections, permissions, information architecture, retention/records policies) and OneDrive for Business (provisioning, sync client management, sharing controls, data loss prevention) - Serves as the primary escalation point for Microsoft 365 and Azure platform architecture, systems design, and technical issues beyond the scope of entry-level engineers - Manages identity and access management across Entra ID and AWS IAM — including Active Directory, app registrations, enterprise applications, and SSO/SAML/SCIM integrations — ensuring least-privilege access - Builds and maintains container and orchestration platforms (Docker, Kubernetes/AKS) to support internal application workloads - Administers end-user device management (Intune, Jamf, or equivalent) and on-premises VMware virtualization (vSphere/ESXi/vCenter) as part of a broader hybrid IT environment - Implements monitoring, logging, and observability (e.g., Azure Monitor) to track platform health, and reviews incidents and performance data to determine root cause and drive remediation - Preserves platform assets by implementing disaster recovery and backup automation, and develops, maintains, and tests business continuity plans across the Microsoft 365, Azure, and VMware environment - Builds Power Automate flows, low-code applications, and Power BI dashboards to support business process automation and reporting - Recommends platform engineering strategies, tooling, and standards by evaluating organizational outcomes, identifying problems, and anticipating requirements - Maintains basic working familiarity with AWS to support occasional cross-platform workloads - Communicating project progress, status, and potential issues to stakeholders and leadership - Implementing and maintaining agile project management methodologies throughout the project lifecycle - Perform additional job duties as assigned Note some have gerund vs verb; we keep as is. Now Qualifications: we have Education & Experience, Core Skills, Computer Skills, Preferred Certifications, Core Competencies. Could combine into one Qualifications section with subheadings? But we only allowed h3 for section headings; we could still have multiple h3 subsections under Qualifications? Might be okay but risk many thin sections. However each subsection has substantive content. Could we combine Education & Experience and Core Skills into one? Might lose detail. Better to keep separate sections: Education & Experience, Core Skills, Computer Skills, Preferred Certifications, Core Competencies. That's 5 sections; maybe okay. But instruction: "Prefer a few substantive sections over many thin ones." Could combine Core Skills and Computer Skills into a single "Skills" section? But they differentiate. However we could have a single "Qualifications" section containing paragraphs for each subtopic, using

  for prose and maybe

  • for lists. That would be one section with multiple paragraphs/lists. That seems better: one Qualifications section with subcontent. Thus:

    Qualifications

    then

    Education & Experience: ...

    then
    • for bullet points? Actually Education & Experience is a paragraph with bullet-like items? It says: "The majority of that experience should be spent administering Microsoft 365 and/or Azure in a production environment Bachelor's degree in Computer Science, 7+ years of experience, or an equivalent combination of education and experience Track record of making things happen in ambiguous, fast-moving environments Uses good judgement to problem-solve proactively, positively impacting hard challenges Demonstrated organization skills to meet tight deadlines with high-quality results". Could format as
      • each line. Then Core Skills: list bullet points: Passion for space and the mission; Entrepreneurial, growth mindset; High EQ and ability to collaborate within teams and cross-functionally; Tech-solutioning in using systems and tools to move smarter and faster. Computer Skills: list bullet points: Strong Microsoft 365 administration (services and licensing) as a core, day-to-day platform — deep, hands-on expertise expected; Strong SharePoint Online administration: site collections, permissions, information architecture, and governance/retention policies; Strong OneDrive for Business administration: provisioning, sync client management, sharing controls, and data loss prevention; Strong Azure Cloud administration (compute, networking, storage, governance) to support Azure-hosted workloads; Active Directory permissions and Entra ID administration, including app registrations and enterprise apps, with strong SAML and SCIM experience; CI/CD pipeline experience (Azure DevOps or GitHub Actions) and scripting proficiency in PowerShell or Python; Working knowledge of AWS administration (IAM, VPC networking, EC2/compute, S3) sufficient to support occasional AWS-hosted workloads; Containers and orchestration (Docker, Kubernetes/AKS, or equivalent); familiarity with end-user device management (Intune, Jamf, or equivalent); Strong virtualization experience with VMware (vSphere, ESXi, vCenter) administering and maintaining on-premises hybrid infrastructure; General IT security and firewall management, backup administration, wired/wireless networking, DHCP, and DNS; Experience with Power Automate flows, low-code application development, Power BI dashboards and Ansible Automation as a plus. Preferred Certifications: list bullet points: Microsoft Certified: Azure Administrator Associate (AZ-104); Microsoft Certified: Identity and Access Administrator Associate (SC-300); Microsoft Certified: Microsoft 365 Certified Administrator Expert (MS-102); Microsoft Certified: Teamwork Administrator Associate (MS-700) — SharePoint, OneDrive, and Teams administration; Microsoft Certified: Azure Solutions Architect Expert (AZ-305); VMware Certified Professional (VCP-DCV). Core Competencies: list bullet points: Accountability; Technical Rigor; Execution Discipline; Pride of Delivery. Now Work Environment: paragraph: "Generally, an office environment, but can involve inside or outside work depending on the task." Requirements: paragraph about export control: "This position may require access to export controlled technical data or technology subject to NASA regulations, International Traffic in Arms Regulations (ITAR), or Export Administration Regulations (EAR). In accordance with U.S. export control laws, final candidates may be required to undergo additional export control screening to determine eligibility for access. Meeting these requirements is a condition of employment Management has the prerogative to select at any level for which the position is advertised Must be willing to work evenings and weekends as needed to meet critical project milestones". Could split into two paragraphs. Physical Requirements: paragraph: "Work may involve sitting or standing for extended periods (90% of the time) May require lifting and carrying up to 25 lbs. (5% of the time)". Could combine. Equipment and Machines: paragraph: "Standard office equipment (PC, phone, printer, etc.)". We should remove duplicated lines: there is duplicate of "Administers and evolves Axiom's Microsoft 365 tenant (including SharePoint Online and OneDrive for Business) and Azure environment — identity, networking, and compute — as a primary, day-to-day platform"