Navigation Lead Engineer for Human Landing Systems
Mclaurin Aerospace · Huntsville, AL · 1 mo ago
Information TechnologyContract
We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content.
We need to parse the posting: It has intro about passion, etc. Could be "About the role". Then "Job Functions" list of duties. Then "Provide demonstrated (minimum of 10 years) expertise..." that's qualifications. Then "Qualifications" heading with degree etc. Then "Skills" list. Then "Duties Day To Day Activities Include" which is responsibilities. Then "Benefits" list. There's also mention of Pay? Not specific. No pay amount. So we should not include Pay or Schedule sections because not stated. Also no schedule specifics.
We need to preserve all substantive info, not invent. Remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, scam warning, duplicated lines. Also remove "Mclaurin is a unique organization..." maybe that's about company but could be considered part of benefits? It's more about organization; maybe keep as part of About the role? It's not boilerplate? It's describing organization; could be considered part of About the role. But we need to preserve all substantive info. However the instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The paragraph about Mclaurin is not boilerplate; it's about the organization. Keep it.
Also "US Citizenship and the ability to pass a comprehensive security background investigation is required." That's a requirement; keep.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content.
We need to parse the posting: It has intro about passion, etc. Could be "About the role". Then "Job Functions" list of duties. Then "Provide demonstrated (minimum of 10 years) expertise..." that's qualifications. Then "Qualifications" heading with degree etc. Then "Skills" list. Then "Duties Day To Day Activities Include" which is responsibilities. Then "Benefits" list. There's also mention of Pay? Not specific. No pay amount. So we should not include Pay or Schedule sections because not stated. Also no schedule specifics.
We need to preserve all substantive info, not invent. Remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, scam warning, duplicated lines. Also remove "Mclaurin is a unique organization..." maybe that's about company but could be considered part of benefits? It's more about organization; maybe keep as part of About the role? It's not boilerplate? It's describing organization; could be considered part of About the role. But we need to preserve all substantive info. However the instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The paragraph about Mclaurin is not boilerplate; it's about the organization. Keep it.
Also "US Citizenship and the ability to pass a comprehensive security background investigation is required." That's a requirement; keep.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
Intro paragraphs about passion, need for talent, etc. plus description of organization maybe.
Responsibilities
- ... list from Job Functions and Duties Day To Day Activities Include.
About the role
... intro paragraphs ... plus organization description.
Responsibilities
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
? The instruction: use
for prose. Could have multiple
elements. We'll keep as one
maybe but could split. Safer to put as one
containing all. Now Responsibilities
- each duty.
We need to ensure no duplication. We'll list each distinct duty.
Let's compile list:
1. Lead the insight/oversight effort of the HLS GNC group (across NASA centers) with regards to all aspects of the navigation system
2. Lead efforts for the modeling and simulation of landing performance analysis of HLS trajectories
3. Lead efforts for the integration of all relevant models into the simulation, including on-orbit state estimation using ground tracking (e.g., range and doppler from Deep Space Network stations), on-board state estimation fusing inertial measurements with terrain relative sensing such as optical, radar, lidar measurements
4. Steward trade studies to assess navigation performance under dispersed model parameters to assess uncertainty of unknown model parameters, and evaluate navigation margins
5. Assess HLS commercial partner test data and partner sensors and models
6. Develop in-house models and/or integrate sensor models from HLS commercial providers into 6-DOF simulations such as the Generalized Aerospace Simulation in Simulink (GLASS) tool
7. Perform and steward deep space navigation studies to assess HLS partner's navigation performance using FreeFlyer, MONTE or JSC-Linear Covariance Tool (SIGMA)
8. Execute/modify existing software/scripts in Python, Matlab, Fortran, C++
9. Communicate navigation margin findings to HLS Chief Engineer and HLS commercial partners
10. Maintain and strengthen NASA HLS cross-center navigation team
11. Develop and coordinate with the GNC discipline strategic planning for growing navigation expertise at MSFC
12. Technical leadership of the HLS navigation team's modeling and simulation of HLS system, including simulation integration, visualization, analysis, and trade studies
13. Interface with commercial HLS partners and other NASA centers
14. Debrief to HLS partners and HLS Chief Engineers
15. Perform and/or steward Deep Space Navigation studies, including orbit determination accuracy of the HLS though its trajectory using FreeFlyer, MONTE and/or LinearCovariance (SIGMA) tools
16. Dynamic modeling of the HLS trajectory
17. Create, edit and debug software written in Python, Matlab, Fortran, and C/C++
18. Optimize and improve analysis tools and GN&C models
19. Work with GN&C leads and other engineering disciplines
20. Support the verification and validation of technical products
21. Prepare and present technical reports and briefings
Some items duplicate (e.g., 1 and 12 similar). But we keep as per instruction to preserve all substantive info; we could keep duplicates but better to avoid redundancy? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplicates are still substantive info; but we could keep them; it's okay.
Now Qualifications
- items: - Demonstrated minimum of 10 years expertise to support HLS program navigation team at SME level within GNC discipline. - Technical leadership of a team of navigation engineers to achieve safe Moon landing and return to Earth. - Programming skills and mentoring abilities highly desired. - Degree in Aerospace Engineering, Mechanical Engineering, Physics or related field from an ABET accredited institution required. -