Sr.Satellite Systems Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions.
We need to parse the posting.
Content:
- Intro about Loft Federal (company description) maybe part of About the role? Actually "About Loft Federal" is company description. Could be part of About the role? Usually "About the role" is description of role. There's a section "About This Role:" after the description of role. So we can treat that as About the role.
- Responsibilities: bullet points after "About This Role:"? Let's see: "In this role, you’ll work at the intersection of engineering, customers, and program execution to help turn mission needs into successful spacecraft. You’ll collaborate with internal teams and customers to develop and manage technical budgets, system requirements, and verification approaches, while helping shape and evolve mission concepts of operations (CONOPS) and supporting customer Service Level Agreements. You’ll also have the opportunity to contribute to program and product management, including working directly with customers on programmatic and schedule matters. Alongside your teammates, you’ll develop interface specifications, CONOPS, and other key design documentation, then bring that work into the real world by supporting test procedures and participating in spacecraft integration and test campaigns at our manufacturer’s facility."
That's responsibilities.
- Must Haves: list of requirements.
- Nice to Haves: list of preferred qualifications.
- Benefits: list under "Some of Our Awesome Benefits:" with bullet points.
- Pay: Salary Range: $136,000 USD - $175,000 USD.
- Schedule: Not mentioned. So we should not include Schedule section.
- Qualifications: Could combine Must Haves and Nice to Haves? But we have separate sections for Requirements and Qualifications maybe. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections to include based on content.
We have:
- About the role: we have company description and "About This Role:" maybe combine.
- Responsibilities: as above.
- Requirements: Must Haves.
- Qualifications: Nice to Haves? Or maybe Skills: Preferred experience etc. Could treat Nice to Haves as Qualifications or Skills. The instruction says we can have Skills section. We could put "Preferred: Experience on RF and/or Electrical subsystems Preferred: Proficient with STK Plus: Experience with thermal/structural analysis" under Skills. Also "You have 5 years of experience as a systems engineer or similar in the space industry" maybe under Requirements? Actually that is under Nice to Haves? Let's re-evaluate.
The posting:
"Must Haves:
US Citizenship Active DoD Secret clearance with ability to obtain Top Secret clearance. Active Top Secret clearance with experience in (last 2 years) or active Sensitive Compartmented Information (SCI) strongly desired.
Enjoy being the face of the technical requirements and working with a team to deliver quality hardware.
Challenge norms in aerospace on implementing and executing on System Engineering functions
Have demonstrated experience as a technical specialist on specific spacecraft subsystems as well as system-level experience (Thermal, Structural, ADCS, RF Link, etc)
Have demonstrated experience in small satellite assembly, integration and test campaigns
Have experience in a fast-paced development environment.
Have prior experience delivering a spacecraft to orbit and/or space-qualified hardware to a customer"
Then "Nice to Haves:
Current in-scope DoD SECRET background investigation with at least 3 years of eligibility remaining, or Continuous Evaluation (CE) status, with willingness and ability to obtain a Top Secret clearance
DoD or Intelligence Community Top Secret background investigation with at least 3 years of eligibility remaining or CE status; and SCI eligibility with current experience in SCI programs, other control systems, and/or Special Access Programs
You have 5 years of experience as a systems engineer or similar in the space industry
Preferred: Experience on RF and/or Electrical subsystems
Preferred: Proficient with STK Plus: Experience with thermal/structural analysis"
Thus Must Haves are requirements. Nice to Haves are qualifications/preferred skills.
We could map:
- Requirements: Must Haves (list)
- Qualifications: Nice to Haves (list)
- Skills: maybe the Preferred items (RF/Electrical, STK, thermal/structural) could be under Skills. But we could also put them under Qualifications. Since we have both Qualifications and Skills headings allowed, we could separate: Qualifications: years of experience, background investigation etc. Skills: RF/Electrical, STK, thermal/structural.
But we need to avoid thin sections. Perhaps combine Qualifications and Skills into one section "Qualifications" that includes both nice-to-haves and skills. However the instruction says prefer a few substantive sections over many thin ones. So we could have: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We can omit Skills separately.
Thus:
About the role
-> include company description and "About This Role:" paragraph.
Responsibilities
-> the paragraph about intersection etc.
Requirements
-> Must Haves list.
Qualifications
-> Nice to Haves list (including years of experience, background investigation, preferred experience etc.)
Benefits
-> list of benefits.
Pay
-> Salary Range.
We must not include Schedule.
We must not include boilerplate like EEO, accessibility, third-party recruiters, etc.
We must preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus for About the role and Responsibilities we use
. For Requirements, Qualifications, Benefits we use
- . For Pay we could use
(since it's a single line). Or could be
but it's not a list; but instruction says use - for any list of duties/requirements/benefits. Pay is not a list, so
is fine.
Now we need to extract exact text.
Let's capture About the role content:
From posting:
"About Loft Federal Loft Federal is committed to delivering the U.S. national security space community a fast, affordable, and streamlined pathway to orbit. As a wholly owned U.S. subsidiary of Loft Orbital Solutions, Inc., we specialize in providing mission-ready space infrastructure with unmatched efficiency. At Loft, we empower our team with autonomy, ownership, and bold problem-solving opportunities while fostering a tight-knit, supportive environment. We believe that diversity, inclusivity, and community are the foundation of an open and innovative culture. We value kind, collaborative, and mission-driven teammates who excel in problem-solving and communication—because great solutions come from great teams. Are you ready to embark on this exciting journey with us? Senior Satellite Systems Engineer Loft Federal provides space infrastructure and operation as a service for whatever size mission a client needs - whether that's a constellation, a single satellite, or even flying multiple customer payloads on the same satellite. As a Senior Satellite System Engineer of Loft's mission team, you will work on multiple satellite missions simultaneously, each with a unique, multi-payload configuration. You will work cross-functionally across multiple Loft teams: satellite operation software, payload interface software, mission engineering and AIT. About This Role: In this role, you’ll work at the intersection of engineering, customers, and program execution to help turn mission needs into successful spacecraft. You’ll collaborate with internal teams and customers to develop and manage technical budgets, system requirements, and verification approaches, while helping shape and evolve mission concepts of operations (CONOPS) and supporting customer Service Level Agreements. You’ll also have the opportunity to contribute to program and product management, including working directly with customers on programmatic and schedule matters. Alongside your teammates, you’ll develop interface specifications, CONOPS, and other key design documentation, then bring that work into the real world by supporting test procedures and participating in spacecraft integration and test campaigns at our manufacturer’s facility."
We need to avoid repeating the job title as a heading. The job title "Senior Satellite Systems Engineer" appears in the text; we should keep it as part of the prose? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can keep it in the paragraph but not as heading. It's okay.
Thus About the role section will contain the company description and the role description up to "About This Role:"? Actually "About This Role:" is a subheading but we treat as part of About the role. We'll include the paragraph after that as part of About the role? But we also have a separate Responsibilities section. The responsibilities are the sentences after "About This Role:"? Actually the responsibilities are the same as the paragraph after "About This Role:"? Let's see: The paragraph after "About This Role:" includes responsibilities. So we could treat About the role as just company description, and Responsibilities as the paragraph after "About This Role:".
Thus we need to split:
About the role: company description (first paragraph up to "Are you ready to embark on this exciting journey with us?" maybe includes that sentence). Then after that we have "Senior Satellite Systems Engineer Loft Federal provides space infrastructure..." That seems like role overview. But we could include that in About the role as well. However we have a separate Responsibilities section for the detailed responsibilities. To avoid duplication, we need to decide what goes where.
Better: About the role: company description + brief role overview (the sentences about Loft Federal provides space infrastructure... and the cross-functional teams). Responsibilities: the detailed bullet-like paragraph after "About This Role:".
Thus:
About the role content:
"About Loft Federal Loft Federal is committed to delivering the U.S. national security space community a fast, affordable, and streamlined pathway to orbit. As a wholly owned U.S. subsidiary of Loft Orbital Solutions, Inc., we specialize in providing mission-ready space infrastructure with unmatched efficiency. At Loft, we empower our team with autonomy, ownership, and bold problem-solving opportunities while fostering a tight-knit, supportive environment. We believe that diversity, inclusivity, and community are the foundation of an open and innovative culture. We value kind, collaborative, and mission-driven teammates who excel in problem-solving and communication—because great solutions come from great teams. Are you ready to embark on this exciting journey with us? Senior Satellite Systems Engineer Loft Federal provides space infrastructure and operation as a service for whatever size mission a client needs - whether that's a constellation, a single satellite, or even flying multiple customer payloads on the same satellite. As a Senior Satellite System Engineer of Loft's mission team, you will work on multiple satellite missions simultaneously, each with a unique, multi-payload configuration. You will work cross-functionally across multiple Loft teams: satellite operation software, payload interface software, mission engineering and AIT."
That seems good.
Responsibilities content:
"In this role, you’ll work at the intersection of engineering, customers, and program execution to help turn mission needs into successful spacecraft. You’ll collaborate with internal teams and customers to develop and manage technical budgets, system requirements, and verification approaches, while helping shape and evolve mission concepts of operations (CONOPS) and supporting customer Service Level Agreements. You’ll also have the opportunity to contribute to program and product management, including working directly with customers on programmatic and schedule matters. Alongside your teammates, you’ll develop interface specifications, CONOPS, and other key design documentation, then bring that work into the real world by supporting test procedures and participating in spacecraft integration and test campaigns at our manufacturer’s facility."
for prose. Thus for About the role and Responsibilities we use
. For Requirements, Qualifications, Benefits we use
- . For Pay we could use
(since it's a single line). Or could be
- but it's not a list; but instruction says use
- for any list of duties/requirements/benefits. Pay is not a list, so
is fine. Now we need to extract exact text. Let's capture About the role content: From posting: "About Loft Federal Loft Federal is committed to delivering the U.S. national security space community a fast, affordable, and streamlined pathway to orbit. As a wholly owned U.S. subsidiary of Loft Orbital Solutions, Inc., we specialize in providing mission-ready space infrastructure with unmatched efficiency. At Loft, we empower our team with autonomy, ownership, and bold problem-solving opportunities while fostering a tight-knit, supportive environment. We believe that diversity, inclusivity, and community are the foundation of an open and innovative culture. We value kind, collaborative, and mission-driven teammates who excel in problem-solving and communication—because great solutions come from great teams. Are you ready to embark on this exciting journey with us? Senior Satellite Systems Engineer Loft Federal provides space infrastructure and operation as a service for whatever size mission a client needs - whether that's a constellation, a single satellite, or even flying multiple customer payloads on the same satellite. As a Senior Satellite System Engineer of Loft's mission team, you will work on multiple satellite missions simultaneously, each with a unique, multi-payload configuration. You will work cross-functionally across multiple Loft teams: satellite operation software, payload interface software, mission engineering and AIT. About This Role: In this role, you’ll work at the intersection of engineering, customers, and program execution to help turn mission needs into successful spacecraft. You’ll collaborate with internal teams and customers to develop and manage technical budgets, system requirements, and verification approaches, while helping shape and evolve mission concepts of operations (CONOPS) and supporting customer Service Level Agreements. You’ll also have the opportunity to contribute to program and product management, including working directly with customers on programmatic and schedule matters. Alongside your teammates, you’ll develop interface specifications, CONOPS, and other key design documentation, then bring that work into the real world by supporting test procedures and participating in spacecraft integration and test campaigns at our manufacturer’s facility." We need to avoid repeating the job title as a heading. The job title "Senior Satellite Systems Engineer" appears in the text; we should keep it as part of the prose? The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can keep it in the paragraph but not as heading. It's okay. Thus About the role section will contain the company description and the role description up to "About This Role:"? Actually "About This Role:" is a subheading but we treat as part of About the role. We'll include the paragraph after that as part of About the role? But we also have a separate Responsibilities section. The responsibilities are the sentences after "About This Role:"? Actually the responsibilities are the same as the paragraph after "About This Role:"? Let's see: The paragraph after "About This Role:" includes responsibilities. So we could treat About the role as just company description, and Responsibilities as the paragraph after "About This Role:". Thus we need to split: About the role: company description (first paragraph up to "Are you ready to embark on this exciting journey with us?" maybe includes that sentence). Then after that we have "Senior Satellite Systems Engineer Loft Federal provides space infrastructure..." That seems like role overview. But we could include that in About the role as well. However we have a separate Responsibilities section for the detailed responsibilities. To avoid duplication, we need to decide what goes where. Better: About the role: company description + brief role overview (the sentences about Loft Federal provides space infrastructure... and the cross-functional teams). Responsibilities: the detailed bullet-like paragraph after "About This Role:". Thus: About the role content: "About Loft Federal Loft Federal is committed to delivering the U.S. national security space community a fast, affordable, and streamlined pathway to orbit. As a wholly owned U.S. subsidiary of Loft Orbital Solutions, Inc., we specialize in providing mission-ready space infrastructure with unmatched efficiency. At Loft, we empower our team with autonomy, ownership, and bold problem-solving opportunities while fostering a tight-knit, supportive environment. We believe that diversity, inclusivity, and community are the foundation of an open and innovative culture. We value kind, collaborative, and mission-driven teammates who excel in problem-solving and communication—because great solutions come from great teams. Are you ready to embark on this exciting journey with us? Senior Satellite Systems Engineer Loft Federal provides space infrastructure and operation as a service for whatever size mission a client needs - whether that's a constellation, a single satellite, or even flying multiple customer payloads on the same satellite. As a Senior Satellite System Engineer of Loft's mission team, you will work on multiple satellite missions simultaneously, each with a unique, multi-payload configuration. You will work cross-functionally across multiple Loft teams: satellite operation software, payload interface software, mission engineering and AIT." That seems good. Responsibilities content: "In this role, you’ll work at the intersection of engineering, customers, and program execution to help turn mission needs into successful spacecraft. You’ll collaborate with internal teams and customers to develop and manage technical budgets, system requirements, and verification approaches, while helping shape and evolve mission concepts of operations (CONOPS) and supporting customer Service Level Agreements. You’ll also have the opportunity to contribute to program and product management, including working directly with customers on programmatic and schedule matters. Alongside your teammates, you’ll develop interface specifications, CONOPS, and other key design documentation, then bring that work into the real world by supporting test procedures and participating in spacecraft integration and test campaigns at our manufacturer’s facility."
- for any list of duties/requirements/benefits. Pay is not a list, so