Platform Software Engineer II

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Key info: - Role: Platform Engineer II, Missile Defense Sensors (MDS) Software Department. - About the role: description of company, mission, etc. Could be "About the role" section. - Responsibilities: bullet list under "What You Will Do". - Requirements: security clearance, US citizenship, etc. Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements" etc. - Qualifications: "Qualifications You Must Have" and "Qualifications We Prefer". Could combine into Requirements and Qualifications sections. The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. - Skills: maybe list of tools etc. - Benefits: mention benefits list. - Pay: salary range. - Schedule: onsite role, location info. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO etc. Also remove duplicated lines, application instructions like "Learn More & Apply Now", "Please ensure the role type defined below is appropriate for your needs before applying to this role." etc. We must preserve all substantive information. Let's extract substantive content: Company description: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Raytheon brings the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. We deliver solutions that help our nation and allies defend freedom and deter aggression, creating a safer, more secure world. Join us and help shape the future of aerospace and defense." That's about the company; could be placed under About the role. Role description: "We are seeking a Platform Engineer II to join the Missile Defense Sensors (MDS) Software Department. The MDS Software mission is to provide world-class radar and Command and Control (C2) Software for our customers’ wide array of surveillance and warning systems. Platform Engineers are responsible for designing, optimizing, and maintaining the critical software infrastructure that underpins these systems. The ideal candidate will bring experience in platform design, system integration, automation, and performance optimization, as well as the ability to collaborate across teams to deliver high-quality solutions. This will be an onsite role in either Woburn, MA or Tewksbury, MA depending on the program assigned." That could be part of About the role or Responsibilities? Probably About the role includes overview. Responsibilities bullet list: - Design, develop, and maintain platform architecture and modernization strategies that support mission-critical radar and Command and/or Control systems. - Develop and manage advanced tools and frameworks to ensure secure, automated build, test and release processes at scale using CI/CD pipelines and DevSecOps workflows. - Collaborate with cross-functional teams, including software developers, system engineers, and test teams, to ensure seamless integration of application software into system platforms. - Support optimization of platform performance, reliability, and scalability to meet the specific needs of defense programs. - Implement and maintain secure computing environments, adhering to cybersecurity best practices and compliance standards. - Support system-level integration, troubleshooting, and debugging of platform-related issues during development, testing, and operational phases. - Participate in efforts to improve platform automation and monitoring, leveraging tools such as Ansible, Terraform, and Kubernetes. - Participate in an Agile Scrum/Kanban environment, supporting planning, estimation and technical execution. Requirements (must have): security clearance, US citizenship, etc. - Active and transferable U.S. government issued security clearance is required prior to start date. - U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. - Ability to obtain INTERIM U.S. government issued security clearance is required prior to start date. - Typically requires a Bachelor’s in Science, Technology, Engineering or Mathematics (STEM) and a minimum of 2 years of prior relevant experience unless prohibited by local laws/regulations. - Experience in Linux platform engineering and administration. - Familiarity with Docker, Kubernetes, Terraform, Ansible and/or virtualization tools such as VMware/KVM. - Familiarity with scripting and automation tools such as Python, Bash and/or PowerShell. - Familiarity with CI/CD systems and/or secure build/deployment architectures. - The ability to obtain and maintain a U.S. government-issued security clearance is required prior to start date. - U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. Some duplicates; we need to preserve all substantive info but avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't say we must deduplicate, but we should avoid duplicated lines? It says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. So we need to deduplicate repeated statements. Thus we can combine: U.S. citizenship required, security clearance required (active and transferable, ability to obtain interim). Also Bachelor's STEM + 2 years experience. Experience in Linux platform engineering/admin. Familiarity with Docker, Kubernetes, Terraform, Ansible and/or VMware/KVM. Familiarity with scripting/automation tools Python, Bash, PowerShell. Familiarity with CI/CD systems and/or secure build/deployment architectures. Qualifications We Prefer (preferred): - Experience with network configuration, protocols, and troubleshooting tools. - Knowledge of large-scale, real-time systems, including radar or Command and Control systems or similar. - Familiarity with DevSecOps practices and tools. - Experience with graphing software such as Grafana. - Familiarity with Agile management tools such as JIRA and Confluence. - Experience with advanced performance tuning, monitoring, and troubleshooting of system platforms. - Experience in high‑availability systems, distributed architectures, or high‑performance computing environments. - Strong analytical and problem-solving skills. - Proven ability to work in a fast-paced, dynamic environment with time-critical requirements. - A passion for continuous learning and cross-team collaboration. Skills: Could be a section listing tools etc. But we already have many in qualifications. Perhaps we can have a Skills section summarizing technical skills: Linux, Docker, Kubernetes, Terraform, Ansible, VMware/KVM, Python, Bash, PowerShell, CI/CD, DevSecOps, network config, Grafana, JIRA, Confluence, etc. However we must not invent content; we can extract from qualifications. Benefits: list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also mention that specific benefits depend on business unit and collective bargaining. Pay: salary range: 68,900 USD - 131,100 USD. Schedule: onsite role, location: Woburn, MA or Tewksbury, MA depending on program assigned. Also mention role type: Onsite. We should not include application instructions like "Learn More & Apply Now", "Please ensure the role type defined below is appropriate for your needs before applying to this role." etc. Also remove duplicated lines like the security clearance repeated. Now produce HTML fragment with headings

for each section that has content. Potential sections: - About the role (company description + role overview) - Responsibilities - Requirements (must-have) - Qualifications (preferred) maybe separate? Could combine Requirements and Qualifications? But we have both Must Have and Preferred. Could have Requirements for must-have, Qualifications for preferred. Or we could have Requirements covering both? The instruction list includes Requirements and Qualifications as separate possible headings. We'll use both. - Skills: maybe we can list technical skills extracted. - Benefits - Pay - Schedule We need to ensure we don't create sections with placeholder text. All sections have real content. Now craft HTML. We'll need to use

• for lists. We'll need to use

  for prose. Let's draft. About the role: combine company description and role overview into a few paragraphs. We can have two

  elements. First paragraph: company description. Second paragraph: role overview: seeking Platform Engineer II, MDS Software Department, mission, responsibilities overview, location. We must not repeat job title as heading, but we can mention it in prose. Now Responsibilities:

  Responsibilities

  then
  with each bullet. Requirements:

  Requirements

  then
  with must-have items. Qualifications:

  Qualifications

  then
  with preferred items. Skills: maybe we can combine some of the technical skills into a list. But we already have many in Requirements and Qualifications. Could still have a Skills section summarizing tools: Linux, Docker, Kubernetes, Terraform, Ansible, VMware/KVM, Python, Bash, PowerShell, CI/CD, DevSecOps, network configuration, Grafana, JIRA, Confluence, etc. However we need to ensure we are not inventing; we can pull from the text. But we already listed many of those in Requirements and Qualifications. Having a separate Skills section might duplicate content. The instruction says remove duplicated lines. So we should avoid duplicating same content across sections. So maybe we don't need a separate Skills section; we can incorporate skills into Requirements and Qualifications. The instruction list includes Skills as a possible heading but we only include if posting has real specific content for it. The posting does mention specific skills/tools; we could put them under Skills, but then we would be duplicating if we also list them under Requirements/Qualifications. To avoid duplication, we could decide to put all skill-related content under Skills, and keep Requirements focused on clearance, citizenship, education, experience. Qualifications could be about preferred experience/skills? But the posting splits into Must Have and Qualifications We Prefer. So we could map Must Have to Requirements, and Qualifications We Prefer to Qualifications. Then Skills could be omitted or we could combine some overlapping? But we risk missing some content if we omit Skills. However the instruction says "Prefer a few substantive sections over many thin ones." So we could combine Must Have and Qualifications We Prefer into one Qualifications section, and have Requirements for clearance/citizenship/education? But the posting also includes education/experience under Must Have. So maybe we treat Requirements as clearance/citizenship, and Qualifications as education/experience/skills. However the instruction list includes both Requirements and Qualifications as separate headings; we can use both. Let's decide: - About the role: company + role overview. - Responsibilities: bullet list of duties. - Requirements: security clearance, US citizenship, ability to obtain interim clearance. - Qualifications: education (Bachelor's STEM + 2 years experience), Linux experience, familiarity with Docker/Kubernetes/Terraform/Ansible/VMware/KVM, scripting tools Python/Bash/PowerShell, CI/CD, plus preferred qualifications list (network config, large-scale real-time systems, DevSecOps, Grafana, JIRA/Confluence, performance tuning, high-availability, analytical skills, fast-paced environment, passion for learning). This would be a long list but okay. - Benefits: bullet list. - Pay: paragraph with salary range. - Schedule: paragraph about onsite, location options. We must not duplicate. Ensure we don't repeat same bullet in both Requirements and Qualifications. Let's