IT Systems Administrator

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. We have a lot of prose describing role, responsibilities, qualifications, etc. We need to extract sections. We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. The posting includes sections like "Department: Technology Keep The Mission Running..." but we can ignore department line? It's not a heading; we can include as paragraph maybe. We need to preserve all substantive information. So we need to include content about role, responsibilities, qualifications, benefits, etc. We need to decide sections: Likely "About the role" (intro paragraph), "Responsibilities" (list of duties), "Qualifications & Requirements" (maybe combine qualifications and requirements), "Skills" (talents & abilities), "Benefits" (salary & benefits), maybe "Pay" if salary specified (not given exact salary, just benefits). There's no explicit pay amount, so we should not create Pay section. Schedule? Not specified. So we omit Pay and Schedule. We need to include Benefits section because they list PTO, medical insurance, life insurance, dental/vision, 401K, weekly payday, quarterly profit sharing. That's specific. We need to include maybe "Work Environment" but not a standard heading; we could incorporate into About the role or maybe a separate section like "Work Environment". But the instruction says use headings for those specific list; we can add other headings if needed? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but we should prefer those. Probably we should stick to those categories. So we can put work environment description inside About the role or Responsibilities. We need to output only HTML fragment, no /, no markdown. We need to use

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

  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, but we can format them. We need to be careful not to omit any detail. That's a lot. We need to capture all responsibilities listed under categories: IT Support (internal support, onboarding/offboarding, network monitoring, client support, audio/video systems, help desk documentation), Cloud & Infrastructure Operations (cloud admin, on-prem admin, identity and access management, endpoint and device management, network and connectivity, SaaS administration, monitoring and uptime), Backup, Business Continuity & Disaster Recovery (maintain backup program, test BC/DR plans, engineer for resilience, write runbooks), Service, Partnership & Development (provide senior-level support, partner across business, support vendors and spend, teach and grow). Also the intro paragraphs about mission, builder role, etc. Qualifications & Requirements: values, attitude, education, certifications preferred, experience, performance, talents & abilities (list many). Also "Our Every-Day SERVICE Values" maybe could be included under Qualifications or as a separate section? Could be part of About the role. We need to include all that. We must not include boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Equal Opportunity Mission Mobile Medical is an Equal Opportunity Employer..." and "About Mission Mobile Medical" etc. Those are likely boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO statement and the "About Mission Mobile Medical" paragraph? That seems like substantive info about company, but maybe it's considered boilerplate? It's describing the company mission; could be considered part of About the role? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The "About Mission Mobile Medical" is not EEO; it's company description. Might be okay to keep. However, the instruction also says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the company description unless it's considered boilerplate. It's not navigation/legal/EEO etc. So we keep. But we also need to remove duplicated lines. There may be duplicated lines like "Mission Mobile Medical is a forward-thinking..." appears later. We'll need to deduplicate. We need to output only HTML fragment. Let's craft sections:

  About the role

  ... intro paragraphs about mission, builder role, etc.

  Responsibilities

  • ... each duty as list items. Could group by categories but still list items.

  Qualifications & Requirements

  ... values, attitude, education, certifications, experience, performance.

  Skills

  • ... talents & abilities list.

  Benefits

  • ... benefits list.
  We might also include a

  for work environment inside About the role. We need to ensure we don't create empty sections. Now we need to extract the exact text from posting, preserving all details. This is tedious but we can approximate. Let's copy the relevant parts. Intro: "Department: Technology Keep The Mission Running One System At a Time. Imagine Being The Person Every Team Trusts When Something Absolutely Has To Work. At Mission Mobile Medical, Our IT Systems Administrators Don’t Just Keep The Lights On, They Own The Cloud Platform, The Identities, The Devices, The Network, The Backups, And The Security Controls That Protect Our People, Our Partners, And The Information They Trust Us With. We’re Looking For Someone Who Wants To Build systems that just work, and fix them fast on the rare day they don’t Take infrastructure, security, and uptime to the next level, not just maintain it Treat reliability as a service to the mission of one billion patient visits by 2040 Find your way into a role where your builder’s instinct actually gets to build. This is a hands-on builder’s role for someone who documents what they build and automates what they repeat. Reports to the Senior Director of Technology." Note there are some missing spaces and punctuation; we should preserve as is? Probably we should keep the text but maybe fix obvious typos? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Changing punctuation could be considered altering detail? Safer to keep as is, but we can add spaces for readability? Might be considered altering. I'd keep original but maybe add spaces where missing to make sense? The original text: "Take infrastructure, security, and uptime to the next level, not just maintain it Treat reliability as a service to the mission of one billion patient visits by 2040" missing space after "it". We could keep as is; it's still substantive. I'll keep exactly as given. Then "General As an IT Systems Administrator, you will own the following categories:" Actually there is "General" maybe a heading? We'll incorporate. Then list categories. Let's extract each bullet. IT Support: - Internal support. Provide internal IT support and resolve issues and requests in person and remotely. - Onboarding and offboarding. Manage end-user onboarding and offboarding processes. - Network monitoring. Perform basic network monitoring and troubleshooting. - Client support. Provide external IT support for our clients. - Audio/video systems. Set up, configure, and maintain corporate audio-video equipment, rooms, and events. - Help desk documentation. Create and maintain the documentation associated with the technology help desk. Cloud & Infrastructure Operations: - Cloud administration. Administer and maintain MMM’s cloud web apps, SQL databases, compute, network, and storage resources; own configuration, capacity, cost hygiene, and lifecycle of those resources. - On-premises administration. Administer and maintain MMM’s local, on-premises server environment. - Identity and access management. Administer Microsoft 365 and Entra ID; manage SSO, multifactor authentication, and conditional access; execute user and guest on-boarding and off-boarding; enforce least-privilege access and conduct periodic access reviews. - Endpoint and device management. Own device management and deployment (Intune/Autopilot), hardware standards, imaging, patch cadence, and endpoint protection across corporate laptops and shared devices. - Network and connectivity. Administer and monitor corporate network, wireless, firewall, and VPN; support field and mobile clinic connectivity (cellular, satellite, routers, NVR) alongside the client service and healthcare operation teams. - SaaS administration. Administer the SaaS solutions in the MMM stack. Keep integrations, permissions, and configurations clean and documented. - Monitoring and uptime. Build and maintain proactive monitoring and alerting; drive system uptime to 98% or better and resolve issues before users feel them. Backup, Business Continuity & Disaster Recovery: - Maintain the backup program. Configure, monitor, and verify backups across cloud, SaaS, and on-premises systems; prove recoverability with scheduled, documented test restores rather than assuming it. - Test BC/DR plans. Document and exercise business continuity and disaster recovery plans; define and defend recovery time and recovery point objectives for critical systems. - Engineer for resilience. Design redundancy, failover, and dependency awareness into infrastructure so a single failure never stops the business. - Write the runbooks. Maintain clear recovery runbooks that another team member could execute under pressure without you in the room. Service, Partnership & Development: - Provide senior-level support. Serve as escalation for complex system, network, and application issues; see long-running issues through to the finish line. - Partner across the business. Work directly with Manufacturing, Engineering, Mobile Health Operations, Program Development, Finance, BD, HR, and Regulatory to understand what support they need from the Technology team. - Support vendors and spend. Support vendor selection, renewals, and quarterly business reviews with technical evaluation and honest data on what a platform is actually delivering. - Teach and grow. Share knowledge through documentation, training, and security awareness content; grow toward the next level of technology leadership as MMM scales. Then Qualifications & Requirements section: "Values: Value all people and have a desire to be a Servant Leader. Attitude: Embrace our culture and our SERVICE values. Education: Bachelor’s degree in Information Technology, Computer Science, or a related field, or equivalent professional experience. Relevant certifications (Microsoft Azure/365 Administrator, Security+, CCNA, or similar) preferred. Experience: 3+ years of progressive information technology experience, including at least 1 year in a systems, cloud, or infrastructure administration role. Hands-on experience with Microsoft 365 and Azure, identity and access management, endpoint management, backup and disaster recovery, network administration, and security operations. Performance: Able and willing to provide world-class service to all stakeholders." Then "Talents & Abilities" list: "Demonstrated strong communication, organization, problem-solving, and teamwork skills Deep hands-on skill administering Microsoft 365 and Azure (Entra ID, Intune, Exchange, SharePoint, Defender) Strong working knowledge of networking — routing, switching, wireless, firewall, VPN — and remote connectivity including cellular and satellite Experience administering backup platforms and executing documented restore and disaster recovery tests Security operations experience: hardening, vulnerability remediation, alert triage, and compliance frameworks (HIPAA preferred) Scripting and automation ability (PowerShell preferred) with a habit of automating repetitive work Strong documentation discipline — able to write SOPs and runbooks that someone else can follow Comfort with data, reporting, and dashboards; able to turn system telemetry into a scoreboard Healthcare technology, medical device/IoT, or manufacturing environment experience preferred Proficiency in Microsoft Office