Jobs · Engineering

Senior Guidance, Navigation, & Control (GNC) Engineer

K2 Space Corporation · United States · 2 wk ago
RemoteRemoteEngineering$160k–$235k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes intro about company then "The Role". We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include sections where there is real specific content. The posting includes: "The Role" description (some paragraphs). Then "Responsibilities" list. Then "Qualifications" list (including Nice to Have). Then "Compensation And Benefits" includes base salary range and benefits. No explicit "Skills" separate; qualifications cover skills. No "Schedule". So we should include sections: About the role (maybe from intro? Actually "The Role" is a heading; we can map to About the role). Responsibilities, Qualifications, Benefits (including Pay). Possibly also "Pay" separate? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which to include. The posting has "Compensation And Benefits" which includes base salary range and benefits. So we could have a Benefits section that includes both salary and benefits. Or we could split Pay and Benefits. Since they gave both, we could include Pay section with salary range, and Benefits section with benefits list. The instruction: Prefer a few substantive sections over many thin ones. But we have both salary and benefits details; could combine into Benefits. However they explicitly list Pay as a possible heading; we could include Pay if we have salary info. I'd include Pay section with salary range, and Benefits section with benefits list. That seems reasonable. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, Export Compliance, Equal Opportunity, accommodation request, etc. Also remove "If you don’t meet 100%..." etc. Also remove "Building a spacecraft..." etc. Also remove "If you need a reasonable accommodation..." etc. Also remove "Export Compliance" etc. Also remove "Equal Opportunity". Also remove any duplicated lines. We need to preserve all substantive information: company intro, role description, responsibilities, qualifications (including nice to have), compensation (base salary range + equity), benefits (PTO, medical/dental/vision, life insurance, paid parental leave, many other perks). Also maybe mention equity in company. We need to format:

About the role

then

with the role description paragraphs (maybe multiple

). Then

Responsibilities

then
  • ... etc. Then

    Qualifications

    then
    • ... for required qualifications. Then maybe a separate

      Nice to Have

      ? Not in list of headings but could be under Qualifications? The instruction says use headings from list; Nice to Have not listed. Could incorporate into Qualifications as part of same list but maybe we can keep as part of Qualifications with a note. However we should not invent headings not in list. So we can keep Qualifications section containing both required and nice-to-have items, maybe separate paragraphs. But we need to preserve all info; we can include a

      saying "Nice to have:" then list. That's okay. Then

      Pay

      then

      with base salary range and equity. Then

      Benefits

      then
      • ... benefits. We must not include Schedule section. We must output only HTML fragment, no markdown fences. Let's extract the substantive text. Company intro: "K2 is building the largest and highest-power satellites ever flown, unlocking performance levels previously out of reach across every orbit. Backed by $450M from leading investors including Altimeter Capital, Redpoint Ventures, T. Rowe Price, Lightspeed Venture Partners, Alpine Space Ventures, and others – with an additional $500M in signed contracts across commercial and US government customers – we’re mass-producing the highest-power satellite platforms ever built for missions from LEO to deep space. The rise of heavy-lift launch vehicles is shifting the industry from an era of mass constraint to one of mass abundance, and we believe this new era demands a fundamentally different class of spacecraft. Engineered to survive the harshest radiation environments and to fully capitalize on today’s and tomorrow’s massive rockets, K2 satellites deliver unmatched capability at constellation scale and across multiple orbits. With multiple launches planned through 2026 and 2027, we're Building Bigger to develop the solar system and become a Kardashev Type II (K2) civilization. If you are a motivated individual who thrives in a fast-paced environment and you're excited about contributing to the success of a groundbreaking Series C space startup, we’d love for you to apply." That's the intro; we can put that under About the role? Actually About the role should describe the role, not company. But we could include company overview as part of About the role? The instruction: "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role likely expects a description of the role. The company intro is not about the role but could be considered part of About the role? Might be okay to include as preamble. However we could treat About the role as the paragraph starting "The Role As a Senior GNC engineer..." That is the role description. The company intro could be omitted? But we must preserve ALL substantive information. The company intro is substantive about the company; but the instruction says we should not repeat job title as heading, but we can include company info in About the role section? It might be acceptable to include it there. However the heading "About the role" suggests role description, but we can still include company overview as part of that section; it's not prohibited. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine company overview and role description under About the role. That would preserve all. Thus About the role section will contain the company intro paragraph(s) plus the role description paragraph(s). We'll need to split into

        tags. Let's parse the role description: After "The Role" heading, we have: "As a Senior GNC engineer, you will be a core driver of the overall spacecraft GNC architecture. You will execute detailed trade studies to find new and novel ways to implement the spacecraft’s orbital guidance, orbital control, and attitude and orbit estimation systems. In the first 3 months, you will support the development/improvement of the MEO navigation, taking lessons learned from the Gravitas mission and applying them to the baseline GNC stack. In the first 6 months you will support the development of new and novel navigation approaches to support future programs – specifically solving navigation for GEO, cis lunar, and interplanetary. In parallel you will support the development of the in-house trajectory design scheme and associated analysis workflow. As we learn more about our system, this will lead to updates to both the GNC stack and the K2 6-DOF simulation. The expectation is that all GNC team members commit code to the 6-DOF sim as well as owning a portion of the GNC flight software. In the first year, you will support launch and on orbit operations of the Trinity mission – the stacked launch of 3 K2 Mega spacecraft. In parallel, you will continue to support improvements, closing the loop on the design, build, test, fly lifecycle." That's the role description. Now Responsibilities: list bullet points: - Work with other engineering leads to develop and validate a novel high level vehicle architecture - Develop novel algorithms for precise navigation in LEO, MEO, GEO, cis lunar, and interplanetary space. - Develop simulation and modeling tools to support vehicle and GNC trade studies. This includes mission design, controls analysis, and 6-DOF simulation development. - Contribute to building the GNC organization by recruiting, hiring, and mentoring other engineers Now Qualifications: list: - Experience with implementing estimation algorithms on for flight software and ground software, specifically Kalman Filters, Extended Kalman Filters, and Unscented Kalman Filters - Experience performing Monte Carlo based analyses and covariance analysis - Experience with verification and validation of GNC flight software in an integrated environment, leveraging 6-DOF simulation and HITL testing. - Experience with GNC sensor sizing, selection, and system design - Experience with Python, Julia, C/C++, Rust, or Matlab for algorithm development, implementation, and simulation Nice to Have: - Experience with system identification, leveraging on-orbit data - Experience with early-stage spacecraft conceptual design, i.e. “clean sheet” design work - Breadth in control algorithm development - Experience with reaction wheel, control moment gyroscope, or thruster sizing and algorithm implementation - Experience with trajectory analysis, modeling, optimization, and mission design for GEO, cislunar, interplanetary missions Now Compensation And Benefits: "Base salary range for this role is $160,000 - $235,000 + equity in the company Salary will be based on several factors including, but not limited to: knowledge and skills, education, and experience level Comprehensive benefits package including paid time off, medical/dental/vision coverage, life insurance, paid parental leave, and many other perks" We need to separate Pay and Benefits. Pay: base salary range + equity. Benefits: list items. Now we need to output HTML. We'll do:

        About the role

        K2 is building the largest and highest-power satellites ever flown, unlocking performance levels previously out of reach across every orbit. Backed by $450M from leading investors including Altimeter Capital, Redpoint Ventures, T. Rowe Price, Lightspeed Venture Partners, Alpine Space Ventures, and others – with an additional $500M in signed contracts across commercial and US government customers – we’re mass-producing the highest-power satellite platforms ever built for missions from LEO to deep space. The rise of heavy-lift launch vehicles is shifting the industry from an era of mass constraint to one of mass abundance, and we believe this new era demands a fundamentally different class of spacecraft. Engineered to survive the harshest radiation environments and to fully capitalize on today’s and tomorrow’s massive rockets, K2 satellites deliver unmatched capability at constellation scale and across multiple orbits. With multiple launches planned through 2026 and 2027, we're Building Bigger to develop the solar system and become a Kardashev Type II (K2) civilization. If you are a motivated individual who thrives in a fast-paced environment and you're excited about contributing to the success of a groundbreaking Series C space startup, we’d love for you to apply.

        As a Senior GNC engineer, you will be a core driver of the overall spacecraft GNC architecture. You will execute detailed trade studies to find new and novel ways to implement the spacecraft’s orbital guidance, orbital control, and attitude and orbit estimation systems. In the first 3 months, you will support the development/improvement of the MEO navigation, taking lessons learned from the Gravitas mission and applying them to the baseline GNC stack. In the first 6 months you will support the development of new and novel navigation approaches to support future programs – specifically solving navigation for GEO, cis lunar, and interplanetary. In parallel you will support the development of the in-house trajectory design scheme and associated analysis workflow. As we learn more about our system, this will lead to updates to both the GNC stack and the K2 6-DOF simulation. The expectation is that all GNC team members commit code to the 6-DOF sim as well as owning a portion of the GNC flight software. In the first year, you will support launch and on orbit operations of the Trinity mission – the stacked launch of 3 K2 Mega spacecraft. In parallel, you will continue to support improvements, closing the loop on the design, build, test, fly lifecycle.

        Then Responsibilities:

        Responsibilities

        • Work with other

Similar jobs