Sr. Full-Stack Engineer (USPACOM)
Culmen International · Alexandria, VA · 1 mo ago
EngineeringFull-time
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 must not repeat job title as heading. No Job ID. Remove boilerplate, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- About the role: maybe a paragraph describing role. The posting starts: "Culmen International is seeking a Senior Full-Stack Engineer to support secure, mission-ready software development for USPACOM J32 targeting and mission-planning workflows. Must be located in the NCR and able to commute onsite to the Mark Center. As the Senior Full-Stack Engineer, you will design, develop, integrate, and field secure software applications that support targeting and mission-planning operations."
We can put that as About the role.
- Responsibilities: list of duties. Many bullet-like sentences: "You will build user-facing and backend services, develop system integrations, implement auditability and security controls, and collaborate directly with operators and subject matter experts to translate complex operational processes into intuitive, mission-focused software solutions." Then many more: "Design, build, and field secure, mission-ready software supporting USPACOM J32 joint targeting and fires-planning workflows." etc. We'll need to extract each distinct duty as . Must preserve all substantive info; not invent.
- Requirements: maybe the eligibility and experience: "7+ years of professional full-stack software engineering experience, including delivery of complex, data-intensive applications." Also "Eligibility for TS/SCI; active clearance strongly preferred." Also "Ability to support on-site engagement with USPACOM J32 operators as mission needs require." Also "Experience with joint targeting, Joint Fires, weaponeering, target-effect pairing, force assignment, or course-of-action analysis." Also "Experience working in DoD classified environments, disconnected or restricted networks, and security-compliance-driven settings." Also "Experience integrating with Maven Smart System, operational data repositories, simulation engines, or government interfaces of record." Also "Experience developing optimization or recommendation systems that present alternatives, constraints, and explainable rationale." Also "Experience supporting independent T&E, operational acceptance testing, and deployment of software into government production environments."
- Qualifications: maybe overlapping with requirements. Could combine but we need separate sections only if content. Could treat "Qualifications" as education? Not present. Might skip Qualifications if no distinct content.
- Skills: list of technical skills: "Strong experience with modern front-end frameworks, backend services, RESTful APIs, event-driven architectures, relational or document databases, and automated testing." Also "Experience building workflow, mission-planning, decision-support, command-and-control, or operational intelligence applications." Also "Ability to transform complex operational and doctrinal processes into usable, explainable software." Also "Experience with data provenance, audit logging, workflow state management, access controls, and configuration or model versioning." Also "Familiarity with containerized deployments, CI/CD pipelines, infrastructure-as-code, observability, and secure cloud or on-premises environments." Also "Demonstrated ability to collaborate with operational users and deliver incrementally through frequent demonstrations and feedback." Also "Understanding of human-centered design for high-consequence workflows where recommendations must remain transparent, reviewable, and reversible." Also "Excellent written and verbal communication skills, including the ability to explain technical decisions to operational and Government stakeholders."
- Benefits: The posting includes benefits: "Exceptional Medical/Dental/Vision Insurance, premiums for employees are 100% paid by Culmen, and dependent coverage is available at a nominal rate (including same or opposite sex domestic partners) 401k - Vested immediately and 4% match Life insurance and disability paid by the company Supplemental Insurance Available Opportunities for Training and Continuing Education 12 Paid Holidays". Also maybe "To learn more about Culmen International, please visit www.culmen.com" but that's not benefit. We'll include Benefits section with list.
- Pay: Not mentioned. No salary. So we should NOT include Pay section.
- Schedule: Not mentioned. No schedule. So omit.
We must not include placeholder text like "commensurate with experience". Not present.
We need to output only HTML fragment, no /. Use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which content goes in prose vs list. For About the role, we can use
. For Responsibilities, we can use
- . For Requirements, maybe
- . For Skills,
- . For Benefits,
- . Ensure we preserve all substantive info; we must not lose any detail.
Let's extract each piece precisely.
First, copy the posting text and parse.
I'll rewrite the posting content in my own words but must preserve info; we can keep same sentences.
Let's list paragraphs:
Paragraph 1: "Culmen International is seeking a Senior Full-Stack Engineer to support secure, mission-ready software development for USPACOM J32 targeting and mission-planning workflows. Must be located in the NCR and able to commute onsite to the Mark Center. As the Senior Full-Stack Engineer, you will design, develop, integrate, and field secure software applications that support targeting and mission-planning operations."
Paragraph 2: "This role requires full software development lifecycle expertise, including requirements analysis, architecture, testing, deployment, and sustainment in classified environments."
Paragraph 3: "Design, build, and field secure, mission-ready software supporting USPACOM J32 joint targeting and fires-planning workflows."
Paragraph 4: "Develop operator-facing applications for Target-Effect Pairing (TEP), including ranked recommendations, alternative pairings, constraint-driven tradeoffs, and explanations."
Paragraph 5: "Build backend services for workflow orchestration, recommendation processing, review and adjudication, approval routing, deconfliction, and draft force-assignment support."
Paragraph 6: "Translate Joint Fires and Targeting SME input into intuitive workflows supporting Phase 3 Capabilities Analysis and Phase 4 Commander’s Decision and Force Assignment."
Paragraph 7: "Implement human-machine teaming controls that allow authorized users to accept, reject, modify, and route recommendations while preserving human authority over inherently governmental decisions."
Paragraph 8: "Create traceable and auditable software that records source data, model or ruleset versions, recommendation history, user actions, timestamps, and approval rationale."
Paragraph 9: "Integrate with Government-designated systems—including Maven Smart System (MSS), object-management systems, simulation services, and command-and-control interfaces—through secure APIs and event-driven patterns."
Paragraph 10: "Build interfaces that clearly communicate inventory constraints, timing and availability limitations, assumptions, confidence indicators, infeasible conditions, and recommended next steps."
Paragraph 11: "Develop resilient services capable of supporting single-target, multi-target, and constrained-resource planning scenarios in connected and degraded operating conditions."
Paragraph 12: "Implement role-based and attribute-based access controls, classification-aware data handling, secure service communication, and tamper-evident audit capabilities."
Paragraph 13: "Create automated unit, integration, regression, performance, and security tests suitable for Government acceptance and independent test and evaluation."
Paragraph 14: "Partner directly with J32 operators, Joint Fires and Targeting SMEs, weaponeering experts, data engineers, security teams, and Government system owners."
Paragraph 15: "Participate in sprint planning, backlog refinement, operator demonstrations, technical reviews, and fielding activities in Government-designated environments."
Paragraph 16: "Produce maintainable code, API documentation, architecture decision records, release notes, runbooks, and transition materials supporting Government operation and sustainment."
Then after that, the qualifications/experience list:
Paragraph 17: "7+ years of professional full-stack software engineering experience, including delivery of complex, data-intensive applications."
Paragraph 18: "Strong experience with modern front-end frameworks, backend services, RESTful APIs, event-driven architectures, relational or document databases, and automated testing."
Paragraph 19: "Experience building workflow, mission-planning, decision-support, command-and-control, or operational intelligence applications."
Paragraph 20: "Ability to transform complex operational and doctrinal processes into usable, explainable software."
Paragraph 21: "Experience with data provenance, audit logging, workflow state management, access controls, and configuration or model versioning."
Paragraph 22: "Familiarity with containerized deployments, CI/CD pipelines, infrastructure-as-code, observability, and secure cloud or on-premises environments."
Paragraph 23: "Demonstrated ability to collaborate with operational users and deliver incrementally through frequent demonstrations and feedback."
Paragraph 24: "Understanding of human-centered design for high-consequence workflows where recommendations must remain transparent, reviewable, and reversible."
Paragraph 25: "Excellent written and verbal communication skills, including the ability to explain technical decisions to operational and Government stakeholders."
Paragraph 26: "Eligibility for TS/SCI; active clearance strongly preferred."
Paragraph 27: "Ability to support on-site engagement with USPACOM J32 operators as mission needs require."
Paragraph 28: "Experience with joint targeting, Joint Fires, weaponeering, target-effect pairing, force assignment, or course-of-action analysis."
Paragraph 29: "Experience working in DoD classified environments, disconnected or restricted networks, and security-compliance-driven settings."
Paragraph 30: "Experience integrating with Maven Smart System, operational data repositories, simulation engines, or government interfaces of record."
Paragraph 31: "Experience developing optimization or recommendation systems that present alternatives, constraints, and explainable rationale."
Paragraph 32: "Experience supporting independent T&E, operational acceptance testing, and deployment of software into government production environments."
Then company description:
Paragraph 33: "Culmen International is committed to enhancing international safety and security, strengthening homeland defense, advancing humanitarian missions, and optimizing government operations. With experience in over 150 countries, Culmen supports our clients to accomplish critical missions in challenging environments."
Then benefits list:
Paragraph 34: "Exceptional Medical/Dental/Vision Insurance, premiums for employees are 100% paid by Culmen, and dependent coverage is available at a nominal rate (including same or opposite sex domestic partners)"
Paragraph 35: "401k - Vested immediately and 4% match"
Paragraph 36: "Life insurance and disability paid by the company"
Paragraph 37: "Supplemental Insurance Available"
Paragraph 38: "Opportunities for Training and Continuing Education"
Paragraph 39: "12 Paid Holidays"
Then final boilerplate: "To learn more about Culmen International, please visit www.culmen.com" and EEO statement.
We need to exclude boilerplate: the To learn more line and EEO.
Now decide sections:
- About the role: Could combine first two paragraphs (role description and lifecycle). Might be better as a
summarizing.
But we must preserve all substantive info; we can put them as
sentences.
- Responsibilities: list of duties from paragraphs 3-16 (maybe also include some from earlier? Actually paragraphs 3-16 are responsibilities). We'll list each as
- .
- Requirements: maybe include eligibility, clearance, on-site engagement, experience with joint targeting, DoD classified environments, integration with Maven, optimization systems, T&E experience. Also maybe the 7+ years experience. That's a requirement.
- Skills: include technical skills paragraphs 18-25 (front-end frameworks, etc.) plus ability to transform processes, data provenance, etc., collaboration, human-centered design, communication skills.
- Benefits: list paragraphs 34-39.
We need to avoid duplication: Some items appear both in responsibilities and skills; but we must preserve all info, even if duplicated? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If something appears in both places, we should include it in both sections?
for prose. We need to decide which content goes in prose vs list. For About the role, we can use
. For Responsibilities, we can use
- . For Requirements, maybe
- . For Skills,
- . For Benefits,
- . Ensure we preserve all substantive info; we must not lose any detail.
Let's extract each piece precisely.
First, copy the posting text and parse.
I'll rewrite the posting content in my own words but must preserve info; we can keep same sentences.
Let's list paragraphs:
Paragraph 1: "Culmen International is seeking a Senior Full-Stack Engineer to support secure, mission-ready software development for USPACOM J32 targeting and mission-planning workflows. Must be located in the NCR and able to commute onsite to the Mark Center. As the Senior Full-Stack Engineer, you will design, develop, integrate, and field secure software applications that support targeting and mission-planning operations."
Paragraph 2: "This role requires full software development lifecycle expertise, including requirements analysis, architecture, testing, deployment, and sustainment in classified environments."
Paragraph 3: "Design, build, and field secure, mission-ready software supporting USPACOM J32 joint targeting and fires-planning workflows."
Paragraph 4: "Develop operator-facing applications for Target-Effect Pairing (TEP), including ranked recommendations, alternative pairings, constraint-driven tradeoffs, and explanations."
Paragraph 5: "Build backend services for workflow orchestration, recommendation processing, review and adjudication, approval routing, deconfliction, and draft force-assignment support."
Paragraph 6: "Translate Joint Fires and Targeting SME input into intuitive workflows supporting Phase 3 Capabilities Analysis and Phase 4 Commander’s Decision and Force Assignment."
Paragraph 7: "Implement human-machine teaming controls that allow authorized users to accept, reject, modify, and route recommendations while preserving human authority over inherently governmental decisions."
Paragraph 8: "Create traceable and auditable software that records source data, model or ruleset versions, recommendation history, user actions, timestamps, and approval rationale."
Paragraph 9: "Integrate with Government-designated systems—including Maven Smart System (MSS), object-management systems, simulation services, and command-and-control interfaces—through secure APIs and event-driven patterns."
Paragraph 10: "Build interfaces that clearly communicate inventory constraints, timing and availability limitations, assumptions, confidence indicators, infeasible conditions, and recommended next steps."
Paragraph 11: "Develop resilient services capable of supporting single-target, multi-target, and constrained-resource planning scenarios in connected and degraded operating conditions."
Paragraph 12: "Implement role-based and attribute-based access controls, classification-aware data handling, secure service communication, and tamper-evident audit capabilities."
Paragraph 13: "Create automated unit, integration, regression, performance, and security tests suitable for Government acceptance and independent test and evaluation."
Paragraph 14: "Partner directly with J32 operators, Joint Fires and Targeting SMEs, weaponeering experts, data engineers, security teams, and Government system owners."
Paragraph 15: "Participate in sprint planning, backlog refinement, operator demonstrations, technical reviews, and fielding activities in Government-designated environments."
Paragraph 16: "Produce maintainable code, API documentation, architecture decision records, release notes, runbooks, and transition materials supporting Government operation and sustainment."
Then after that, the qualifications/experience list:
Paragraph 17: "7+ years of professional full-stack software engineering experience, including delivery of complex, data-intensive applications."
Paragraph 18: "Strong experience with modern front-end frameworks, backend services, RESTful APIs, event-driven architectures, relational or document databases, and automated testing."
Paragraph 19: "Experience building workflow, mission-planning, decision-support, command-and-control, or operational intelligence applications."
Paragraph 20: "Ability to transform complex operational and doctrinal processes into usable, explainable software."
Paragraph 21: "Experience with data provenance, audit logging, workflow state management, access controls, and configuration or model versioning."
Paragraph 22: "Familiarity with containerized deployments, CI/CD pipelines, infrastructure-as-code, observability, and secure cloud or on-premises environments."
Paragraph 23: "Demonstrated ability to collaborate with operational users and deliver incrementally through frequent demonstrations and feedback."
Paragraph 24: "Understanding of human-centered design for high-consequence workflows where recommendations must remain transparent, reviewable, and reversible."
Paragraph 25: "Excellent written and verbal communication skills, including the ability to explain technical decisions to operational and Government stakeholders."
Paragraph 26: "Eligibility for TS/SCI; active clearance strongly preferred."
Paragraph 27: "Ability to support on-site engagement with USPACOM J32 operators as mission needs require."
Paragraph 28: "Experience with joint targeting, Joint Fires, weaponeering, target-effect pairing, force assignment, or course-of-action analysis."
Paragraph 29: "Experience working in DoD classified environments, disconnected or restricted networks, and security-compliance-driven settings."
Paragraph 30: "Experience integrating with Maven Smart System, operational data repositories, simulation engines, or government interfaces of record."
Paragraph 31: "Experience developing optimization or recommendation systems that present alternatives, constraints, and explainable rationale."
Paragraph 32: "Experience supporting independent T&E, operational acceptance testing, and deployment of software into government production environments."
Then company description:
Paragraph 33: "Culmen International is committed to enhancing international safety and security, strengthening homeland defense, advancing humanitarian missions, and optimizing government operations. With experience in over 150 countries, Culmen supports our clients to accomplish critical missions in challenging environments."
Then benefits list:
Paragraph 34: "Exceptional Medical/Dental/Vision Insurance, premiums for employees are 100% paid by Culmen, and dependent coverage is available at a nominal rate (including same or opposite sex domestic partners)"
Paragraph 35: "401k - Vested immediately and 4% match"
Paragraph 36: "Life insurance and disability paid by the company"
Paragraph 37: "Supplemental Insurance Available"
Paragraph 38: "Opportunities for Training and Continuing Education"
Paragraph 39: "12 Paid Holidays"
Then final boilerplate: "To learn more about Culmen International, please visit www.culmen.com" and EEO statement.
We need to exclude boilerplate: the To learn more line and EEO.
Now decide sections:
- About the role: Could combine first two paragraphs (role description and lifecycle). Might be better as a
summarizing. But we must preserve all substantive info; we can put them as
sentences. - Responsibilities: list of duties from paragraphs 3-16 (maybe also include some from earlier? Actually paragraphs 3-16 are responsibilities). We'll list each as
- . - Requirements: maybe include eligibility, clearance, on-site engagement, experience with joint targeting, DoD classified environments, integration with Maven, optimization systems, T&E experience. Also maybe the 7+ years experience. That's a requirement. - Skills: include technical skills paragraphs 18-25 (front-end frameworks, etc.) plus ability to transform processes, data provenance, etc., collaboration, human-centered design, communication skills. - Benefits: list paragraphs 34-39. We need to avoid duplication: Some items appear both in responsibilities and skills; but we must preserve all info, even if duplicated? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If something appears in both places, we should include it in both sections?
- . Ensure we preserve all substantive info; we must not lose any detail.
Let's extract each piece precisely.
First, copy the posting text and parse.
I'll rewrite the posting content in my own words but must preserve info; we can keep same sentences.
Let's list paragraphs:
Paragraph 1: "Culmen International is seeking a Senior Full-Stack Engineer to support secure, mission-ready software development for USPACOM J32 targeting and mission-planning workflows. Must be located in the NCR and able to commute onsite to the Mark Center. As the Senior Full-Stack Engineer, you will design, develop, integrate, and field secure software applications that support targeting and mission-planning operations."
Paragraph 2: "This role requires full software development lifecycle expertise, including requirements analysis, architecture, testing, deployment, and sustainment in classified environments."
Paragraph 3: "Design, build, and field secure, mission-ready software supporting USPACOM J32 joint targeting and fires-planning workflows."
Paragraph 4: "Develop operator-facing applications for Target-Effect Pairing (TEP), including ranked recommendations, alternative pairings, constraint-driven tradeoffs, and explanations."
Paragraph 5: "Build backend services for workflow orchestration, recommendation processing, review and adjudication, approval routing, deconfliction, and draft force-assignment support."
Paragraph 6: "Translate Joint Fires and Targeting SME input into intuitive workflows supporting Phase 3 Capabilities Analysis and Phase 4 Commander’s Decision and Force Assignment."
Paragraph 7: "Implement human-machine teaming controls that allow authorized users to accept, reject, modify, and route recommendations while preserving human authority over inherently governmental decisions."
Paragraph 8: "Create traceable and auditable software that records source data, model or ruleset versions, recommendation history, user actions, timestamps, and approval rationale."
Paragraph 9: "Integrate with Government-designated systems—including Maven Smart System (MSS), object-management systems, simulation services, and command-and-control interfaces—through secure APIs and event-driven patterns."
Paragraph 10: "Build interfaces that clearly communicate inventory constraints, timing and availability limitations, assumptions, confidence indicators, infeasible conditions, and recommended next steps."
Paragraph 11: "Develop resilient services capable of supporting single-target, multi-target, and constrained-resource planning scenarios in connected and degraded operating conditions."
Paragraph 12: "Implement role-based and attribute-based access controls, classification-aware data handling, secure service communication, and tamper-evident audit capabilities."
Paragraph 13: "Create automated unit, integration, regression, performance, and security tests suitable for Government acceptance and independent test and evaluation."
Paragraph 14: "Partner directly with J32 operators, Joint Fires and Targeting SMEs, weaponeering experts, data engineers, security teams, and Government system owners."
Paragraph 15: "Participate in sprint planning, backlog refinement, operator demonstrations, technical reviews, and fielding activities in Government-designated environments."
Paragraph 16: "Produce maintainable code, API documentation, architecture decision records, release notes, runbooks, and transition materials supporting Government operation and sustainment."
Then after that, the qualifications/experience list:
Paragraph 17: "7+ years of professional full-stack software engineering experience, including delivery of complex, data-intensive applications."
Paragraph 18: "Strong experience with modern front-end frameworks, backend services, RESTful APIs, event-driven architectures, relational or document databases, and automated testing."
Paragraph 19: "Experience building workflow, mission-planning, decision-support, command-and-control, or operational intelligence applications."
Paragraph 20: "Ability to transform complex operational and doctrinal processes into usable, explainable software."
Paragraph 21: "Experience with data provenance, audit logging, workflow state management, access controls, and configuration or model versioning."
Paragraph 22: "Familiarity with containerized deployments, CI/CD pipelines, infrastructure-as-code, observability, and secure cloud or on-premises environments."
Paragraph 23: "Demonstrated ability to collaborate with operational users and deliver incrementally through frequent demonstrations and feedback."
Paragraph 24: "Understanding of human-centered design for high-consequence workflows where recommendations must remain transparent, reviewable, and reversible."
Paragraph 25: "Excellent written and verbal communication skills, including the ability to explain technical decisions to operational and Government stakeholders."
Paragraph 26: "Eligibility for TS/SCI; active clearance strongly preferred."
Paragraph 27: "Ability to support on-site engagement with USPACOM J32 operators as mission needs require."
Paragraph 28: "Experience with joint targeting, Joint Fires, weaponeering, target-effect pairing, force assignment, or course-of-action analysis."
Paragraph 29: "Experience working in DoD classified environments, disconnected or restricted networks, and security-compliance-driven settings."
Paragraph 30: "Experience integrating with Maven Smart System, operational data repositories, simulation engines, or government interfaces of record."
Paragraph 31: "Experience developing optimization or recommendation systems that present alternatives, constraints, and explainable rationale."
Paragraph 32: "Experience supporting independent T&E, operational acceptance testing, and deployment of software into government production environments."
Then company description:
Paragraph 33: "Culmen International is committed to enhancing international safety and security, strengthening homeland defense, advancing humanitarian missions, and optimizing government operations. With experience in over 150 countries, Culmen supports our clients to accomplish critical missions in challenging environments."
Then benefits list:
Paragraph 34: "Exceptional Medical/Dental/Vision Insurance, premiums for employees are 100% paid by Culmen, and dependent coverage is available at a nominal rate (including same or opposite sex domestic partners)"
Paragraph 35: "401k - Vested immediately and 4% match"
Paragraph 36: "Life insurance and disability paid by the company"
Paragraph 37: "Supplemental Insurance Available"
Paragraph 38: "Opportunities for Training and Continuing Education"
Paragraph 39: "12 Paid Holidays"
Then final boilerplate: "To learn more about Culmen International, please visit www.culmen.com" and EEO statement.
We need to exclude boilerplate: the To learn more line and EEO.
Now decide sections:
- About the role: Could combine first two paragraphs (role description and lifecycle). Might be better as a
- . For Benefits,
- . For Skills,