Mission Engineer - Enterprise Architecture

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, we need to remove boilerplate: "Skip to content Home Learn MoreHelp You are viewing a preview of this job. Log in or register to view more details about this job." Also "Mission Engineer - Enterprise Architecture Space Dynamics Laboratory Email Job ID: 9550 Date Posted: September 24, 2026" - we should not repeat job title as heading, and not put Job ID/requisition numbers as headings; fold minor metadata into a short

or drop it. So we can include a short paragraph with Job ID and date maybe. Then the description: "Space Dynamics Laboratory’s (SDL) Strategic & Military Space Division is seeking applicants for a Mission Engineer with a background in DoW Classified Enterprise Architectures and national security space systems to serve as an embedded subject matter expert (SME) in the U.S. Space Force System Delta 81 (SYD 81) and Operational Test & Training Infrastructure (OTTI). The successful applicant will be responsible for assisting SYD 81 and the OTTI to develop national level capabilities to test the USA’s next generation of space capabilities, and develop tactics, techniques, and procedures for the service’s weapons systems. The Strategic & Military Space Division delivers advanced satellite and sensor systems that support the Department of Defense and the Intelligence Community. Our division is a key component of national security, providing technological solutions and expert mission support. Become part of a team dedicated to making a tangible contribution to our nation’s defense capabilities." That's about the role. Could be "About the role" section. Then "Key Responsibilities" list bullet points. Then "Required Qualifications" list bullet points. Then "Preferred Qualifications" list bullet points. Then "Salary Range $115,000 - $220,000 Salary commensurate on education and relevant experience ..." This is pay info. We need a Pay section only if posting actually states them. It does state salary range. So we include Pay section with that info (maybe as

). We should not include filler like "commensurate with experience" as heading; but we can include the text. Then "Why Join SDL?" includes benefits and culture. Could be Benefits section. It mentions "SDL offers competitive salaries and a comprehensive benefits package. Visit our Benefits Page to learn more about what we offer." Also description of SDL mission, culture. That's benefits-ish. We'll treat as Benefits section. Schedule: Not mentioned. So we omit Schedule section. Skills: Could be derived from qualifications but we have separate Required and Preferred Qualifications. The instruction says use headings like Skills, Benefits, Pay, Schedule. We have Required Qualifications and Preferred Qualifications; maybe we combine them into Requirements and Qualifications? The headings list includes Requirements, Qualifications, Skills. We need to decide which to use. The posting has "Required Qualifications" and "Preferred Qualifications". Could map Required Qualifications to Requirements section, Preferred Qualifications to Qualifications section (or Skills). But we also have Skills heading; maybe we can put technical skills under Skills. However we must not create thin sections. Better to use Requirements for required qualifications, Qualifications for preferred qualifications, and maybe Skills for specific technical skills (like audio-visual, etc.) but that might be redundant. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Required and Preferred Qualifications into one Qualifications section, but we need to preserve all info. Could have a Qualifications section with subheadings? Not allowed; only headings are h3. Could use

to differentiate. But we need to follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which headings to include based on content. We have content for About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Pay, Benefits (Why Join SDL?). That's six sections. Could map Required Qualifications to Requirements, Preferred Qualifications to Qualifications, and maybe Skills not needed. Or we could combine both into Qualifications and omit Requirements. But we need to preserve all info; we can include both Required and Preferred under Qualifications heading with paragraphs distinguishing. That would be one section. But we also have Responsibilities section. Thus sections: About the role, Responsibilities, Qualifications (including required and preferred), Pay, Benefits. We should not include Skills if no specific skills list separate; but we could extract skills from qualifications but that would be thin. Better to omit Skills. Schedule omitted. Now we need to output HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information. Let's extract content. About the role: The paragraph(s) describing the role: "Space Dynamics Laboratory’s (SDL) Strategic & Military Space Division is seeking applicants for a Mission Engineer with a background in DoW Classified Enterprise Architectures and national security space systems to serve as an embedded subject matter expert (SME) in the U.S. Space Force System Delta 81 (SYD 81) and Operational Test & Training Infrastructure (OTTI). The successful applicant will be responsible for assisting SYD 81 and the OTTI to develop national level capabilities to test the USA’s next generation of space capabilities, and develop tactics, techniques, and procedures for the service’s weapons systems. The Strategic & Military Space Division delivers advanced satellite and sensor systems that support the Department of Defense and the Intelligence Community. Our division is a key component of national security, providing technological solutions and expert mission support. Become part of a team dedicated to making a tangible contribution to our nation’s defense capabilities." We can keep as one

  . Responsibilities: The list under "Key Responsibilities". Items: - Develops enterprise architectures using structured systems engineering and mission engineering principles - Translates complex operational mission requirements into scalable, resilient test and training infrastructure designs - Leads end-to-end enterprise engineering initiatives to modernize United States Space Force (USSF) technical capabilities - Delivers technical subject matter expertise directly to embedded customer leadership to guide long-term infrastructure strategy - Designs audio visual systems including video conferencing, audio, video, control, and networking components - Conducts site surveys, specify equipment, and create system design drawings and documentation - Develops system functionality, signal flow, and performance requirements - Conducts mission threads analysis to identify capability gaps, dependencies, and integration risks across the enterprise - Authors comprehensive technical baselines, engineering products, interface control documents, and architectural frameworks - Establishes engineering governance frameworks that align multi-domain test and training environments with evolving space domain directives - Synthesizes disparate technical inputs from multiple stakeholders into unified, actionable engineering roadmaps We need to output as

  • each. Qualifications: Combine required and preferred. Required Qualifications list: - Active Top Secret/Sensitive Compartmented Information (TS/SCI) clearance - Bachelor of science degree in systems engineering, information technology, computer science, or a related technical discipline - Minimum of 10 years of experience executing enterprise-level systems engineering within DoD or aerospace sectors - Demonstrated technical understanding of USSF classified networks and IT mission systems across both on-premises and cloud architectures - Strong understanding of audio-visual technologies, digital signal processing, control systems, routing, and audio/video signal flow - Experience with developing audio-visual system functionality, signal flow, and performance requirements - Strong technical communication capability with a history of presenting complex concepts and delivering architectural products to executive military leadership - Ability to work full-time on-site embedded within a secure customer facility - Applied understanding of security principles, data protection, and compliance requirements for secure architecture design. Preferred Qualifications list: - Master of science degree in systems engineering, mission engineering, or computer science - IT, cybersecurity, or data related professional certifications - Direct operational experience with USSF Space Training and Readiness Command (STARCOM) or Space Systems Command (SSC) infrastructure and programs - Advanced technical knowledge of Cloud Architecture (AWS GovCloud), DevSecOps pipelines, and secure cross-domain solutions - Experience in building and optimizing data architecture that significantly reduces processing times for analytics and business intelligence reporting - Proficiency with architecture development frameworks (DoDAF, UAF, MBSE, Cameo), including defining "as-is" and "to-be" environments across administrative, data, and technology domains - Experience applying Agile systems engineering frameworks to multi-year, complex defense acquisition portfolios We need to output as
    • each. Could separate required and preferred with a

      indicating "Required Qualifications:" and "Preferred Qualifications:" but we cannot add extra headings; we can include

      inside the section. Pay: The salary range text: "Salary Range $115,000 - $220,000 Salary commensurate on education and relevant experience This range serves as a general guideline and may vary based on factors such as role, level, location, market conditions, and individual qualifications, including job-related skills, experience, and relevant education or training. The range displayed in the job advertisement reflects the minimum and maximum target salaries across all US locations. Specific salary details for a candidate’s preferred location can be provided by the recruiter or HR manager during the hiring process." We should include that as

      under Pay section. Benefits: The "Why Join SDL?" paragraph(s): - "SDL offers competitive salaries and a comprehensive benefits package. Visit our Benefits Page to learn more about what we offer." - "SDL delivers advanced multi-domain solutions to protect national security and enable scientific discovery. Our expertise in satellites, sensors and instruments, ground systems and data processing, and autonomous systems plays a critical role in missions supporting NASA and the Department of Defense." - "Join our team of engineers, scientists, technicians, and business professionals in our seventh decade of delivering mission success." - "At SDL, we strive to uphold a culture of respect, collaboration, empowerment, and accountability. We listen with open minds, seek to understand diverse perspectives, and engage in thoughtful dialogue. We work together by sharing knowledge, involving others, and offering support. We trust and empower our team members to take ownership, act with integrity, and be accountable. Above all, we deliver on our commitments to each other and to our mission partners." - Also maybe the application window text: "The application window for this position is expected to remain open for approximately 7 days; however, it may be shortened or extended depending on business needs and the availability of qualified candidates. We encourage interested candidates to submit their applications promptly." This is application instructions, which we should remove per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we drop that. Thus Benefits section includes the first four paragraphs (maybe combine into one or multiple

      ). We should not include the "Visit our Benefits Page to learn more about what we offer." as a link? It's just text; we keep. Now we need to include minor metadata like Job ID and date posted folded into a short

      or drop it. Probably include a short

      at top: "Job ID: 9550 • Posted: September 24, 2026". That's okay. Now output HTML fragment: no or , just the elements. Let's construct:

      Job ID: 9550 • Posted: September 24, 2026

      About the role

      Space Dynamics Laboratory’s (SDL) Strategic & Military Space Division is seeking applicants for a Mission Engineer with a background in DoW Classified Enterprise Architectures and national security space systems to serve as an embedded subject matter expert (SME) in the U.S. Space Force System Delta 81 (SYD 81) and Operational Test & Training Infrastructure (OTTI). The successful applicant will be responsible for assisting SYD 81