Sr. Platform Engineer (Up to $25k Sign-on) (6842)

We need to output HTML fragment only, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do not repeat job title as heading. Do not put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it — never emit heading with filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - Intro: "As a Sr. Platform Engineer, you’ll play a critical role in designing, operating, and improving shared cloud and DevOps platform services used by multiple customer mission teams. This role supports Linux-based environments, AWS services including EC2, S3, RDS, and load balancing, containerized services using Docker or Podman, and CI/CD tooling such as Jenkins or GitLab. This role provides reliable, secure, and reusable platform capabilities while customer teams retain ownership of their application-specific pipelines, releases, and delivery processes. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers." That's about the role / company overview. Could be "About the role" or maybe "About the role". We'll treat that as About the role. Then "What you’ll do:" list of responsibilities. Then "What you’ll need to succeed:" list of requirements. Then "SALARY RANGE: $170,000 - $260,000" plus explanation. Then "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." Then "Benefits: All full-time employees are eligible to participate in our benefits programs: ..." list. Then other sections: "Commitment to Non-Discrimination", "What we want you to know:", "Not ready to apply now? Sign up to join our newsletter here." Those are boilerplate/legal/EEO etc. Should be removed. Also "Application Deadline: Applications will be accepted on a rolling basis until the position is filled; candidates are encouraged to apply as early as possible for full consideration." That's application instruction; remove. Also "Like we said, we are big fans of our people. That’s why we offer a generous benefits package, professional growth, and valuable time to recharge. Learn more about our company culture code and benefits. Plus, check out our accolades." This is fluff but maybe part of benefits? It's generic; but we already have benefits list. Might be considered filler; but we can keep as part of benefits prose? It's not specific detail; but it's not placeholder like "commensurate with experience". It's still generic but maybe we can include as part of benefits prose. However instruction: Prefer few substantive sections over many thin ones. We can combine benefits and additional compensation maybe. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role (intro). Responsibilities (What you’ll do). Requirements (What you’ll need to succeed). Qualifications? Might be overlapping with requirements; but we can treat "What you’ll need to succeed" as Requirements. Qualifications maybe not separate; we could omit if no distinct content. Skills: maybe we can extract skills from requirements: Linux, AWS, Docker/Podman, CI/CD, Git, Bash/Python, etc. Could be a Skills section. But we already have requirements list includes those; we could combine. However we need to decide which sections to include based on real specific content. We have Pay: salary range given. Also Additional Compensation (bonuses). So we can have Pay section with salary range and mention additional compensation. We have Benefits: list. Schedule: Not mentioned; no info about work schedule (e.g., full-time, remote, hours). So we should NOT create Schedule section because no specific content. Qualifications: Could be separate from Requirements? The posting lumps experience etc under "What you’ll need to succeed". That's both qualifications and requirements. Could treat as Requirements. Qualifications maybe not needed. Skills: Could be separate but we might avoid thin section. However we have specific skills listed: Linux, AWS EC2/S3/RDS/Load Balancing, Docker/Podman, Jenkins/GitLab, Git, Bash/Python. Could be a Skills section. But we already have them in requirements; we could keep Requirements and not Skills. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to format lists with

  • . For prose, use

    . We need to preserve all substantive information; do not invent or summarize away detail. Let's extract exact sentences. About the role: The introductory paragraph(s) before "What you’ll do:". Original: "As a Sr. Platform Engineer, you’ll play a critical role in designing, operating, and improving shared cloud and DevOps platform services used by multiple customer mission teams. This role supports Linux-based environments, AWS services including EC2, S3, RDS, and load balancing, containerized services using Docker or Podman, and CI/CD tooling such as Jenkins or GitLab. This role provides reliable, secure, and reusable platform capabilities while customer teams retain ownership of their application-specific pipelines, releases, and delivery processes. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers." We should keep that as prose. Could be multiple

    but we can combine into one

    . It's fine. Responsibilities: Under "What you’ll do:" list items: - Engineer, administer, automate, and sustain shared platform services that support multiple customer teams. - Build, maintain, and troubleshoot shared Linux-based cloud and DevOps services used by multiple customer mission teams. - Provision, configure, troubleshoot, and optimize AWS infrastructure and services, including EC2, S3, RDS, and Elastic Load Balancing capabilities. - Support the operation of containerized services and workloads. - Configure, administer, integrate, and troubleshoot CI/CD tooling such as Jenkins and/or GitLab. - Develop and maintain automation scripts, configuration patterns, deployment procedures, and reusable technical solutions to improve platform reliability and repeatability. - Integrate shared platform tooling with source control, artifact repositories, authentication/authorization services, security tooling, monitoring, logging, and ticketing systems as applicable. We need to preserve each as

  • . Requirements: Under "What you’ll need to succeed:" list: - Active TS/SCI with CI Poly (or ability to obtain CI Poly). - 5-10+ years of hands-on experience in DevOps, platform operations, cloud infrastructure, or infrastructure engineering. - Experience administering and troubleshooting Linux-based systems in production or mission environments. - Experience supporting AWS infrastructure (e.g., EC2, S3, RDS, Security Groups, and Load Balancing). - Experience building, running, troubleshooting, or supporting containerized workloads with Docker and/or Podman. - Experience with building CI/CD pipelines from scratch with Gitlab and/or Jenkins. - Experience with Git-based source-control workflows. - Ability to automate infrastructure and processes using Bash and/or Python. - Ability to work independently and communicate with stakeholders across a global enterprise and cross-functional teams to drive project completion. We need to keep each as
  • . Benefits: Under "Benefits:" list: - Health, dental, and vision insurance - 401(k) retirement plan with company match - Paid time off (PTO) and holidays - Parental Leave and dependent care - Flexible work arrangements - Professional development opportunities - Employee assistance and wellness programs Also there is preceding sentence: "All full-time employees are eligible to participate in our benefits programs:" That's prose; we can include as

    before list. Also there is fluff: "Like we said, we are big fans of our people. That’s why we offer a generous benefits package, professional growth, and valuable time to recharge. Learn more about our company culture code and benefits. Plus, check out our accolades." This is somewhat generic but could be considered part of benefits prose. However it's not specific detail; but it's not placeholder. Might be okay to include as additional prose after list? But we risk adding thin content. Probably better to omit as it's not specific benefit details; it's more marketing. The instruction: "Prefer a few substantive sections over many thin ones." This fluff is thin; we could omit. We'll keep only the concrete benefits list. Pay: Under "SALARY RANGE: $170,000 - $260,000" plus explanation. We have: "SALARY RANGE: $170,000 - $260,000The salary range for this position is determined based on qualifications, skills, and relevant experience. The final salary offered will be determined based on several factors including: The candidate's professional background and relevant work experienceThe specific responsibilities of the role and organizational needsInternal equity and alignment with current team compensationThis role is also eligible for additional compensation, subject to the terms and policies of MetroStar, which may include:Performance-based bonusesCompany-paid training and/or certificationsReferral bonuses Application Deadline: Applications will be accepted on a rolling basis until the position is filled; candidates are encouraged to apply as early as possible for full consideration.Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." We need to remove application deadline line. Also remove duplicated lines? There's some run-on text without spaces. We need to parse. Let's extract substantive pay info: - Salary range: $170,000 - $260,000. - Salary range determined based on qualifications, skills, and relevant experience. - Final salary offered based on several factors: candidate's professional background and relevant work experience; specific responsibilities of the role and organizational needs; internal equity and alignment with current team compensation. - Role eligible for additional compensation, subject to terms/policies of MetroStar, which may include: performance-based bonuses; company-paid training and/or certifications; referral bonuses. - Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance. We can combine. We should not include "Application Deadline" line. We need to format as prose (

    ) maybe with a list for additional compensation types. We could have

    for salary range explanation, then

    • for additional compensation types. But we must not create thin sections; but Pay section is substantive. Now we need to output only HTML fragment, no /, no markdown. Thus:

      About the role

      ...

      Responsibilities

      • ...
      ...

      Requirements

      • ...
      ...

      Benefits

      All full-time employees are eligible to participate in our benefits programs:

      • Health, dental, and vision insurance
      • 401(k) retirement plan with company match
      • Paid time off (PTO) and holidays
      • Parental Leave and dependent care
      • Flexible work arrangements
      • Professional