Ground System Integration Engineer
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have real content. - About the role: maybe a brief overview? The posting starts with "What You’ll Be Doing ..." which is responsibilities. Could treat that as About the role? But we also have Responsibilities section. We can combine? The instruction: Prefer a few substantive sections over many thin ones. So we could have sections: Responsibilities, Tech Skills, Soft Skills, Background Qualifications, Benefits, Pay, Schedule. But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit sections that lack content. So we need to include only those with real content. We have content for Responsibilities (the bullet list of duties). We have Tech Skills (list). We have Soft Skills (list). We have Background Qualifications (education, experience, clearance). We have Benefits (list). We have Pay (Compensation Range). We have Schedule (hybrid role 2-3 days in-office). We might not have a separate "About the role" distinct from responsibilities; but we could include a short paragraph summarizing role. However we must not repeat job title as heading. Could put a short
under About the role summarizing the role: developing and integrating software Command & Control solutions for satellite vehicles, etc. That is present in first paragraph. So we can put that as About the role. Requirements: maybe we could combine Background Qualifications and Requirements? But we have separate sections: Requirements and Qualifications. The posting has "Background Qualifications". Could treat that as Qualifications. Requirements maybe could be the tech skills? But we already have Skills. Could treat Tech Skills as Skills. Soft Skills maybe also under Skills? But we have separate Soft Skills list; we could put under Skills as well but we have separate heading Skills (maybe combine both). However we need to follow instruction: Use headings only when posting has real, specific content for it. So we can have Skills heading and include both tech and soft skills under it (maybe separate
- lists). Or we could have Skills for tech and Soft Skills separate? The allowed headings list includes Skills but not Soft Skills. So we should put soft skills under Skills as well, maybe separate sub-lists? But we cannot invent headings not allowed. So we will have Skills heading containing both technical and soft skills bullet lists.
Requirements: Could be the background qualifications (education, experience, clearance). But we also have Qualifications heading. Might be redundant. We could treat Requirements as the mandatory items (education, experience, clearance) and Qualifications as preferred? However posting lumps them together under Background Qualifications. To avoid thin sections, we could combine Requirements and Qualifications into one section, maybe using Qualifications heading (since it's more natural). But we need to decide.
We have Pay heading: compensation range.
Schedule heading: hybrid role.
Benefits heading: list.
Thus we could have sections: About the role, Responsibilities, Skills, Qualifications, Benefits, Pay, Schedule.
Check if any content missing: About the role: we have first paragraph describing role. Responsibilities: we have bullet list of duties (developing and integrating software Command & Control solutions, working with customer stakeholders, etc). Actually the first paragraph already includes responsibilities. But we can still separate: About the role could be a brief overview; Responsibilities could be detailed list.
Let's extract responsibilities: "You will be responsible for developing and integrating software Command & Control solutions for satellite vehicles as well as working with customer stakeholders to decompose mission requirements and engineer solutions with existing products. The successful candidate will have very strong software integration and debugging skills and deep experience in low level software integration with hardware (satellites or other!). You will bring or build expertise with C2 concepts and common industry standards and protocols such as CCSDS, CSP, CFDP, XTCE, and MIB. Your primary responsibility will be integrating new satellites and flight software into Quindar’s mission management platform and you will collaborate with a multidisciplinary team to do this while supporting development and integration of solutions into Quindar’s broader product suite. Ultimately, you will contribute to Quindar’s mission of simplifying operations and allowing our customers to utilize their satellites like servers!"
That's a lot of prose; we can put as
- Technical skills: maybe we can separate? But we need bullet list of duties/requirements/benefits. For skills we can have nested lists? Simpler: just bullet each skill item. We'll separate technical and soft maybe as subheadings? Not allowed. Could just list all. Thus:
- Proficiency in programming languages such as Python, C++, or Java
- Experience developing real-time embedded software and/or integrating hardware assets with mission management software
- Preferred experience with satellite communication protocols such as CCSDS, CSP, CFDP, IP and data processing algorithms
- Preferred understanding of standardized command and telemetry definitions such as XTCE and MIB or similar concepts from other industries
- Understanding of encryption algorithms such as AES-256 GCM, AES-256 CFB, AES-256 ECB, NSA Type 1 PEGASUS, NSA Type 1 CARIBOU
- Preferred experience with AWS services such as Lambda, ECS, EKS, CloudWatch, S3, EFS/EBS, EC2, and RDS
- Familiarity with Git and GitHub or similar framework for version control
- Preference for experience with open source software
- Deep technical analysis and troubleshooting skills
- Highly adaptable; you will integrate a wide variety of missions into Quindar’s software and will need to find creative solutions to work through unknowns and unforeseen challenges quickly
- A foresight for scalability and proliferation of C2
- Independent self‑starter; able to complete projects on time with minimal guidance
- A high standard for software maintainability, quality, resilience, and performance
- Strong cross‑functional communication and ability to distill complex information for internal and customer‑facing audiences
- Bachelor’s degree in Computer Science, Electrical Engineering, or related field
- 3+ years of professional experience with satellite command and control systems or similarly complex hardware‑software integration efforts
- Ability to obtain a U.S. Security Clearance
- To conform to U.S. Government export regulations, applicant must be a (i) U.S. citizen or national, (ii) U.S. lawful permanent resident (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.
- Work‑life balance: employees required to take 15 days off but provided unlimited PTO and most US federal holidays
- Quarterly health & wellness benefits
- Comprehensive health insurance for employee and family with 100% coverage
- 4% 401(k) matching
- Annual 4‑day company offsite (past locations: San Francisco, Nashville, Denver, Santa Fe, New Orleans, San Diego)
- Opportunity
under Responsibilities. Tech skills list: "Proficiency in programming languages such as Python, C++, or JavaExperience developing real-time embedded software and/or integrating hardware assets with mission management softwarePreferred experience with satellite communication protocols such as CCSDS, CSP, CFDP, IP and data processing algorithmsPreferred understanding of standardized command and telemetry definitions such as XTCE and MIB or similar concepts from other industriesUnderstanding of encryption algorithms such as AES-256 GCM, AES-256 CFB, AES-256 ECB, NSA Type 1 PEGASUS, NSA Type 1 CARIBOUPreferred experience with AWS services such as Lambda, ECS, EKS, CloudWatch, S3, EFS/EBS, EC2, and RDSFamiliarity with Git and GitHub or similar framework for version controlPreference for experience with open source software" We need to split into bullet items. Soft skills list: "Deep technical analysis and troubleshooting skillsHighly adaptable; you will integrate a wide variety of missions into Quindar’s software and will need to find creative solutions to work through unknowns and unforeseen challenges quicklyA foresight for scalability and proliferation of c2Independent self-starter; able to complete projects on time with minimal guidanceA high standard for software maintainability, quality, resilience, and performanceStrong cross-functional communication and ability to distill complex information for internal and customer-facing audiences" We'll bullet those. Background Qualifications: "Bachelor’s degree in Computer Science, Electrical Engineering, or related field3+ years [professional] experience with satellite command and control systems or similarly complex hardware-software integration effortsAbility to obtain a U.S. Security Clearance 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 the ITAR here." We need to keep that content but maybe drop the "Learn more about the ITAR here." as it's a link? It's boilerplate? Might be considered minor metadata; but it's part of qualifications. We'll keep the sentence but maybe drop the link text? It's not boilerplate; it's a reference. We'll keep. Benefits: "We take work life balance very seriously. We require employees to take 15 days off but provide unlimited PTO and follow most US federal government holidays. Mental health is just as important as physical so we provide quarterly health & wellness benefits. Comprehensive health insurance for you and your family with 100% coverage for employees. We encourage employees to save for retirement and provide 4% 401(k) matching. Each year we have a 4-day company offsite. Previous locations include San Francisco, Nashville, Denver, Santa Fe, New Orleans, and San Diego. Our culture and company is evolving. You will be key in creating the next major or minor version!" We need to put as bullet list? Could be prose
. But we can make bullet list for each benefit. Pay: "Compensation Range: $110K - $170K" Schedule: "This is a hybrid role with 2-3 days in-office in Arvada, CO. We aim to maximize benefits of having in-person collaboration spaces while also working on a flexible schedule with a large amount of remote work!" Now produce HTML. We must not include or . Just fragment. We'll structure:
About the role
...
Responsibilities
...