Astrodynamics and Navigation Engineer III

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real content. We need to parse the posting. First, job title is already shown, we should not repeat it as heading. We need to extract: - About the role: maybe a paragraph describing the role. The posting starts: "Quantum Space is redefining mobility and maneuverability in space... Who We’re Looking For We are seeking an experienced Astrodynamics and Navigation Engineer III to lead the analysis, design, and operational support of highly maneuverable spacecraft missions. This role will lead trajectory design, orbit determination, maneuver planning, and mission analysis efforts across the mission lifecycle — from early concept development through on-orbit operations. You will work closely with systems engineering, GNC, flight software, propulsion, and mission operations teams to develop and implement robust, high-fidelity flight dynamics capabilities that support trajectory design, orbit determination, maneuver planning, and mission analysis for missions across multiple regimes." That's about the role. So we can have

About the role

with a

containing that paragraph. - Responsibilities: The "Where You’ll Make an Impact" section lists many responsibilities. So we can have

Responsibilities

with a

• list. - Requirements: The "What It Takes" section lists required qualifications: Bachelor’s degree, 5-10+ years experience, strong background, experience with tools, language, analytical skills, communication. So we can have

  Requirements

  with list. - Qualifications: Might be overlapping with Requirements. The posting also has "Nice-to-Have Experience:" which could be Qualifications or Skills. We could treat "Nice-to-Have Experience" as

  Preferred Qualifications

  but the instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We can use Qualifications for required, and Skills for nice-to-have? Or we could combine. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings if content exists. We have: - About the role: yes. - Responsibilities: yes. - Requirements: yes (the "What It Takes"). - Qualifications: maybe we can treat the "Nice-to-Have Experience" as Qualifications (preferred). Or we could treat as Skills. But we have also "Skills" heading; we could put technical skills there (experience with tools, languages). However the required section already includes experience with tools and languages. Might be redundant. Better: Use Requirements for mandatory qualifications, Skills for technical skills (tools, languages), Qualifications for education/degree? But the instruction says we can choose whichever fits. Let's map: - About the role: paragraph. - Responsibilities: list of impact items. - Requirements: list of mandatory qualifications (Bachelor’s degree, 5-10+ years experience, strong background, strong analytical/problem-solving, excellent communication). - Skills: list of technical skills/experience (experience with STK/ODTK, Freeflyer, GMAT, Python/MATLAB, etc.) plus maybe nice-to-have. - Qualifications: maybe education? But we already have degree in Requirements. Could combine. Alternatively, we could have Qualifications for the Nice-to-Have Experience (preferred qualifications). And Skills for the technical tools/languages. Let's decide: - Requirements: mandatory (degree, years experience, background, analytical, communication). - Skills: technical skills (tools, languages, etc.) - Qualifications: preferred qualifications (nice-to-have) (Master’s degree, cislunar three-body, RPO, low-thrust, alternative nav, exposure to other subsystems). - Benefits: The "What You’ll Get" section includes ownership, innovation, impact, growth, compensation (competitive salary, equity, comprehensive benefits). Also there is a separate "Compensation – Competitive salary, equity, and comprehensive benefits including medical, dental, vision, generous leave, HSA, 401(k) matching, and equity sharing." Also location and base salary range. Thus we have Benefits: we can list ownership, innovation, impact, growth as benefits? Actually those are more like "What You’ll Get". Could treat as Benefits section. Pay: we have base salary range $125,000 - $175,000. Also mention equity, etc. So we can have Pay section. Schedule: Not mentioned. So we should not include Schedule heading. Location: Not a heading per instruction; we can fold into a short p or drop. Probably include as a short paragraph under Benefits or separate? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Location is minor metadata, we can include in a short p. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Apply now. Join us in building the next generation of spacecraft." That's application instruction; we should remove. Also "Additional Requirements To comply with U.S. Government space technology export regulations, including ITAR, applicants must be a U.S. citizen, lawful permanent resident, protected individual per 8 U.S.C. 1324b(a)(3), or eligible to obtain the required authorizations from the U.S. Department of State." That is a requirement (citizenship). Should we include? It's a requirement. It's not boilerplate; it's a specific requirement. So we should include it under Requirements. Thus Requirements list should include: Bachelor’s degree, 5-10+ years experience, strong background in orbital mechanics, spacecraft dynamics, navigation, experience with industry standard tools, experience in at least one language (Python/MATLAB), strong analytical and problem-solving skills, excellent written and verbal communication skills, U.S. citizenship or lawful permanent resident etc. Now we need to ensure we don't include filler like "commensurate with experience". Not present. Now produce HTML. Structure:

  About the role

  ...

  Responsibilities

  • Lead mission design activities for LEO, MEO, GEO, and cislunar missions, including:
  Actually the responsibilities list includes a colon then subitems. We need to break into list items. The original text: "Lead mission design activities for LEO, MEO, GEO, and cislunar missions, including:Trajectory and maneuver designDelta-v/propellant budgetingOrbit maintenance planningNavigation covariance sensitivity studiesLaunch injection dispersion and maneuver execution Monte Carlo analysesDisposal planningOwn mission-level simulation and end-to-end performance analysis, including:Eclipse & payload coverage analysesConjunction assessment and collision avoidance analysisGround station visibility analysis and link budget inputsTracking geometry assessment and schedulesScheduling support for mission operationsArchitect navigation solutions, informing selection of spacecraft tracking measurement phenomenologies and ground networksDevelop and maintain internal flight dynamics and mission analysis tools (Python/MATLAB/C++-based)Contribute to spacecraft operations, including maneuver planning, anomaly investigation and on-orbit performance evaluationGenerate technical documentation, trade studies, and design reportsCollaborate with GNC, communications, systems engineering, mission operations" We need to parse into sensible list items. Could break each bullet after colon as separate items. But we can keep as a single list item with subitems? Better to split. We can produce list items: - Lead mission design activities for LEO, MEO, GEO, and cislunar missions, including: - Trajectory and maneuver design - Delta-v/propellant budgeting - Orbit maintenance planning - Navigation covariance sensitivity studies - Launch injection dispersion and maneuver execution Monte Carlo analyses - Disposal planning - Own mission-level simulation and end-to-end performance analysis, including: - Eclipse & payload coverage analyses - Conjunction assessment and collision avoidance analysis - Ground station visibility analysis and link budget inputs - Tracking geometry assessment and schedules - Scheduling support for mission operations - Architect navigation solutions, informing selection of spacecraft tracking measurement phenomenologies and ground networks - Develop and maintain internal flight dynamics and mission analysis tools (Python/MATLAB/C++-based) - Contribute to spacecraft operations, including maneuver planning, anomaly investigation and on-orbit performance evaluation - Generate technical documentation, trade studies, and design reports - Collaborate with GNC, communications, systems engineering, mission operations We can embed nested
  but instruction only says use
  • for any list of duties/requirements/benefits. It didn't forbid nested lists. Could do nested. Simplify: just make each top-level bullet as
  • and include sub-bullets as separate
  • with indentation? Might be okay. We'll produce a flat list with each distinct responsibility. Let's extract distinct responsibilities: 1. Lead mission design activities for LEO, MEO, GEO, and cislunar missions. 2. Trajectory and maneuver design. 3. Delta-v/propellant budgeting. 4. Orbit maintenance planning. 5. Navigation covariance sensitivity studies. 6. Launch injection dispersion and maneuver execution Monte Carlo analyses. 7. Disposal planning. 8. Own mission-level simulation and end-to-end performance analysis. 9. Eclipse & payload coverage analyses. 10. Conjunction assessment and collision avoidance analysis. 11. Ground station visibility analysis and link budget inputs. 12. Tracking geometry assessment and schedules. 13. Scheduling support for mission operations. 14. Architect navigation solutions, informing selection of spacecraft tracking measurement phenomenologies and ground networks. 15. Develop and maintain internal flight dynamics and mission analysis tools (Python/MATLAB/C++-based). 16. Contribute to spacecraft operations, including maneuver planning, anomaly investigation and on-orbit performance evaluation. 17. Generate technical documentation, trade studies, and design reports. 18. Collaborate with GNC, communications, systems engineering, mission operations. That seems fine. Now Requirements list: - Bachelor’s degree in Aerospace Engineering, Astrodynamics, Physics, or related field. - 5-10+ years of experience performing mission design tasks, general mission analysis, and flight dynamics related operations for spacecraft systems. - Strong background in orbital mechanics, spacecraft dynamics, and spacecraft navigation. - Experience with industry standard tools such as Systems Tool Kit (STK)/Orbit Determination Toolkit (ODTK), Freeflyer, GMAT, or similar. - Experience in at least one of the following languages: Python, MATLAB. - Strong analytical and problem-solving skills. - Excellent written and verbal communication skills. - U.S. citizenship, lawful permanent resident, protected individual per 8 U.S.C. 1324b(a)(3), or eligible to obtain required authorizations from the U.S. Department of State (ITAR compliance). Now Skills list (technical skills/experience): - Experience with Systems Tool Kit (STK)/Orbit Determination Toolkit (ODTK), Freeflyer, GMAT, or similar. - Experience with Python, MATLAB (or C++? Actually tools include C++-based). Could list: Python, MATLAB, C++. - Experience with cislunar three-body trajectory design and navigation (nice-to-have) maybe put under Qualifications. But we already have experience with tools in Requirements; we could avoid duplication. Perhaps better: Skills list includes: Proficiency with STK/ODTK, Freeflyer, GMAT; Programming languages: Python, MATLAB, C++; Experience with mission analysis tools development; Experience with orbit determination, maneuver planning, etc. However many of these are already in Requirements. To avoid duplication, we could put the nice-to-have under Qualifications and keep Skills for technical proficiencies not already covered. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Requirements and Qualifications into one section? But we have headings for both