Cloud Systems Engineer

We need to output HTML fragment with sections: headings

for sections present: About the role (maybe from intro), Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. We must only include sections if posting has real specific content. Let's parse. Intro: "We are seeking a Cloud Systems Engineer to support and operate large-scale AI and high-performance computing (HPC) environments. This role will be responsible for the deployment, maintenance, performance, and lifecycle management of GPU-accelerated compute infrastructure that powers critical AI, machine learning, and data-intensive workloads. The ideal candidate is a hands-on infrastructure professional with strong Linux administration skills, deep hardware troubleshooting experience, and expertise supporting enterprise-class compute platforms. This individual will work closely with infrastructure, networking, storage, and AI engineering teams to ensure the reliability, scalability, and operational excellence of our AI infrastructure." That's about the role. So we can have

About the role

with paragraph(s) containing that text. Responsibilities: there is a block titled "Responsibilities:" with bullet-like lines. We'll convert to

• each line. Requirements/Qualifications: there is "Experience Required Qualifications" then list of bullet-like lines. We'll treat as Requirements or Qualifications. Could combine into one section "Requirements". We'll include bullet list. Skills: The posting includes some skill items like Bash, Python, PowerShell, etc. They are within the qualifications list. Might be considered part of Requirements. Could create a Skills section if distinct. But we have to avoid thin sections. Probably better to keep qualifications as one section. Benefits: there is a "Company Benefits" paragraph describing benefits. So we include Benefits section. Pay: there is "Base Salary Range $100,000—$135,000 USD". So we include Pay section. Schedule: there is mention "Alarm.com values working together and collaborating in person. Our employees work from the office 4 days a week." That's schedule info. So we include Schedule section. We must not include boilerplate like EEO, legal, immigration note, etc. Also remove "Please note that sponsorship..." etc. Also remove "Company Info" maybe? It's not a required heading but could be considered About the company? Not requested headings. We should not include company info unless it fits under About the role? Probably not. We should drop it. Also drop "WHY WORK FOR ALARM.COM?" maybe could be considered Benefits? But we already have Benefits. Could incorporate some of that into Benefits? But the instruction: include section only when posting has real specific content for it. The "WHY WORK FOR ALARM.COM?" is basically benefits/culture. Could be part of Benefits. But we already have Benefits section with details. We could add more bullet points from that section. However we must preserve all substantive information; we cannot invent or summarize away detail. So we need to include that content somewhere. If we don't create a separate section, we could incorporate into Benefits as additional bullet points. That's allowed: we can have Benefits section with bullet list of benefits and also include those culture points? The instruction: Use
  • for any list of duties/requirements/benefits. So we can make Benefits section with bullet list of benefits and also include those culture points as list items. That would preserve info. Similarly, "Company Info" could be omitted? It's substantive about the company. Not requested heading; maybe we could incorporate into About the role? Not ideal. But we could add a short paragraph under About the role describing company? The About the role currently is about role. Could we add a paragraph about company? Might be considered extra but not heading. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we must include company info somewhere. Could add a paragraph after About the role before Responsibilities, maybe as a separate

    not under a heading. That's acceptable: we can have free-form paragraphs not under headings. The instruction only says use headings for sections; we can have paragraphs elsewhere. So we can add a

    about company info. Similarly, "WHY WORK FOR ALARM.COM?" could be a

    or incorporated into Benefits. Safer to make a separate section? But we have no heading for culture; we could add a section "Culture and Values" but not in allowed headings list. The allowed headings list includes specific ones; we should not create other headings. So we should embed that content either in Benefits or as a paragraph without heading. Probably best to add a paragraph after Benefits? But Benefits heading expects list of benefits; we could add a

    after the list describing culture. That's fine. Similarly, "Company Info" could be a paragraph after Benefits or before. We must not include boilerplate like EEO, legal, immigration note, etc. Also remove "Please note that sponsorship..." etc. Also remove "Notice To Third Party Agencies:" etc. Also remove "Alarm.com is an Equal Opportunity Employer" etc. Also remove the long personal info collection notice. Also remove "By submitting your application..." etc. Also remove "Notice To Third Party Agencies:" etc. Also remove "If you are interested in working with Alarm.com, please email your company information..." etc. Also remove "WHY WORK FOR ALARM.COM?" heading? We'll not use heading; we'll embed content. Now construct HTML. We'll start with

    About the role

    then

    containing the intro sentences. Then maybe a

    for company info: "Alarm.com is the leading platform for intelligently connected properties. Millions of homeowners and businesses rely on Alarm.com's technology to secure, monitor, and manage their environments from anywhere. Our comprehensive suite of solutions—including security, video surveillance, access control, active shooter detection, intelligent automation, energy management, and wellness—is delivered exclusively through a trusted network of thousands of professional service providers and commercial integrators across North America and worldwide. Alarm.com's common stock is traded on Nasdaq under the ticker symbol ALRM. Alarm.com delivers serious security for serious people." Then Responsibilities

    Responsibilities

    with
    • each line. List items from Responsibilities block: - Deploy, configure, and maintain GPU-accelerated compute infrastructure. - Manage operating system, firmware, BIOS, BMC, driver, and software lifecycle updates. - Monitor system health, performance, utilization, and capacity across AI infrastructure environments. - Support infrastructure utilized for AI model training, inference, and data processing workloads. - Develop and maintain operational standards, runbooks, and maintenance procedures. - Participate in on-call support and incident response activities. Then Linux Systems Administration is a subheading? Not in allowed headings but could be part of Responsibilities? Actually it's a separate category under Responsibilities? The original had "Responsibilities:" then bullet list, then "Linux Systems Administration" as a heading within responsibilities? It seems they grouped responsibilities into categories. We could treat each category as a subsection but we only allowed headings for sections like Responsibilities; we could keep the bullet list under Responsibilities and include all items, regardless of subheadings. So we need to include all bullet points from all subcategories: Linux Systems Administration, Hardware and Datacenter Operations, Other duties as assigned. Thus we need to extract all bullet points after each subheading. Let's list them: Linux Systems Administration: - Administer enterprise Linux environments, including Ubuntu and Red Hat-based distributions. - Perform system patching, hardening, and operating system lifecycle management. - Troubleshoot operating system, kernel, storage, networking, and application-level issues. - Develop automation to streamline deployment, monitoring, and operational processes. - Support security and compliance initiatives across AI infrastructure platforms. Hardware and Datacenter Operations: - Install, configure, maintain, and troubleshoot enterprise compute hardware. - Diagnose and resolve issues involving GPUs, CPUs, memory, storage, power, and networking components. - Perform firmware upgrades and hardware lifecycle management activities. - Coordinate hardware replacements, vendor support engagements, and warranty services. - Participate in rack-and-stack deployments, datacenter expansions, and technology refresh projects. - Maintain accurate asset inventories and operational documentation. - Support high-performance networking technologies, including Ethernet and InfiniBand environments. - Collaborate with networking, storage, cloud, and AI engineering teams on infrastructure design and operations. - Assist with scalability, resiliency, and performance optimization initiatives. - Perform root-cause analysis of infrastructure failures and develop preventative measures. Other duties as assigned: (just that phrase) maybe we can include as a bullet: "Other duties as assigned." Now Requirements/Qualifications block: "Experience Required Qualifications Bachelor’s degree required3-5 years of Linux systems administration experience in production environments.3-5 years of experience supporting enterprise server infrastructure.Experience supporting large-scale compute environments, HPC platforms, AI infrastructure, or GPU-enabled systems.Experience performing hardware diagnostics, firmware management, and lifecycle maintenance.Experience working within datacenter operations environments.Bash, Python, PowerShell, or similar scripting languagesOperating system performance tuning and monitoringStorage and networking fundamentalsExperience with infrastructure monitoring and observability platforms, ex Grafana.Hardware and firmware lifecycle management" We need to split into sensible bullet items. The text seems concatenated without spaces. We need to parse manually. Let's separate: - Bachelor’s degree required - 3-5 years of Linux systems administration experience in production environments. - 3-5 years of experience supporting enterprise server infrastructure. - Experience supporting large-scale compute environments, HPC platforms, AI infrastructure, or GPU-enabled systems. - Experience performing hardware diagnostics, firmware management, and lifecycle maintenance. - Experience working within datacenter operations environments. - Bash, Python, PowerShell, or similar scripting languages - Operating system performance tuning and monitoring - Storage and networking fundamentals - Experience with infrastructure monitoring and observability platforms, ex Grafana. - Hardware and firmware lifecycle management Note "Hardware and firmware lifecycle management" maybe duplicate of earlier but keep. Now Benefits section: we have paragraph under "Company Benefits Our total rewards package is designed to support you holistically—in your health, your finances, and your life outside of work. The package includes medical plans with company subsidies, a Health Savings Account (HSA) with a company contribution, and a 401(k) with an employer match. We encourage a healthy work-life balance with paid vacation that increases with tenure, paid holidays, wellness time, and paid maternity and bonding leave. To complete the package, we also provide company-paid disability and life insurance, all within a collaborative and casual work environment." We can turn that into bullet list: - Medical plans with company subsidies - Health Savings Account (HSA) with a company contribution - 401(k) with an employer match - Paid vacation that increases with tenure - Paid holidays - Wellness time - Paid maternity and bonding leave - Company-paid disability and life insurance - Collaborative and casual work environment Also we could add culture points from "WHY WORK FOR ALARM.COM?" as bullet points: - Collaborate with outstanding people: high standards, high achievers. - Make an immediate impact: real responsibility for bringing new technologies to marketplace. - Gain well-rounded experience: diverse and dynamic environment, work directly with executives, develop expertise across multiple areas. - Community and Camaraderie: core value 'Keep It Fun', fostering strong sense of community, collaboration and connection, celebrate successes, positive engaging environment. - Alarm.com values working together and collaborating in person. Employees work from the office 4 days a week. We could incorporate those into Benefits as additional bullet points, or we could add a separate paragraph after Benefits list. Since we already have Benefits heading, we can add a

      after the list describing culture. That preserves info. Pay section:

      Pay

      with

      Base Salary Range $100,000—$135,000 USD

      Schedule section:

      Schedule

      with

      Employees work from the office 4 days a week.

      (maybe also mention collaboration in