Senior Software Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Description: We are seeking an experienced Senior Software Engineer... Based in Arlington, VA... embedded within Agile Scrum team... etc. - What You’ll Work On: list of software portfolio items. - Primary Responsibilities: bullet list. - Basic Qualifications: bullet list. - Preferred Qualifications: bullet list. - Pay Range: $107,900.00 - $195,050.00. - Pay And Benefits: mention competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. More details at link. - No explicit schedule info (maybe travel up to 25% mentioned under responsibilities). That's not schedule but travel. - No explicit benefits list beyond generic; but we have "Pay and benefits" paragraph describing categories. Could we create a Benefits section? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. We have Pay Range specific numbers, so Pay section is okay. Benefits: they mention "competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." That's specific enough? It's a list of benefit categories. Could be considered specific. We'll include Benefits section with those items. Schedule: Not mentioned besides travel up to 25% (not schedule). No explicit schedule like full-time, part-time, shift. So we should not create Schedule section. About the role: we have description paragraph at start. Could be About the role. Responsibilities: we have Primary Responsibilities list. Requirements: Could be Basic Qualifications. Qualifications: Could be Preferred Qualifications. Skills: maybe combine some skills from qualifications? But we already have Requirements and Qualifications sections. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We need to avoid duplication. We'll include: -

About the role

with paragraph summarizing the description (but must preserve ALL substantive information; do not invent or summarize away detail). So we need to keep the description text verbatim? We can include the description as a paragraph (

) under About the role. Must not lose any detail. So we can copy the description paragraph(s) exactly. The description includes: "We are seeking an experienced Senior Software Engineer to join our team in developing the forefront of unmanned and autonomous ship development for the US Government. Based in Arlington, VA, you will be embedded within an Agile Scrum team – designing, building, and testing software that powers some of the nation’s most critical maritime programs. The candidate will help to lead projects of significant national importance, guiding the transformation of existing vessels into autonomous platforms and supporting the development of new ships from concept through deployment." We'll put that as a

. -

What You’ll Work On

maybe not a standard heading but we could treat as About the role? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. But we could also include "What You’ll Work On" as a subsection under About the role? However we need to preserve all substantive information. Could embed that list under About the role as a

. That would be okay. But we also have Primary Responsibilities list; we can put under

Responsibilities

. Basic Qualifications under

Requirements

. Preferred Qualifications under

Qualifications

. Pay under

Pay

. Benefits under

Benefits

. We should not include Schedule. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the "If you're looking for comfort, keep scrolling..." and the Leidos motivational text, the "Original Posting September 21, 2026", the "For U.S. Positions: While subject to change..." etc. Also the "About Leidos" paragraph, "Pay And Benefits" (we already used benefits but need to ensure we don't duplicate). Also the "Securing Your Data", "Commitment to Non-Discrimination", "#Featuredjob". All that should be removed. We must preserve all substantive information: that includes the description, what you'll work on, responsibilities, basic qualifications, preferred qualifications, pay range, benefits list. We need to ensure we don't lose any bullet points. Let's extract: Description paragraph (first paragraph). We'll keep as is. What You’ll Work On: list: - Ship Automation & Control Systems - Autonomous Navigation - Sensor Fusion & Processing - Communication Systems - Modeling & Simulation for verification and software testing Primary Responsibilities bullet list: - Analyze, design, code and update software for new features and performance improvements. - Participate in the full software development lifecycle, from requirements and design through implementation, testing, and deployment. - Serve as technical lead for small projects, providing direction and ensuring technical quality. - Mentor and coach junior engineers, fostering professional growth and elevating team capabilities. - Perform peer reviews of software, ensuring quality, maintainability, and adherence to best practices. - Drive continuous process improvement, collaborating with the team to optimize workflows, tools, and engineering practices. - Assist with evaluating field tests, analyzing results and transitioning findings into actionable software enhancements. - Engage directly with client project stakeholders, communicating technical progress, risks, and solutions effectively. - Some travel (up to 25%) to support field testing, client engagements, and program milestones. Basic Qualifications: - A Bachelor’s degree in Computer Science or STEM field plus 8+ years of professional software development experience, or 6+ years of professional experience with a Master’s degree. - Understanding of data structures. - Professional experience using C++ and Linux. - Knowledge of the Linux operating system. - Experience with software source control and configuration management tools. - Significant experience working in a team environment, including experience providing guidance and coaching other developers - Exposure to one or more of the following: high availability, sensor fusion, target tracking, path planning, communications systems, or military systems integration. - Ability to obtain and maintain a Secret Security Clearance. Preferred Qualifications: - Familiarity with the Atlassian tool suite (Jira, Confluence) - Familiarity with automated build processes (Bamboo, Jenkins, etc.) - Professional experience using Java and front-end development frameworks. - Knowledge and experience with relational databases such as Oracle, MySQL, PostgreSQL, MariaDB, or Microsoft SQL Server. - Experience with Python. - Experience designing complex systems, considering performance and user requirements. - Experience with interface communication standards / protocols such as TCP/IP, UDP, and DDS. - Familiarity with game theory, artificial intelligence, petri nets, safety critical software. - Demonstrated experience with Docker and Kubernetes (RKE2) in containerization, Kubernetes management and automation technologies. - Experienced in designing, implementing, and analyzing simulations involving extensive datasets, ensuring efficient data processing and accurate modeling outcomes. - Proficient in applying vector geometry concepts for spatial analysis, modeling, and problem-solving in simulation environments. - Active Secret Security Clearance preferred Pay Range: $107,900.00 - $195,050.00 Benefits: "competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." Also maybe more details at link but we can just list those. We should not include the sentence "Pay and benefits are fundamental to any career decision..." etc. But we need to keep the substantive benefit items. The paragraph includes: "Employment benefits include competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement." We'll keep that as a

or

. Better to make a
with each benefit. Thus Benefits section:
• competitive compensation
• Health and Wellness programs
• Income Protection
• Paid Leave
• Retirement
Now we need to output only HTML fragment, no /, no markdown. We'll structure:

About the role

We are seeking an experienced Senior Software Engineer to join our team in developing the forefront of unmanned and autonomous ship development for the US Government. Based in Arlington, VA, you will be embedded within an Agile Scrum team – designing, building, and testing software that powers some of the nation’s most critical maritime programs. The candidate will help to lead projects of significant national importance, guiding the transformation of existing vessels into autonomous platforms and supporting the development of new ships from concept through deployment.

What You’ll Work On

• Ship Automation & Control Systems
• Autonomous Navigation
• Sensor Fusion & Processing
• Communication Systems
• Modeling & Simulation for verification and software testing
But "What You’ll Work On" is not one of the prescribed headings. However we could incorporate that list under About the role as a
after the paragraph. But the instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but they gave examples. Safer to stick to those headings only. So we should not create a heading for "What You’ll Work On". Instead we can include that list under About the role as a

. That would preserve the info. Thus About the role section will have paragraph + ul. Similarly, we might not need a separate "What You’ll Work On" heading. Now Responsibilities:

Responsibilities

with ul. Requirements:

Requirements

with ul (basic qualifications). Qualifications:

Qualifications

with ul (preferred qualifications). Pay:

Pay

with p containing the range. Benefits:

Benefits

with ul. We must not include Schedule. Check for any other sections like Skills: we could combine some skills but we already have Requirements and Qualifications; maybe we can omit Skills. Now ensure we didn't lose any detail: The description paragraph includes the location Arlington, VA, Agile Scrum team, etc. Good. The "What You’ll Work On" list is included as ul under About the role. Check that we didn't miss any bullet from responsibilities: we have all nine. Check basic qualifications: we have eight bullet points (including the degree/experience, understanding of data structures, professional experience using C++ and Linux, knowledge of Linux OS, experience with source control, significant experience in team environment, exposure to one or more of..., ability to obtain and maintain Secret Security Clearance). Ensure we kept the line "Significant experience working in a team environment, including experience providing guidance and coaching other developers" (note there is a line break after developers but it's fine). Also "Exposure to one or more of the following: high availability, sensor