Sr. Systems Engineer (8-12 yrs)
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate: EEO etc. Also remove navigation, cookie, legal, etc. Must preserve all substantive info. Include sections only when posting has real specific content. The posting includes sections: About The Role (we can map to "About the role" heading). Then "What You'll Actually Do" is responsibilities. Then "Who Thrives Here" includes requirements/qualifications/skills. Then "Bonus Points If You Have Experience With ..." maybe skills. Then "Success is Measured By" maybe metrics but could be responsibilities? Might be considered responsibilities or performance metrics. Then "Why Join Advanced Space" maybe benefits? Actually benefits are in "Compensation & Benefits". So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to extract content accordingly.
Let's parse:
About The Role: paragraph(s) describing role. We'll put under
About the role
with content.
Responsibilities: "What You'll Actually Do" bullet list of duties. We'll put under
Responsibilities
with - each bullet.
Requirements: maybe "Who Thrives Here" includes experience, education, etc. Could be split into Requirements and Qualifications. The posting says: "Who Thrives Here You have 8–12 years of progressively responsible systems engineering experience supporting spaceflight or other complex aerospace systems. You have a B.S., M.S., or Ph.D. in Aerospace Engineering, Systems Engineering, or a related technical field; equivalent relevant experience may be considered. You have demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation. You have experience leading technical reviews, trade studies, integration and test activities, and multidisciplinary engineering teams. You have supported complex aerospace or other safety-critical systems across multiple lifecycle phases, including system development, integration and test, operations, or related system-level activities. You have strong technical judgment and excellent written and verbal communication skills. You're comfortable engaging directly with customers, mission partners, and technical stakeholders. You can provide technical leadership while collaborating effectively across multidisciplinary engineering teams. You're adaptable, proactive, and mission-focused in dynamic technical environments. You take ownership. When you see a challenge, you work with the team to solve it. You have the ability to obtain an active U.S. Government Top Secret security clearance. You're able to work in the Westminster, Colorado office five days per week during core business hours."
That's a mix of requirements, qualifications, skills. We need separate sections: Requirements, Qualifications, Skills. We'll need to decide what goes where. Typically Requirements: experience, education, clearance, location. Qualifications: maybe degrees, experience. Skills: technical skills like MBSE, programming, etc. The "Bonus Points If You Have Experience With ..." list is clearly skills/bonus.
Thus:
Requirements: maybe the core mandatory items: 8-12 years experience, B.S./M.S./Ph.D. in Aerospace Engineering, Systems Engineering, or related; ability to obtain Top Secret clearance; ability to work Westminster CO office five days per week; U.S. Person (citizenship) etc. Also "You have demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation." That could be a requirement. Also "You have experience leading technical reviews, trade studies, integration and test activities, and multidisciplinary engineering teams." Also "You have supported complex aerospace or other safety-critical systems across multiple lifecycle phases..." Also "You have strong technical judgment and excellent written and verbal communication skills." Also "You're comfortable engaging directly with customers, mission partners, and technical stakeholders." Also "You can provide technical leadership while collaborating effectively across multidisciplinary engineering teams." Also "You're adaptable, proactive, and mission-focused in dynamic technical environments." Also "You take ownership." These are more like qualifications/skills.
Qualifications: maybe education and experience. But we have overlapping.
Given instruction: Prefer a few substantive sections over many thin ones. But we must include sections only when posting has real specific content. We could combine some: maybe Requirements (experience, education, clearance, location, citizenship). Qualifications (demonstrated experience with system architecture, ConOps, etc.) Skills (technical skills like MBSE, programming, etc.) Benefits (compensation & benefits). Pay (base salary, signing bonus, quarterly bonuses). Schedule (Hybrid work with at least three days per week in person). Also maybe "About Advanced Space" could be part of About the role? Already have About the role.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Let's extract:
About the role: The paragraph(s) under "About The Role". We'll combine into one
.
Responsibilities: The bullet list under "What You'll Actually Do". Each line starts with a bold phrase? We'll extract each sentence as list item.
Let's list them:
- Lead mission and system architecture development.
- Lead the development of mission concepts, ConOps, system architectures, and technical baselines.
- Translate mission objectives and stakeholder needs into practical system-level solutions that balance performance, cost, schedule, risk, operability, and mission assurance.
- Develop And Manage System Requirements.
- Translate customer and stakeholder needs into measurable system requirements.
- Lead requirements allocation, traceability, verification, and validation while ensuring requirements remain aligned with mission objectives and overall system performance.
- Lead system-level trade studies and technical decisions.
- Evaluate system-level design options and lead technical trade studies across spacecraft, ground systems, flight software, mission operations, and relevant subsystem disciplines.
- Use sound technical judgment to drive decisions and manage impacts to performance, cost, schedule, risk, and mission success.
- Manage system interfaces and integration.
- Define and manage internal and external system interfaces, including Interface Control Documents (ICDs).
- Provide technical oversight of system integration and ensure interfaces are effectively coordinated across multidisciplinary engineering teams and mission partners.
- Lead verification, validation, and test activities.
- Plan and guide integration, verification, validation, test, and operational-readiness activities.
- Lead or support major technical reviews, including System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), and operational-readiness reviews.
- Provide technical leadership across the mission lifecycle.
- Provide system-level technical oversight from early mission design through development, integration and test, launch, commissioning, and operations.
- Work across spacecraft, ground systems, flight software, mission operations, and subsystem teams to ensure the overall system remains aligned and mission-ready.
- Partner directly with customers and mission teams.
- Work directly with customers and mission partners throughout the mission lifecycle.
- Communicate complex technical concepts clearly, support technical decision-making, and help ensure customer needs are translated into successful system solutions.
- Manage technical risks and system performance.
- Identify and manage technical risks, system margins, technical performance measures, and engineering-change impacts.
- Support risk management and technical assessments to ensure mission objectives remain achievable throughout development and operations.
- Support mission operations and future missions.
- Contribute to mission operations activities, including contingency planning, anomaly resolution, and system evolution.
- Support early-phase mission studies, proposals, and the development of future mission concepts and architectures.
- Mentor and develop engineers.
- Provide technical guidance and mentorship to junior engineers.
- Share systems engineering knowledge, encourage strong technical practices, and help develop the next generation of engineers at Advanced Space.
That's many items; we can keep as list.
Requirements: Let's extract mandatory items:
- 8–12 years of progressively responsible systems engineering experience supporting spaceflight or other complex aerospace systems.
- B.S., M.S., or Ph.D. in Aerospace Engineering, Systems Engineering, or a related technical field; equivalent relevant experience may be considered.
- Ability to obtain an active U.S. Government Top Secret security clearance (preferred? Actually says "You have the ability to obtain an active U.S. Government Top Secret security clearance." It's a requirement? It's listed under Who Thrives Here, maybe required. We'll include as requirement.
- Must be a U.S. Person (U.S. citizens, lawful permanent residents, or other protected individuals) only; visa sponsorship not available; candidates must be authorized to work in the U.S. without need for current or future sponsorship. (From earlier About The Role section.)
- Able to work in the Westminster, Colorado office five days per week during core business hours.
Also maybe "You have demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation." Could be requirement but we might put under Qualifications.
Qualifications: Could be the demonstrated experience items:
- Demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation.
- Experience leading technical reviews, trade studies, integration and test activities, and multidisciplinary engineering teams.
- Supported complex aerospace or other safety-critical systems across multiple lifecycle phases, including system development, integration and test, operations, or related system-level activities.
- Strong technical judgment and excellent written and verbal communication skills.
- Comfortable engaging directly with customers, mission partners, and technical stakeholders.
- Able to provide technical leadership while collaborating effectively across multidisciplinary engineering teams.
- Adaptable, proactive, and mission-focused in dynamic technical environments.
- Takes ownership; works with team to solve challenges.
Skills: Bonus points list:
- Experience With Model-Based Systems Engineering (MBSE), particularly Cameo
- Python or another programming/scripting language
- Requirements or configuration-management tools such as Jama
- Spacecraft communications
- Mission design or spacecraft navigation
- Spacecraft or ground systems
- Flight software or mission operations
- Launch and commissioning activities
- Earth-orbit, cislunar, or deep-space missions
- NASA systems-engineering practices
- DoD space programs or comparable government-customer environments
- Proposals and early-phase mission studies
Benefits: From "Compensation & Benefits" section:
- Base Salary: $134K–$174K (based on experience, qualifications, and location)
- Signing bonus
- Quarterly performance bonuses
- Company-sponsored medical benefits and 401(k)
- Unlimited vacation time and extensive flexibility
- Relocation assistance
- Hybrid work with at least three days per week in person
Pay: Base salary, signing bonus, quarterly performance bonuses.
Schedule: Hybrid work with at least three days per week in person (maybe also mention five days per week in office? Actually earlier said "You're able to work in the Westminster, Colorado office five days per week during core business hours." That's a requirement. But schedule: hybrid work with at least three days per week in person. We'll put schedule section.
We need to avoid duplication: Benefits already includes hybrid work; schedule could be just that. But we can still have schedule section with that detail.
We must not repeat job title heading. Use
for each section.
We must not include boilerplate like EEO etc. Remove that.
Now produce HTML fragment.
Let's craft:
About the role
At Advanced Space, we're enabling humanity's return to the Moon and building the technologies that will take us to Mars and beyond. We're looking for a Senior Systems Engineer with 8–12 years of experience to lead mission-critical systems engineering efforts across the full lifecycle of space systems—from concept to orbit and beyond. In this role, you'll lead the development of mission concepts, ConOps, system architectures, technical baselines, requirements, interfaces, and verification strategies. You'll provide system-level technical leadership across spacecraft, ground systems, flight software, mission operations, and relevant subsystem disciplines while working directly with customers and mission partners throughout the mission lifecycle. You'll have the opportunity to support complex aerospace and spaceflight programs across multiple lifecycle phases, including system development,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate: EEO etc. Also remove navigation, cookie, legal, etc. Must preserve all substantive info. Include sections only when posting has real specific content. The posting includes sections: About The Role (we can map to "About the role" heading). Then "What You'll Actually Do" is responsibilities. Then "Who Thrives Here" includes requirements/qualifications/skills. Then "Bonus Points If You Have Experience With ..." maybe skills. Then "Success is Measured By" maybe metrics but could be responsibilities? Might be considered responsibilities or performance metrics. Then "Why Join Advanced Space" maybe benefits? Actually benefits are in "Compensation & Benefits". So we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content accordingly. Let's parse: About The Role: paragraph(s) describing role. We'll put under
About the role
withcontent. Responsibilities: "What You'll Actually Do" bullet list of duties. We'll put under
Responsibilities
with- each bullet.
Requirements: maybe "Who Thrives Here" includes experience, education, etc. Could be split into Requirements and Qualifications. The posting says: "Who Thrives Here You have 8–12 years of progressively responsible systems engineering experience supporting spaceflight or other complex aerospace systems. You have a B.S., M.S., or Ph.D. in Aerospace Engineering, Systems Engineering, or a related technical field; equivalent relevant experience may be considered. You have demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation. You have experience leading technical reviews, trade studies, integration and test activities, and multidisciplinary engineering teams. You have supported complex aerospace or other safety-critical systems across multiple lifecycle phases, including system development, integration and test, operations, or related system-level activities. You have strong technical judgment and excellent written and verbal communication skills. You're comfortable engaging directly with customers, mission partners, and technical stakeholders. You can provide technical leadership while collaborating effectively across multidisciplinary engineering teams. You're adaptable, proactive, and mission-focused in dynamic technical environments. You take ownership. When you see a challenge, you work with the team to solve it. You have the ability to obtain an active U.S. Government Top Secret security clearance. You're able to work in the Westminster, Colorado office five days per week during core business hours."
That's a mix of requirements, qualifications, skills. We need separate sections: Requirements, Qualifications, Skills. We'll need to decide what goes where. Typically Requirements: experience, education, clearance, location. Qualifications: maybe degrees, experience. Skills: technical skills like MBSE, programming, etc. The "Bonus Points If You Have Experience With ..." list is clearly skills/bonus.
Thus:
Requirements: maybe the core mandatory items: 8-12 years experience, B.S./M.S./Ph.D. in Aerospace Engineering, Systems Engineering, or related; ability to obtain Top Secret clearance; ability to work Westminster CO office five days per week; U.S. Person (citizenship) etc. Also "You have demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation." That could be a requirement. Also "You have experience leading technical reviews, trade studies, integration and test activities, and multidisciplinary engineering teams." Also "You have supported complex aerospace or other safety-critical systems across multiple lifecycle phases..." Also "You have strong technical judgment and excellent written and verbal communication skills." Also "You're comfortable engaging directly with customers, mission partners, and technical stakeholders." Also "You can provide technical leadership while collaborating effectively across multidisciplinary engineering teams." Also "You're adaptable, proactive, and mission-focused in dynamic technical environments." Also "You take ownership." These are more like qualifications/skills.
Qualifications: maybe education and experience. But we have overlapping.
Given instruction: Prefer a few substantive sections over many thin ones. But we must include sections only when posting has real specific content. We could combine some: maybe Requirements (experience, education, clearance, location, citizenship). Qualifications (demonstrated experience with system architecture, ConOps, etc.) Skills (technical skills like MBSE, programming, etc.) Benefits (compensation & benefits). Pay (base salary, signing bonus, quarterly bonuses). Schedule (Hybrid work with at least three days per week in person). Also maybe "About Advanced Space" could be part of About the role? Already have About the role.
We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content.
Let's extract:
About the role: The paragraph(s) under "About The Role". We'll combine into one
. Responsibilities: The bullet list under "What You'll Actually Do". Each line starts with a bold phrase? We'll extract each sentence as list item. Let's list them: - Lead mission and system architecture development. - Lead the development of mission concepts, ConOps, system architectures, and technical baselines. - Translate mission objectives and stakeholder needs into practical system-level solutions that balance performance, cost, schedule, risk, operability, and mission assurance. - Develop And Manage System Requirements. - Translate customer and stakeholder needs into measurable system requirements. - Lead requirements allocation, traceability, verification, and validation while ensuring requirements remain aligned with mission objectives and overall system performance. - Lead system-level trade studies and technical decisions. - Evaluate system-level design options and lead technical trade studies across spacecraft, ground systems, flight software, mission operations, and relevant subsystem disciplines. - Use sound technical judgment to drive decisions and manage impacts to performance, cost, schedule, risk, and mission success. - Manage system interfaces and integration. - Define and manage internal and external system interfaces, including Interface Control Documents (ICDs). - Provide technical oversight of system integration and ensure interfaces are effectively coordinated across multidisciplinary engineering teams and mission partners. - Lead verification, validation, and test activities. - Plan and guide integration, verification, validation, test, and operational-readiness activities. - Lead or support major technical reviews, including System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Test Readiness Review (TRR), and operational-readiness reviews. - Provide technical leadership across the mission lifecycle. - Provide system-level technical oversight from early mission design through development, integration and test, launch, commissioning, and operations. - Work across spacecraft, ground systems, flight software, mission operations, and subsystem teams to ensure the overall system remains aligned and mission-ready. - Partner directly with customers and mission teams. - Work directly with customers and mission partners throughout the mission lifecycle. - Communicate complex technical concepts clearly, support technical decision-making, and help ensure customer needs are translated into successful system solutions. - Manage technical risks and system performance. - Identify and manage technical risks, system margins, technical performance measures, and engineering-change impacts. - Support risk management and technical assessments to ensure mission objectives remain achievable throughout development and operations. - Support mission operations and future missions. - Contribute to mission operations activities, including contingency planning, anomaly resolution, and system evolution. - Support early-phase mission studies, proposals, and the development of future mission concepts and architectures. - Mentor and develop engineers. - Provide technical guidance and mentorship to junior engineers. - Share systems engineering knowledge, encourage strong technical practices, and help develop the next generation of engineers at Advanced Space. That's many items; we can keep as list. Requirements: Let's extract mandatory items: - 8–12 years of progressively responsible systems engineering experience supporting spaceflight or other complex aerospace systems. - B.S., M.S., or Ph.D. in Aerospace Engineering, Systems Engineering, or a related technical field; equivalent relevant experience may be considered. - Ability to obtain an active U.S. Government Top Secret security clearance (preferred? Actually says "You have the ability to obtain an active U.S. Government Top Secret security clearance." It's a requirement? It's listed under Who Thrives Here, maybe required. We'll include as requirement. - Must be a U.S. Person (U.S. citizens, lawful permanent residents, or other protected individuals) only; visa sponsorship not available; candidates must be authorized to work in the U.S. without need for current or future sponsorship. (From earlier About The Role section.) - Able to work in the Westminster, Colorado office five days per week during core business hours. Also maybe "You have demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation." Could be requirement but we might put under Qualifications. Qualifications: Could be the demonstrated experience items: - Demonstrated experience with system architecture, ConOps, requirements development and traceability, interface management, and verification and validation. - Experience leading technical reviews, trade studies, integration and test activities, and multidisciplinary engineering teams. - Supported complex aerospace or other safety-critical systems across multiple lifecycle phases, including system development, integration and test, operations, or related system-level activities. - Strong technical judgment and excellent written and verbal communication skills. - Comfortable engaging directly with customers, mission partners, and technical stakeholders. - Able to provide technical leadership while collaborating effectively across multidisciplinary engineering teams. - Adaptable, proactive, and mission-focused in dynamic technical environments. - Takes ownership; works with team to solve challenges. Skills: Bonus points list: - Experience With Model-Based Systems Engineering (MBSE), particularly Cameo - Python or another programming/scripting language - Requirements or configuration-management tools such as Jama - Spacecraft communications - Mission design or spacecraft navigation - Spacecraft or ground systems - Flight software or mission operations - Launch and commissioning activities - Earth-orbit, cislunar, or deep-space missions - NASA systems-engineering practices - DoD space programs or comparable government-customer environments - Proposals and early-phase mission studies Benefits: From "Compensation & Benefits" section: - Base Salary: $134K–$174K (based on experience, qualifications, and location) - Signing bonus - Quarterly performance bonuses - Company-sponsored medical benefits and 401(k) - Unlimited vacation time and extensive flexibility - Relocation assistance - Hybrid work with at least three days per week in person Pay: Base salary, signing bonus, quarterly performance bonuses. Schedule: Hybrid work with at least three days per week in person (maybe also mention five days per week in office? Actually earlier said "You're able to work in the Westminster, Colorado office five days per week during core business hours." That's a requirement. But schedule: hybrid work with at least three days per week in person. We'll put schedule section. We need to avoid duplication: Benefits already includes hybrid work; schedule could be just that. But we can still have schedule section with that detail. We must not repeat job title heading. Use
for each section. We must not include boilerplate like EEO etc. Remove that. Now produce HTML fragment. Let's craft:
About the role
At Advanced Space, we're enabling humanity's return to the Moon and building the technologies that will take us to Mars and beyond. We're looking for a Senior Systems Engineer with 8–12 years of experience to lead mission-critical systems engineering efforts across the full lifecycle of space systems—from concept to orbit and beyond. In this role, you'll lead the development of mission concepts, ConOps, system architectures, technical baselines, requirements, interfaces, and verification strategies. You'll provide system-level technical leadership across spacecraft, ground systems, flight software, mission operations, and relevant subsystem disciplines while working directly with customers and mission partners throughout the mission lifecycle. You'll have the opportunity to support complex aerospace and spaceflight programs across multiple lifecycle phases, including system development,