Linux Engineer

We need to output only HTML fragment, using

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove sections like "About Moderna", "Equal Opportunities", "Accommodations", "Export Control Notice". Also remove "Here’s What You Will Do" etc but we need to capture content under appropriate headings. We need to map content: - About the role: The initial paragraph describing role: "The Role Moderna is expanding our footprint...". That's description of role. Could be "About the role". We'll put that as

About the role

then

with that paragraph. - Responsibilities: The list under "Here’s What You Will Do". That's a series of bullet points (actually sentences separated by periods). We need to convert to

• . Must preserve all details. Let's extract each bullet: "Serve as a technical owner for enterprise Linux systems (Amazon Linux, Ubuntu, RHEL) across on-premises and cloud environments (VMware, AWS, Azure)." "Design, install, configure, and maintain Linux systems supporting research and production operations." "Conduct root cause analysis and advanced troubleshooting for system, network, and authentication issues." "Ensure high availability, scalability, and performance through configuration management and proactive monitoring" "Automate infrastructure operations using shell scripting, Ansible, Python, Terraform, or other IaC tools" "Integrate Linux systems with Active Directory (realmd, sssd, winbind); configure Kerberos, LDAP, NSS, and PAM; manage SPNs, keytabs, and TLS/SSL certificates." "Support containerized environments leveraging Docker, Podman, and Kubernetes." "Implement and maintain storage solutions (LVM, iSCSI, NFS) with a focus on performance and resilience." "Partner with cybersecurity teams to ensure compliance with Moderna’s security and incident response software suite." "Contribute to monitoring and observability efforts using tools such as Prometheus, Dynatrace, or Splunk." "Develop server and application implementation plans, custom scripts, and testing procedures to ensure operational reliability." "Maintain accurate documentation, diagrams, and system inventories." "Participate in on-call rotation and respond to escalated support incidents." We'll put each as
• . - Requirements: The "Here’s What You’ll Need (Basic Qualifications)" section. That's a list of qualifications. We'll treat as Requirements heading. Items: "Bachelor’s degree in computer science, engineering, or related field (or equivalent experience)." "3–5 years of professional experience supporting Linux in a mixed OS environment" "Strong understanding of multiple Linux distros including all core services/daemons" "Proven ability to troubleshoot system, network, and performance issues." "Experience with patch management process and tooling, endpoint protection, compliance and server hardening." "Familiarity with hybrid multi-cloud environments and virtualization technologies." "Excellent communication, documentation, and collaboration skills, including working across global teams." We'll put as
  • . - Qualifications: The "Here’s What You’ll Bring to the Table (Preferred Qualifications)" section. That's preferred qualifications. We'll treat as Qualifications heading. Items: "Linux certifications such as RHCSA/RHCE, LFCS/LFCE, or LPIC." "Industry certifications: AWS, CISSP, CISM, ITIL." "Experience in regulated or security-sensitive environments (e.g., GxP, DISA-STIG, CIS, PCI)." "Ability to work independently, develop long term strategic Infrastructure enterprise goals." We'll put as
    • . - Skills: Not explicitly separate; but we could combine some skill mentions from responsibilities and qualifications. However we should only create a Skills section if posting has real specific content for it. There's no dedicated "Skills" heading, but we could infer skills from responsibilities and qualifications. However the instruction: "Prefer a few substantive sections over many thin ones." We could omit Skills if not explicitly present. But we have many skill-like items; but we already have Requirements and Qualifications covering them. Might be okay to omit Skills. - Benefits: The posting includes "Pay & Benefits" section with description of benefits and salary range. So we need Benefits heading (maybe separate from Pay). The instruction: Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Benefits and Pay separate. The posting has "Pay & Benefits" with paragraph about benefits and then salary range. We'll split: Benefits heading with description of benefits (competitive healthcare, voluntary benefit programs, holistic well-being, family planning, generous PTO, savings/investments, location-specific perks). Pay heading with salary range and bonus info. - Schedule: Not mentioned; no info about schedule (e.g., full-time, shift). So we should not create Schedule section. - Also we need to include any other sections like "About Moderna"? That's boilerplate about company; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Moderna" is not exactly legal boilerplate but it's company description; could be considered part of job posting but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The "About Moderna" paragraph is substantive info about company. Should we keep? It's not a standard heading but could be placed under "About the role"? Actually "About the role" is about the role, not company. The instruction says we can use headings like About the role, Responsibilities, etc. It didn't list "About the company". So we might omit that section because not requested heading. However we must preserve ALL substantive information; if we omit it, we lose info. But maybe we can incorporate it into "About the role" paragraph? The instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says "Use

      for section headings (e.g. ...)". It implies we should use those headings for sections; we could also add other headings if needed, but better to stick to those. The "About Moderna" is company overview, not role. Could be considered part of "About the role"? Might be okay to include under "About the role" as extra paragraph. But the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

      or drop it." It doesn't forbid other headings. However to be safe, we could include a section "About Moderna" as

      About Moderna

      but that's not in the list; but the list is just examples. It says "e.g." meaning for example. So we could add other headings if needed. But the instruction also says "Prefer a few substantive sections over many thin ones." Adding another section may be okay. But we need to decide: The "About Moderna" paragraph is substantive; we should preserve it. We could put it under a heading "About Moderna". However the instruction about headings list includes "About the role" not "About the company". I'd lean to include it as a separate section, but maybe better to incorporate into "About the role" as extra paragraph, because it's still about the role context. However the role description already includes a paragraph about Moderna's mission; the "About Moderna" is more generic company info. Might be okay to keep as separate. Let's see if any other sections like "Equal Opportunities", "Accommodations", "Export Control Notice" are legal boilerplate; we should remove those. Thus final HTML will have sections:

      About the role

      ... (the initial paragraph)

      Responsibilities

      ...

      Requirements

      ...

      Qualifications

      ...

      Benefits

      ... (benefits description)

      Pay

      ... (salary range and bonus info)

      We should not include Schedule. Now we need to ensure we preserve all substantive info from the posting. Let's extract the exact text for each piece. First, the initial paragraph: "The Role Moderna is expanding our footprint to deliver the greatest possible impact to people through mRNA medicines. Our technology hub server team is responsible for the design, implementation, administration, and support of the server environments supporting our research and pharmaceutical production. This role requires deep expertise in engineering and supporting a multi-distro enterprise Linux environment. The ideal candidate is a hands-on technical expert who excels in troubleshooting, automation, and system optimization to ensure stability, scalability, and security across enterprise systems. We are seeking experienced engineers who embody the Moderna Mindsets and want to help transform patients’ lives by building reliable, secure, and scalable systems." We need to keep that exactly. Note there is a stray "The Role" at start maybe part of heading; but we keep as is. Now responsibilities bullets: We need to ensure we keep each sentence exactly as in posting. Let's copy them: - Serve as a technical owner for enterprise Linux systems (Amazon Linux, Ubuntu, RHEL) across on-premises and cloud environments (VMware, AWS, Azure). - Design, install, configure, and maintain Linux systems supporting research and production operations. - Conduct root cause analysis and advanced troubleshooting for system, network, and authentication issues. - Ensure high availability, scalability, and performance through configuration management and proactive monitoring - Automate infrastructure operations using shell scripting, Ansible, Python, Terraform, or other IaC tools - Integrate Linux systems with Active Directory (realmd, sssd, winbind); configure Kerberos, LDAP, NSS, and PAM; manage SPNs, keytabs, and TLS/SSL certificates. - Support containerized environments leveraging Docker, Podman, and Kubernetes. - Implement and maintain storage solutions (LVM, iSCSI, NFS) with a focus on performance and resilience. - Partner with cybersecurity teams to ensure compliance with Moderna’s security and incident response software suite. - Contribute to monitoring and observability efforts using tools such as Prometheus, Dynatrace, or Splunk. - Develop server and application implementation plans, custom scripts, and testing procedures to ensure operational reliability. - Maintain accurate documentation, diagrams, and system inventories. - Participate in on-call rotation and respond to escalated support incidents. Note some lines missing period at end; we keep as is. Now Requirements (Basic Qualifications) bullets: - Bachelor’s degree in computer science, engineering, or related field (or equivalent experience). - 3–5 years of professional experience supporting Linux in a mixed OS environment - Strong understanding of multiple Linux distros including all core services/daemons - Proven ability to troubleshoot system, network, and performance issues. - Experience with patch management process and tooling, endpoint protection, compliance and server hardening. - Familiarity with hybrid multi-cloud environments and virtualization technologies. - Excellent communication, documentation, and collaboration skills, including working across global teams. Now Qualifications (Preferred Qualifications) bullets: - Linux certifications such as RHCSA/RHCE, LFCS/LFCE, or LPIC. - Industry certifications: AWS, CISSP, CISM, ITIL. - Experience in regulated or security-sensitive environments (e.g., GxP,