Senior Software Engineer (Prime)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We have content for role description (What Makes This Opportunity Stand Out, Here’s What Your Day-to-Day Could Include). That could be About the role and Responsibilities. We have Minimum Qualifications (Qualifications). Required Skills (Skills). Desired Skills maybe also Skills. Compensation Range (Pay). Benefits: they list benefits in Why Intelliforce? section: Ample PTO, medical plans, 401k, bonus opportunities, culture. So Benefits section exists. Schedule not mentioned; we should not include Schedule. Also we should not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodations, powered by JazzHR, etc. Also remove application instructions (reach us at careers@..., schedule a call link). Also remove Equal Opportunity Matters paragraph. Also remove "You can reach us at..." and the link. Also remove "Equal Opportunity Matters" etc.
We need to preserve all substantive information. So we need to include the description paragraphs, bullet lists for duties/requirements/benefits.
We need to use - for any list of duties/requirements/benefits. For prose use
.
We need to decide sections: About the role (maybe introductory paragraph). Responsibilities (day-to-day). Qualifications (minimum qualifications). Skills (required and desired). Benefits (benefits). Pay (compensation range). Possibly also "About Intelliforce" but not required.
We must not create sections with filler. So we will include sections where we have content.
Let's extract content.
Intro: "Make an Impact Where It Matters Most At Intelliforce, we build and sustain mission software that has to operate as part of a much larger ecosystem. In this role, you will support Application Integration efforts by helping ensure applications, services, and data flows continue working together as platforms evolve."
That's about the role.
"What Makes This Opportunity Stand Out This role puts you at the point where software development meets real-world mission integration. You will not be working on an isolated application. You will help determine how capabilities interact with other systems, how data moves through the environment, and what needs to change as mission platforms modernize. A major part of the work involves sustaining what already matters while improving it for what comes next. You will refactor software for stronger interoperability, support system integration and testing, maintain policy compliance, and help deliver capabilities to external partners. At Intelliforce, your work is visible and your technical judgment matters. Because we support prime programs, our engineers stay close to meaningful mission work and the teams relying on what they build. Because we are a small business, leadership is accessible, communication is direct, and strong engineering gets noticed. Add in long-term stability, strong benefits, and a people-first culture, and this is an opportunity to have real influence across the full lifecycle of a mission capability."
That's also role description.
"Here’s What Your Day-to-Day Could Include Provide software engineering, systems engineering, Information Assurance, and testing support for mission effortsSustain existing mission software and integrated capabilitiesMaintain interoperability with upstream and downstream systemsAnalyze and troubleshoot system data flows across interconnected environmentsDevelop and refactor software to improve interoperability within the platformSupport build, integration, testing, and deployment activitiesSupport external mission partners integrating with or operating supported capabilitiesMaintain standards and policy compliance across supported systemsInvestigate software and integration issues and implement technical solutionsModify existing software to improve performance, compatibility, or functionalityParticipate in software testing, integration testing, and operational validationDevelop and maintain technical and system documentationWork with systems engineers, software engineers, security teams, testers, and mission stakeholders to resolve technical issuesEvaluate system behavior, data movement, interfaces, and operational dependencies as capabilities evolve"
That's responsibilities.
Minimum Qualifications: list items.
"Clearance: Top Secret Clearance with Full Scope Polygraph, must be active. We do not have the ability to sponsor clearancesCitizenship: Must be a U.S. Citizen. We cannot sponsor visas20 years of Software Engineering experience on programs and contracts of similar scope, type, and complexityBachelor’s degree in Computer Science or a related discipline from an accredited college or universityFour additional years of Software Engineering experience on projects with similar software processes may be substituted for the bachelor’s degreeFive years of demonstrated cloud experience supporting distributed scalable data technologies and related processing environments"
We need to format as list.
Required Skills: list.
"Experience developing, maintaining, and enhancing complex software systemsExperience integrating software into new or modified systems and operating environmentsExperience troubleshooting software, integration, and interoperability issuesExperience maintaining interfaces and data flows between upstream and downstream systemsExperience refactoring software to improve interoperability, maintainability, or performanceExperience supporting software build, integration, testing, and deployment activitiesExperience working in environments with defined security, IA, and policy requirementsExperience analyzing user and system requirements to derive software design and performance requirementsAbility to debug existing software and correct defectsExperience developing or implementing algorithms that meet functional and performance requirementsExperience developing and executing software test proceduresAbility to write and review software and system documentationExperience analyzing systems flow, data usage, work processes, and problem areasExperience working with complex data repositories and interfacesStrong collaboration skills across software, systems, security, testing, and operational teams"
Desired Skills: list.
"Experience supporting Analytical Application Integration or similar enterprise integration environmentsExperience with software modernization or application refactoring effortsExperience integrating software into converged or shared mission platformsExperience supporting deployed or expeditionary mission systemsExperience working directly with external mission partnersExperience sustaining operational software throughout its lifecycleExperience troubleshooting complex end-to-end data flowsExperience serving as a technical lead on software development or integration effortsExperience recommending new technologies and processes for complex software projectsExperience overseeing software quality and technical implementation across development teams"
Compensation Range: "$196,000.00 - $252,000.00 This salary range reflects our current market estimate for the role. Final compensation will depend on your experience, technical background, overall qualifications, and alignment with the position. We evaluate each candidate thoughtfully, so offers are shaped around the value you bring to the team"
Benefits: from Why Intelliforce? section.
"Ample PTO to rest and recharge—plus all federal holidays and your birthday off, just becauseMultiple medical plan options, including ones with zero deductible or premium for employeesGenerous 401(k) with immediate vesting—because your future matters nowExciting bonus opportunities, from profit sharing to quarterly awards and President’s Club recognitionA culture of collaboration, connection, and fun, with regular team activities that go beyond the work"
We need to format as list.
Now produce HTML.
We'll have:
About the role
... intro + what makes this opportunity stand out combined maybe as prose.
Responsibilities
- ... each responsibility as separate li.
Qualifications
- ... each qualification.
Skills
Maybe split Required and Desired? But we can combine as one Skills section with subheadings? The instruction only says use for section headings; we could have multiple h3 sections: Required Skills, Desired Skills. But they said use headings like Skills. Could also have one Skills section and list both required and desired. But to preserve detail, we could have two subsections: Required Skills and Desired Skills as each. That's okay because they are headings. The list of allowed headings includes Skills, but not Required Skills. However we can still use Skills heading and then inside have paragraphs distinguishing required vs desired. But better to follow instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those exact headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we can use those headings exactly. So we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We'll not use Requirements separately (maybe Qualifications covers). We'll not repeat job title.
Thus:
About the role
combined intro paragraphs.
Responsibilities
- ... each bullet.
Qualifications
- ... each qualification.
Skills
We could split into Required Skills and Desired Skills as headings inside? But we must use
for section headings; we could have Required Skills
and Desired Skills
but those are not in the list. Might be okay as they are still section headings. 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. So we can use any heading as long as it's . Safer to follow the examples: we could have a single Skills section and inside we can have
Required Skills:
then ... then Desired Skills:
then . That uses for prose headings inside. That respects the rule.
Thus Skills section:
Skills
then Required Skills:
...
Desired Skills:
...
Benefits: Benefits
...
Pay: Pay
...
We should not include Schedule.
Now we need to ensure we preserve all substantive information. Let's extract each bullet.
Responsibilities bullets (from day-to-day list). The text is a continuous string without punctuation. We need to split by capital letters? Let's manually separate:
- Provide software engineering, systems engineering, Information Assurance, and testing support for mission efforts
- Sustain existing mission software and integrated capabilities
- Maintain interoperability with upstream and downstream systems
- Analyze and troubleshoot system data flows across interconnected environments
- Develop and refactor software to improve interoperability within the platform
- Support build, integration, testing, and deployment activities
- Support external mission partners integrating with or operating supported capabilities
- Maintain standards and policy compliance across supported systems
- Investigate software and integration issues and implement technical solutions
- Modify existing software to improve performance, compatibility, or functionality
- Participate in software testing, integration testing, and operational validation
- Develop and maintain technical and system documentation
- Work with systems engineers, software engineers, security teams, testers, and mission stakeholders to resolve technical issues
- Evaluate system behavior, data movement, interfaces, and operational dependencies as capabilities evolve
That's 14 items.
Qualifications bullets:
- Clearance: Top Secret Clearance with Full Scope Polygraph, must be active. We do not have the ability to sponsor clearances
- Citizenship: Must be a U.S. Citizen. We cannot sponsor visas
- 20 years of Software Engineering experience on programs and contracts of similar scope, type, and complexity
- Bachelor’s degree in Computer Science or a related discipline from an accredited college or university
- Four additional years of Software Engineering experience on projects with similar software processes may be substituted for the bachelor’s degree
- Five years of demonstrated cloud experience supporting distributed scalable data technologies and related processing environments
We could combine first two as separate bullets.
Skills Required list: split by "Experience" or "Ability
. We need to decide sections: About the role (maybe introductory paragraph). Responsibilities (day-to-day). Qualifications (minimum qualifications). Skills (required and desired). Benefits (benefits). Pay (compensation range). Possibly also "About Intelliforce" but not required. We must not create sections with filler. So we will include sections where we have content. Let's extract content. Intro: "Make an Impact Where It Matters Most At Intelliforce, we build and sustain mission software that has to operate as part of a much larger ecosystem. In this role, you will support Application Integration efforts by helping ensure applications, services, and data flows continue working together as platforms evolve." That's about the role. "What Makes This Opportunity Stand Out This role puts you at the point where software development meets real-world mission integration. You will not be working on an isolated application. You will help determine how capabilities interact with other systems, how data moves through the environment, and what needs to change as mission platforms modernize. A major part of the work involves sustaining what already matters while improving it for what comes next. You will refactor software for stronger interoperability, support system integration and testing, maintain policy compliance, and help deliver capabilities to external partners. At Intelliforce, your work is visible and your technical judgment matters. Because we support prime programs, our engineers stay close to meaningful mission work and the teams relying on what they build. Because we are a small business, leadership is accessible, communication is direct, and strong engineering gets noticed. Add in long-term stability, strong benefits, and a people-first culture, and this is an opportunity to have real influence across the full lifecycle of a mission capability." That's also role description. "Here’s What Your Day-to-Day Could Include Provide software engineering, systems engineering, Information Assurance, and testing support for mission effortsSustain existing mission software and integrated capabilitiesMaintain interoperability with upstream and downstream systemsAnalyze and troubleshoot system data flows across interconnected environmentsDevelop and refactor software to improve interoperability within the platformSupport build, integration, testing, and deployment activitiesSupport external mission partners integrating with or operating supported capabilitiesMaintain standards and policy compliance across supported systemsInvestigate software and integration issues and implement technical solutionsModify existing software to improve performance, compatibility, or functionalityParticipate in software testing, integration testing, and operational validationDevelop and maintain technical and system documentationWork with systems engineers, software engineers, security teams, testers, and mission stakeholders to resolve technical issuesEvaluate system behavior, data movement, interfaces, and operational dependencies as capabilities evolve" That's responsibilities. Minimum Qualifications: list items. "Clearance: Top Secret Clearance with Full Scope Polygraph, must be active. We do not have the ability to sponsor clearancesCitizenship: Must be a U.S. Citizen. We cannot sponsor visas20 years of Software Engineering experience on programs and contracts of similar scope, type, and complexityBachelor’s degree in Computer Science or a related discipline from an accredited college or universityFour additional years of Software Engineering experience on projects with similar software processes may be substituted for the bachelor’s degreeFive years of demonstrated cloud experience supporting distributed scalable data technologies and related processing environments" We need to format as list. Required Skills: list. "Experience developing, maintaining, and enhancing complex software systemsExperience integrating software into new or modified systems and operating environmentsExperience troubleshooting software, integration, and interoperability issuesExperience maintaining interfaces and data flows between upstream and downstream systemsExperience refactoring software to improve interoperability, maintainability, or performanceExperience supporting software build, integration, testing, and deployment activitiesExperience working in environments with defined security, IA, and policy requirementsExperience analyzing user and system requirements to derive software design and performance requirementsAbility to debug existing software and correct defectsExperience developing or implementing algorithms that meet functional and performance requirementsExperience developing and executing software test proceduresAbility to write and review software and system documentationExperience analyzing systems flow, data usage, work processes, and problem areasExperience working with complex data repositories and interfacesStrong collaboration skills across software, systems, security, testing, and operational teams" Desired Skills: list. "Experience supporting Analytical Application Integration or similar enterprise integration environmentsExperience with software modernization or application refactoring effortsExperience integrating software into converged or shared mission platformsExperience supporting deployed or expeditionary mission systemsExperience working directly with external mission partnersExperience sustaining operational software throughout its lifecycleExperience troubleshooting complex end-to-end data flowsExperience serving as a technical lead on software development or integration effortsExperience recommending new technologies and processes for complex software projectsExperience overseeing software quality and technical implementation across development teams" Compensation Range: "$196,000.00 - $252,000.00 This salary range reflects our current market estimate for the role. Final compensation will depend on your experience, technical background, overall qualifications, and alignment with the position. We evaluate each candidate thoughtfully, so offers are shaped around the value you bring to the team" Benefits: from Why Intelliforce? section. "Ample PTO to rest and recharge—plus all federal holidays and your birthday off, just becauseMultiple medical plan options, including ones with zero deductible or premium for employeesGenerous 401(k) with immediate vesting—because your future matters nowExciting bonus opportunities, from profit sharing to quarterly awards and President’s Club recognitionA culture of collaboration, connection, and fun, with regular team activities that go beyond the work" We need to format as list. Now produce HTML. We'll have:
About the role
... intro + what makes this opportunity stand out combined maybe as prose.
Responsibilities
- ... each responsibility as separate li.
Qualifications
- ... each qualification.
Skills
Maybe split Required and Desired? But we can combine as one Skills section with subheadings? The instruction only says use for section headings; we could have multiple h3 sections: Required Skills, Desired Skills. But they said use headings like Skills. Could also have one Skills section and list both required and desired. But to preserve detail, we could have two subsections: Required Skills and Desired Skills as each. That's okay because they are headings. The list of allowed headings includes Skills, but not Required Skills. However we can still use Skills heading and then inside have paragraphs distinguishing required vs desired. But better to follow instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those exact headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we can use those headings exactly. So we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We'll not use Requirements separately (maybe Qualifications covers). We'll not repeat job title.
Thus:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those exact headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But to be safe, we can use those headings exactly. So we will have sections: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. We'll not use Requirements separately (maybe Qualifications covers). We'll not repeat job title.
Thus:
About the role
About the role
combined intro paragraphs.
Responsibilities
- ... each bullet.
Qualifications
- ... each qualification.
Skills
We could split into Required Skills and Desired Skills asheadings inside? But we must use
for section headings; we could have Required Skills
and Desired Skills
but those are not in the list. Might be okay as they are still section headings. 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. So we can use any heading as long as it's . Safer to follow the examples: we could have a single Skills section and inside we can have
for section headings. So we can use any heading as long as it's . Safer to follow the examples: we could have a single Skills section and inside we can have
Required Skills:
then- ... then
Desired Skills:
then- . That uses
for prose headings inside. That respects the rule. Thus Skills section:
Skills
thenRequired Skills:
- ...
Desired Skills:
- ...
Benefits
- ...
Pay
...
We should not include Schedule. Now we need to ensure we preserve all substantive information. Let's extract each bullet. Responsibilities bullets (from day-to-day list). The text is a continuous string without punctuation. We need to split by capital letters? Let's manually separate: - Provide software engineering, systems engineering, Information Assurance, and testing support for mission efforts - Sustain existing mission software and integrated capabilities - Maintain interoperability with upstream and downstream systems - Analyze and troubleshoot system data flows across interconnected environments - Develop and refactor software to improve interoperability within the platform - Support build, integration, testing, and deployment activities - Support external mission partners integrating with or operating supported capabilities - Maintain standards and policy compliance across supported systems - Investigate software and integration issues and implement technical solutions - Modify existing software to improve performance, compatibility, or functionality - Participate in software testing, integration testing, and operational validation - Develop and maintain technical and system documentation - Work with systems engineers, software engineers, security teams, testers, and mission stakeholders to resolve technical issues - Evaluate system behavior, data movement, interfaces, and operational dependencies as capabilities evolve That's 14 items. Qualifications bullets: - Clearance: Top Secret Clearance with Full Scope Polygraph, must be active. We do not have the ability to sponsor clearances - Citizenship: Must be a U.S. Citizen. We cannot sponsor visas - 20 years of Software Engineering experience on programs and contracts of similar scope, type, and complexity - Bachelor’s degree in Computer Science or a related discipline from an accredited college or university - Four additional years of Software Engineering experience on projects with similar software processes may be substituted for the bachelor’s degree - Five years of demonstrated cloud experience supporting distributed scalable data technologies and related processing environments We could combine first two as separate bullets. Skills Required list: split by "Experience" or "Ability