Software Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate (cookie/navigation/legal/EEO etc). Must preserve all substantive info. We need to parse the posting. Let's extract content: First paragraph: "i3 is seeking Software Engineers and Principal Software Engineers to join our team in Huntsville, Alabama. You will support the Integrated Battle Command System (IBCS) System Team - a specialized Agile team responsible for enabling and sustaining the Agile development environment, including development and maintenance of the Continuous Delivery Pipeline for mission‑critical command and control (C2) software. In this role, you will partner closely with software, systems, DevOps, networking, cybersecurity, and infrastructure teams to deliver robust, secure, and scalable solutions in support of IBCS. This position is well‑suited for an engineer who enjoys cross‑functional coordination, solving complex integration problems, and driving continuous improvement across development pipelines and environments. Serve as a key member of the IBCS System Team, supporting the Agile development environment and Continuous Delivery Pipeline for multiple software baselines.Collaborate cross‑functionally with software, systems, DevOps, networking, cybersecurity, and infrastructure teams to plan, integrate, and improve end‑to‑end delivery workflows.Communicate effectively with both technical and non‑technical stakeholders, clearly conveying technical issues, options, and impacts.Apply strong problem-solving skills in ambiguous situations where requirements, priorities, and external constraints may change rapidly.Influence and coordinate work across multiple teams without direct line authority, ensuring alignment on priorities and commitments.Apply DevOps concepts and best practices to support software delivery pipelines, even when not acting as the primary implementer.Take ownership to identify roadblocks, track actions, and drive issues through to closure.Operate comfortably in an environment where priorities shift and the work mix includes both hands-on technical tasks and coordination/facilitation work.Maintain technical credibility across multiple disciplines to effectively communicate with engineers and understand the work and trade space being discussed.Work in a fast-paced environment with high expectations, diverse assignments, and collaborative team settings across all levels of the organization.Other duties as assigned." That's the role description. Could be "About the role" or "Responsibilities". Usually "About the role" is a summary, "Responsibilities" list duties. We have many duties listed as sentences. Could split into bullet list. Next: "Education, Experience and Required skills This role can be filled at mulitple levelsSoftware Engineer- Bachelor's degree in a STEM field and at least 2 years of relevant experience, or Master's degree in STEM field and 0 years of experience.Principal Software Engineer- Bachelor's degree in a STEM field and at least 5 years of relevant experience, Master's degree in STEM field and 3 years of relevant experience, or PhD in STEM field and 0 years Strong experience with Continuous Integration / Continuous Delivery (CI/CD) concepts and implementation, includingVirtualized environments and virtual machines.Containerization technologies.Container orchestration platforms. Hands-on experience withAnsible and Ansible playbooks; Ansible Automation Platform.Jenkins or similar CI/CD automation tools.Sonatype Nexus or similar artifact repository managers.Proficiency in Linux-based development and runtime environments.Experience with modern configuration management and source control tools (Git / GitLab).Current CompTIA Security+ certificationActive Secret Clearance and the ability to maintain a clearance required.Must be a U.S. Citizen." That's requirements/qualifications/skills. Then: "Preferred Qualifications Experience with Python for automation, tooling, or pipeline integration.CI/CD experience in classified or highly controlled environments.Experience designing, implementing, and maintaining test bench and benchmarking CI/CD pipelines.Experience defining CI/CD requirements, user stories, and use cases in partnership with development and test teams.Familiarity with Agile frameworks (e.g., Scrum, SAFe)" Then: "Physical Demands The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. While performing the duties of this job, the employee is regularly required to talk or hear. The employee frequently is required to stand; walk; handle or feel; and reach with hands and arms. The employee is occasionally required to sit; climb or balance; and stoop, kneel, crouch or crawl. The employee must be able to lift and/or move up to 10 pounds and occasionally lift and/or move up to 25 pounds. Specific vision abilities required by this job include close vision, distance vision, peripheral vision, depth perception and ability to adjust focus. Regular i3 hours are 800 a.m. - 500 p.m. Monday-Friday, however, additional hours may be required on occasion. Regular and punctual attendance is required." That includes schedule (hours). Also physical demands maybe not needed but could be part of responsibilities? Probably we can include schedule section. Then: "Founded in 2007, Integration Innovation, Inc. (i3) is headquartered in Huntsville, AL, with additional offices in Orlando, FL, and the National Capital Region. We are a 100% team member-owned mid-tier integrator with over 800 employee-owners, and our culture speaks for itself we've earned ten Best Places to Work® awards, driven by strong employee engagement, transparent leadership, and a genuine commitment to communication. i3 team members operate at the leading edge of national defense across a broad range of technical disciplines, from systems and software engineering to modeling, simulation, and training solutions to cybersecurity, digital engineering, and enterprise IT. We also take products from prototype through production, bringing that same engineering rigor to manufacturing and delivering hardware at scale. For candidates, that means a rare opportunity the innovation and mission focus of an engineering services company paired with the hands-on impact of building and delivering real solutions that benefit the Warfighter, all inside an employee-owned company where your contributions directly shape both the mission and your ownership stake in the business." That's about company, could be "About the role"? Actually "About the role" is about the job; company description maybe not needed but could be included as part of "About the role"? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include sections that have content. We have: - About the role: maybe a brief summary (first paragraph). Could be used. - Responsibilities: list of duties. - Requirements: education/experience required. - Qualifications: maybe preferred qualifications. - Skills: maybe technical skills list. - Benefits: not mentioned explicitly (no benefits). So we should not create Benefits section. - Pay: not mentioned. - Schedule: we have regular hours. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Schedule. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive info. So we need to capture all details. Let's craft:

  About the role

  i3 is seeking Software Engineers and Principal Software Engineers to join our team in Huntsville, Alabama. You will support the Integrated Battle Command System (IBCS) System Team – a specialized Agile team responsible for enabling and sustaining the Agile development environment, including development and maintenance of the Continuous Delivery Pipeline for mission‑critical command and control (C2) software. In this role, you will partner closely with software, systems, DevOps, networking, cybersecurity, and infrastructure teams to deliver robust, secure, and scalable solutions in support of IBCS. This position is well‑suited for an engineer who enjoys cross‑functional coordination, solving complex integration problems, and driving continuous improvement across development pipelines and environments.

  Then Responsibilities: list bullet points from the many sentences. Let's extract duties: - Serve as a key member of the IBCS System Team, supporting the Agile development environment and Continuous Delivery Pipeline for multiple software baselines. - Collaborate cross‑functionally with software, systems, DevOps, networking, cybersecurity, and infrastructure teams to plan, integrate, and improve end‑to‑end delivery workflows. - Communicate effectively with both technical and non‑technical stakeholders, clearly conveying technical issues, options, and impacts. - Apply strong problem‑solving skills in ambiguous situations where requirements, priorities, and external constraints may change rapidly. - Influence and coordinate work across multiple teams without direct line authority, ensuring alignment on priorities and commitments. - Apply DevOps concepts and best practices to support software delivery pipelines, even when not acting as the primary implementer. - Take ownership to identify roadblocks, track actions, and drive issues through to closure. - Operate comfortably in an environment where priorities shift and the work mix includes both hands‑on technical tasks and coordination/facilitation work. - Maintain technical credibility across multiple disciplines to effectively communicate with engineers and understand the work and trade space being discussed. - Work in a fast‑paced environment with high expectations, diverse assignments, and collaborative team settings across all levels of the organization. - Other duties as assigned. We'll put each as
• . Next Requirements: education/experience required, plus mandatory certifications/clearance. We have: Software Engineer: - Bachelor's degree in a STEM field and at least 2 years of relevant experience, or Master's degree in STEM field and 0 years of experience. Principal Software Engineer: - Bachelor's degree in a STEM field and at least 5 years of relevant experience, Master's degree in STEM field and 3 years of relevant experience, or PhD in STEM field and 0 years. Strong experience with CI/CD concepts and implementation, including: - Virtualized environments and virtual machines. - Containerization technologies. - Container orchestration platforms. - Hands‑on experience with Ansible and Ansible playbooks; Ansible Automation Platform. - Jenkins or similar CI/CD automation tools. - Sonatype Nexus or similar artifact repository managers. - Proficiency in Linux‑based development and runtime environments. - Experience with modern configuration management and source control tools (Git / GitLab). - Current CompTIA Security+ certification. - Active Secret Clearance and the ability to maintain a clearance required. - Must be a U.S. Citizen. We'll put these as list items under Requirements. Qualifications: Preferred Qualifications list: - Experience with Python for automation, tooling, or pipeline integration. - CI/CD experience in classified or highly controlled environments. - Experience designing, implementing, and maintaining test bench and benchmarking CI/CD pipelines. - Experience defining CI/CD requirements, user stories, and use cases in partnership with development and test teams. - Familiarity with Agile frameworks (e.g., Scrum, SAFe). Skills: maybe we can separate technical skills from requirements? But we already listed many technical skills in Requirements. Could create Skills section for things like "Strong problem‑solving skills", "Ability to influence without authority", etc. However the instruction: prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask for headings e.g. Requirements, Qualifications, Skills. We can include all three if they have content. We already have Requirements (education/experience + mandatory skills/certifications). Qualifications (preferred). Skills maybe we can list soft skills: cross‑functional coordination, problem‑solving, communication, influence, ownership, technical credibility, fast‑paced adaptability. But those are already in responsibilities. Might be redundant. Perhaps better to not create Skills section if it would be thin. But we have many technical skills already in Requirements; we could move some to Skills. However we need to preserve all substantive info; we can keep them in Requirements and not duplicate. Thus we can have sections: About the role, Responsibilities, Requirements, Qualifications, Schedule. We need Schedule: Regular i3 hours are 800 a.m. - 500 p.m. Monday-Friday, however, additional hours