Flight Software Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map sections accordingly.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should remove the EEO paragraph and ITAR? ITAR is not boilerplate but is a requirement; maybe keep? It's a requirement about citizenship. It's substantive. We can include under Requirements or Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine.
We need sections: About the role (maybe "About the role" corresponds to Who We Are and description). Responsibilities (Job Responsibilities). Requirements (What It Takes). Qualifications/Skills (What We'd Love). Benefits (What We Offer). Pay (Pay Range). Schedule? Not given. Where You'll Be maybe location; could be part of About the role or separate? Not required heading; we can include location in About the role paragraph.
We must not create sections with filler like "commensurate with experience". Pay range is given, so we can create Pay section.
We must not include duplicated lines. Ensure we preserve all substantive info.
Let's extract content:
Who We Are: Space Kinetic is a dual use space technology startup building a completely new architecture for space operations – one that brings the advantages of proliferated drone technology (low-cost, operationally flexible, attainable, distributed) to space missions while reducing the ecosystem's reliance on consumable fuel. In a world where many companies are focused on incrementally improving the status quo, we are focused on creating something entirely different – an architecture underpinned by new first principles to meet the opportunities and challenges of the third space age head-on. Our goal is to move away from one-to-one space architectures – where each satellite in a constellation has one (or a small # of) primary payloads attached to the bus -- and unlock a ‘one-to-many’ system, where each satellite has a large number of payloads which can be deployed from their host spacecraft at high velocities without firing a thruster. This is not a role for someone looking for a traditional 40-hour work week. Space Kinetic is building ambitious, first-of-its-kind technology, and that requires urgency, ownership, and a high level of commitment to changing the foundational assumptions for everything we do in space.
What You’ll Do: The Flight Software Engineer will design, develop, test, and maintain the software that controls Space Kinetic’s spacecraft. You will work across the full software lifecycle and collaborate with multidisciplinary engineering teams to deliver reliable, mission-critical software for operation in space.
Job Responsibilities:
- Design, develop, test, and maintain embedded flight software for spacecraft control and operations.
- Integrate and validate software in simulation, flight-replica, hardware-in-the-loop, and flight environments.
- Partner with systems, electrical, GNC, test, and mission engineering teams to define software requirements, interfaces, and designs.
- Support spacecraft commissioning, flight operations, anomaly resolution, and software updates following launch.
What It Takes:
- Bachelor’s or master’s degree in Computer Science, Electrical Engineering, Computer Engineering, or a related technical field.
- 2 to 3 years of experience developing embedded or real-time software for space, aerospace, robotics, or other mission-critical systems.
- Understanding of the software-development lifecycle, from requirements and design through integration, testing, and operations.
- Working proficiency in C/C++, with knowledge of Python or similar scripting languages for automation and testing.
- Familiarity with RTOS, bare-metal programming, or Linux-based embedded systems.
- Understanding of software reliability, deterministic timing, concurrency, and resource management in constrained environments.
- Ability to obtain and maintain a U.S. Government security clearance.
What We’d Love:
- Experience with flight software frameworks such as NASA cFS, F´, or custom architectures.
- Familiarity with model-based systems engineering and interface-control documentation.
- Knowledge of spacecraft communication protocols such as CCSDS, SpaceWire, or MIL-STD-1553.
Where You’ll Be:
- The position is onsite at our headquarters in El Segundo, CA.
- Domestic travel may be required (up to ~20% of the year).
What We Offer:
- Equity-Based Compensation
- 401(k) retirement plan with a 3.5% company match
- Highly Competitive PTO
- Paid company holidays + winter break
- Comprehensive medical, dental, and vision insurance
- Unique Performance-based bonus opportunities
ITAR Requirements: To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful, permanent resident (aka green card holder), (iii) Refugee under 8 U.S.C. 1157, or (iv) Asylee under 8 U.S.C.1158, or be eligible to obtain the required authorizations from the U.S. Department of State. Learn more about ITAR here
Equal Employment Opportunity: ... (remove as boilerplate)
Pay Range: $120,000 USD - $150,000 USD
We need to output HTML fragment only, no markdown fences.
We'll create sections:
About the role
with paragraph(s) containing Who We Are and What You'll Do maybe combined.
Responsibilities
with - list.
Requirements
with - list (What It Takes).
Preferred Qualifications
(or Skills) with - list (What We'd Love).
Location & Travel
maybe not required but we can include 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 we can use Qualifications or Skills for preferred qualifications. Benefits for What We Offer. Pay for Pay Range.
We might not need Schedule.
We should not create empty sections.
Thus sections:
About the role (Who We Are + What You'll Do)
Responsibilities
Requirements
Qualifications (or Skills) for What We'd Love
Benefits for What We Offer
Pay for Pay Range
We could also include Location & Travel but not required; maybe incorporate into About the role paragraph.
We must not include ITAR as separate heading; we can fold into Requirements (citizenship/clearance). Actually ITAR is about citizenship; we can include in Requirements as a bullet.
Equal Employment Opportunity removed.
Now craft HTML.
We need to preserve all substantive info: include details about equity-based compensation, 401k match, PTO, holidays, medical/dental/vision, performance bonus.
Pay range: $120,000 - $150,000.
Let's write.
Be careful to not duplicate lines.
Let's produce:
About the role
Space Kinetic is a dual‑use space technology startup building a completely new architecture for space operations – one that brings the advantages of proliferated drone technology (low‑cost, operationally flexible, attainable, distributed) to space missions while reducing the ecosystem's reliance on consumable fuel. In a world where many companies are focused on incrementally improving the status quo, we are focused on creating something entirely different – an architecture underpinned by new first principles to meet the opportunities and challenges of the third space age head‑on. Our goal is to move away from one‑to‑one space architectures – where each satellite in a constellation has one (or a small # of) primary payloads attached to the bus -- and unlock a ‘one‑to‑many’ system, where each satellite has a large number of payloads which can be deployed from their host spacecraft at high velocities without firing a thruster. This is not a role for someone looking for a traditional 40‑hour work week. Space Kinetic is building ambitious, first‑of‑its‑kind technology, and that requires urgency, ownership, and a high level of commitment to changing the foundational assumptions for everything we do in space. The Flight Software Engineer will design, develop, test, and maintain the software that controls Space Kinetic’s spacecraft. You will work across the full software lifecycle and collaborate with multidisciplinary engineering teams to deliver reliable, mission‑critical software for operation in space.
Responsibilities
- Design, develop, test, and maintain embedded flight software for spacecraft control and operations.
- Integrate and validate software in simulation, flight‑replica, hardware‑in‑the‑loop, and flight environments.
- Partner with systems, electrical, GNC, test, and mission engineering teams to define software requirements, interfaces, and designs.
- Support spacecraft commissioning, flight operations, anomaly resolution, and software updates following launch.
Requirements
- Bachelor’s or master’s degree in Computer Science, Electrical Engineering, Computer Engineering, or a related technical field.
- 2 to 3 years of experience developing embedded or real‑time software for space, aerospace, robotics, or other mission‑critical systems.
- Understanding of the software‑development lifecycle, from requirements and design through integration, testing, and operations.
- Working proficiency in C/C++, with knowledge of Python or similar scripting languages for automation and testing.
- Familiarity with RTOS, bare‑metal programming, or Linux‑based embedded systems.
- Understanding of software reliability, deterministic timing, concurrency, and resource management in constrained environments.
- Ability to obtain and maintain a U.S. Government security clearance.
- Must be a U.S. citizen or national, U.S. lawful permanent resident (green card holder), refugee, or asylee, or eligible to obtain the required authorizations from the U.S. Department of State (ITAR compliance).
Qualifications
- Experience with flight software frameworks such as NASA cFS, F´, or custom architectures.
- Familiarity with model‑based systems engineering and interface‑control documentation.
- Knowledge of spacecraft communication protocols such as CCSDS, SpaceWire, or MIL‑STD‑1553.
Benefits
- Equity‑based compensation
- 401(k) retirement plan with a 3.5% company match
- Highly competitive PTO
- Paid company holidays + winter break
- Comprehensive medical, dental, and vision insurance
- Unique performance‑based bonus opportunities
Pay
$120,000 USD – $150,000 USD annual base salary
We should not include location/travel separate; we could add location in About the role paragraph: maybe add sentence about location. The Where You'll Be info: onsite at headquarters in El Segundo, CA; domestic travel up to ~20% of year. We can incorporate that into About the role paragraph after the description.
Add: "The position is onsite at our headquarters in El Segundo, CA, with domestic travel required up to ~20% of the year."
Let's add that to About the role paragraph.
Now final HTML.
Check no extra headings like Schedule. Good.
Now output
Requirements
with- list (What It Takes).
Preferred Qualifications
(or Skills) with- list (What We'd Love).
Location & Travel
maybe not required but we can include as part of About the role? The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use Qualifications or Skills for preferred qualifications. Benefits for What We Offer. Pay for Pay Range. We might not need Schedule. We should not create empty sections. Thus sections: About the role (Who We Are + What You'll Do) Responsibilities Requirements Qualifications (or Skills) for What We'd Love Benefits for What We Offer Pay for Pay Range We could also include Location & Travel but not required; maybe incorporate into About the role paragraph. We must not include ITAR as separate heading; we can fold into Requirements (citizenship/clearance). Actually ITAR is about citizenship; we can include in Requirements as a bullet. Equal Employment Opportunity removed. Now craft HTML. We need to preserve all substantive info: include details about equity-based compensation, 401k match, PTO, holidays, medical/dental/vision, performance bonus. Pay range: $120,000 - $150,000. Let's write. Be careful to not duplicate lines. Let's produce:
About the role
Space Kinetic is a dual‑use space technology startup building a completely new architecture for space operations – one that brings the advantages of proliferated drone technology (low‑cost, operationally flexible, attainable, distributed) to space missions while reducing the ecosystem's reliance on consumable fuel. In a world where many companies are focused on incrementally improving the status quo, we are focused on creating something entirely different – an architecture underpinned by new first principles to meet the opportunities and challenges of the third space age head‑on. Our goal is to move away from one‑to‑one space architectures – where each satellite in a constellation has one (or a small # of) primary payloads attached to the bus -- and unlock a ‘one‑to‑many’ system, where each satellite has a large number of payloads which can be deployed from their host spacecraft at high velocities without firing a thruster. This is not a role for someone looking for a traditional 40‑hour work week. Space Kinetic is building ambitious, first‑of‑its‑kind technology, and that requires urgency, ownership, and a high level of commitment to changing the foundational assumptions for everything we do in space. The Flight Software Engineer will design, develop, test, and maintain the software that controls Space Kinetic’s spacecraft. You will work across the full software lifecycle and collaborate with multidisciplinary engineering teams to deliver reliable, mission‑critical software for operation in space.
Responsibilities
- Design, develop, test, and maintain embedded flight software for spacecraft control and operations.
- Integrate and validate software in simulation, flight‑replica, hardware‑in‑the‑loop, and flight environments.
- Partner with systems, electrical, GNC, test, and mission engineering teams to define software requirements, interfaces, and designs.
- Support spacecraft commissioning, flight operations, anomaly resolution, and software updates following launch.
Requirements
- Bachelor’s or master’s degree in Computer Science, Electrical Engineering, Computer Engineering, or a related technical field.
- 2 to 3 years of experience developing embedded or real‑time software for space, aerospace, robotics, or other mission‑critical systems.
- Understanding of the software‑development lifecycle, from requirements and design through integration, testing, and operations.
- Working proficiency in C/C++, with knowledge of Python or similar scripting languages for automation and testing.
- Familiarity with RTOS, bare‑metal programming, or Linux‑based embedded systems.
- Understanding of software reliability, deterministic timing, concurrency, and resource management in constrained environments.
- Ability to obtain and maintain a U.S. Government security clearance.
- Must be a U.S. citizen or national, U.S. lawful permanent resident (green card holder), refugee, or asylee, or eligible to obtain the required authorizations from the U.S. Department of State (ITAR compliance).
Qualifications
- Experience with flight software frameworks such as NASA cFS, F´, or custom architectures.
- Familiarity with model‑based systems engineering and interface‑control documentation.
- Knowledge of spacecraft communication protocols such as CCSDS, SpaceWire, or MIL‑STD‑1553.
Benefits
- Equity‑based compensation
- 401(k) retirement plan with a 3.5% company match
- Highly competitive PTO
- Paid company holidays + winter break
- Comprehensive medical, dental, and vision insurance
- Unique performance‑based bonus opportunities
Pay
$120,000 USD – $150,000 USD annual base salary
We should not include location/travel separate; we could add location in About the role paragraph: maybe add sentence about location. The Where You'll Be info: onsite at headquarters in El Segundo, CA; domestic travel up to ~20% of year. We can incorporate that into About the role paragraph after the description. Add: "The position is onsite at our headquarters in El Segundo, CA, with domestic travel required up to ~20% of the year." Let's add that to About the role paragraph. Now final HTML. Check no extra headings like Schedule. Good. Now output
- list (What We'd Love).