Ground Software Engineer Senior - (Security Clearance; Field-Based)
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "How To Apply" and EEO statements. Also remove "Prior Space-industry Experience Is Not Required." That's substantive? It's a statement about requirement; we can keep maybe under Requirements? It's a note that prior space industry experience not required. Could be included under Requirements or Qualifications. We'll decide.
We need sections: About the role (maybe from first paragraph about York and role). Responsibilities (list). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications). Skills (maybe list of skills). Benefits (they gave benefits). Pay and Schedule: not provided, so we should NOT include those sections.
We must not create sections with filler. So include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like: York Space Systems founded..., mission, etc. Also mention remote policy, on-call, travel, etc. Also mention team structure, etc. Also mention key responsibilities list. Also mention required qualifications list. Also mention preferred qualifications list. Also mention benefits list.
We need to be careful not to duplicate content. Let's parse the posting.
Original text:
"York Space Systems was founded to radically improve spacecraft affordability and reliability, transforming, and enabling next- generation space mission operations worldwide. Today, York is one of the most innovative aerospace companies, specializing in end-to-end customer solutions and the rapid production of spacecraft platforms. York’s complete Space Segment Solution includes spacecraft production, payload integration, system integration & test, launch services, ground segment services, and mission operations, enabling customers to leverage York’s existing technology solutions to get to orbit rapidly and responsively. We’re looking to expand our team across the board. We are looking for a Senior Full Stack Software Engineer who thrives working independently and is passionate about building software that pushes the bounds of what's possible. Our software is a modern web-based application (React/TypeScript, C# .NET) with a microservice infrastructure (Docker, Kafka, REST) that operators use to monitor and control constellations of spacecraft across several active missions. In this role, you will be embedded at or near a Mission Operation Center (MOC) local to you, serving as the primary technical point of contact for that facility. You'll operate with a high degree of autonomy — often as a team of one or two — while staying closely integrated with our primary office in Denver, CO for feature development, technical direction, and longer-term project work. This is not a traditional office role. You must be comfortable owning problems end-to-end without immediate peer support, communicating proactively across time zones, and context-switching between hands-on operational support and collaborative product development. About The Work You'll work closely with satellite operators, customers, and the Denver engineering and UI/UX teams to tackle hard problems like: Collision avoidance, conjunction analysis, and orbit-raising maneuver planning Operation center failover and continuity of control Cross-satellite network maintenance and space-to-ground link management Ground station contact scheduling and pass optimization Multi-vehicle mission coordination Your work will be deployed in a MOC where it will directly support active missions in orbit. Prior Space-industry Experience Is Not Required. Position Details Team structure: Field-based; typically 1–2 engineers on-site, integrated with a remote team of 6–8 developers Remote Policy: On-Site Travel: Must be willing and able to travel to Denver, CO for onboarding, training, and periodic team collaboration On-Call: Must be available for on-call support to serve the MOC local to you Key Responsibilities Serve as the primary technical resource for your local MOC, providing direct support to operators and resolving issues with a high degree of independence Provide on-call support for mission-critical operations by responding to incidents and escalations at your assigned facility Integrate remotely with the Denver ground software teams for feature development, longer-term technical work, sprint ceremonies, and cross-team coordination Develop key user-facing features to support both current and future missions using TypeScript, React, C#, MSSQL, InfluxDB, Kafka, and Python Translate designs and requirements into high-quality, maintainable code Build reusable components, shared libraries, and scalable services for use across the platform Engineer algorithms and business logic to promote scalability and automation Write unit and integration tests, including tests against simulation tools to validate behavior against realistic mission scenarios Write documentation for internal users and customers Team Leadership Act as the technical face of the engineering team at your local site, building strong relationships with operators and customers Mentor junior engineers (on-site or remote) through code reviews, pair programming, and design discussions Contribute to sprint planning, technical scoping, and cross-team alignment with the distributed engineering organization Communicate proactively and clearly with remote teammates. Written communication and async collaboration are essential in this role Help establish and advocate for engineering best practices across the team Required Qualifications Bachelor's degree in Computer Science or related field 6+ years of full-stack software engineering experience Active Secret security clearance Demonstrated ability to work independently with minimal day-to-day supervision and comfort operating as a primary technical resource without immediate peer support Strong remote collaboration skills with experience working effectively as part of a geographically distributed team, including async communication and documentation habits Demonstrated ability to independently troubleshoot and resolve deployment failures, runtime issues, and environment-specific defects, including in isolated and/or air-gapped environments without immediate escalation paths Deep expertise in strongly typed backend languages, particularly C#, including multithreaded applications, concurrency patterns, and near-realtime data handling Experience designing and consuming REST APIs at scale Experience with SQL databases, including schema design and query optimization Experience with Git in a collaborative, multi-contributor environment Willingness and ability to provide on-call support for operational facilities Ability to travel to Denver, CO for onboarding, training, and periodic team visits Strong verbal and written communication skills, including presenting technical concepts to non-technical audiences Proven ability to thrive in a fast-paced, mission-driven environment with ambiguous requirements Preferred Qualifications Eligibility for Top Secret security clearance Proficiency in modern React and its core principles, including component architecture and performance optimization Proficiency with common front-end tooling such as Yarn, Babel, or Material-UI Experience working across a polyglot stack including Python, Kafka, and InfluxDB Experience with modern state management tools such as TanStack Query Experience designing and executing forward and backward compatible database migrations and deployment strategies in live production environments Experience with feature flagging strategies, including gradual rollouts, environment-based toggles, and flag lifecycle management Experience with container-based installation and deployment strategies, including Docker and CI/CD pipeline integration Benefits In addition to compensation, York Space Systems is proud to offer a comprehensive benefits package including medical, dental, and vision insurance along with PTO and a 401K. How To Apply ..."
We need to remove How To Apply and EEO statements.
Now we need to structure.
Section About the role: Could combine the introductory paragraphs about York and the role description up to "About The Work". But we have a separate "About The Work" heading in the posting; but we are to use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. So we can treat "About the role" as general overview. Could include the description of York, the role, the work description (the bullet list of hard problems). Also maybe include team structure, remote policy, on-call, travel. Those could be part of About the role or maybe under Responsibilities? But they are more about position details. We could include them under About the role.
Responsibilities: list from "Key Responsibilities" and "Team Leadership" bullet points.
Requirements: maybe the "Required Qualifications" list.
Qualifications: maybe the "Preferred Qualifications" list.
Skills: Could be a separate section for technical skills? But we already have required and preferred qualifications which include many skills. The instruction says use sections like Skills if there is real specific content. We could create a Skills section summarizing the technical stack: React/TypeScript, C# .NET, Docker, Kafka, REST, MSSQL, InfluxDB, Python, etc. However that may duplicate content from qualifications. But we can still include a Skills section if we have specific content not covered elsewhere. However we must not invent or summarize away detail; we can list the technologies mentioned. That's not summarizing away detail; it's extracting. But we need to preserve all substantive information; if we put them in Skills, we still need to keep them elsewhere? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but we should avoid losing info. If we put them in Skills and also keep them in Required/Preferred, that's duplication but okay. However we might avoid duplication by moving some details to Skills and removing from qualifications? That would be summarizing away detail (removing). So better to keep qualifications as is and maybe not add a Skills section unless there is distinct skill list not already captured. The posting already lists many skills in qualifications. So we could skip Skills section to avoid thin sections. But the instruction says "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed.
Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits.
We need to ensure we don't include Pay or Schedule.
Now we need to format.
We'll produce:
About the role
York Space Systems was founded to radically improve spacecraft affordability and reliability, transforming, and enabling next‑generation space mission operations worldwide. Today, York is one of the most innovative aerospace companies, specializing in end‑to‑end customer solutions and the rapid production of spacecraft platforms. York’s complete Space Segment Solution includes spacecraft production, payload integration, system integration & test, launch services, ground segment services, and mission operations, enabling customers to leverage York’s existing technology solutions to get to orbit rapidly and responsibly. We’re looking to expand our team across the board. We are looking for a Senior Full Stack Software Engineer who thrives working independently and is passionate about building software that pushes the bounds of what's possible. Our software is a modern web‑based application (React/TypeScript, C# .NET) with a microservice infrastructure (Docker, Kafka, REST) that operators use to monitor and control constellations of spacecraft across several active missions. In this role, you will be embedded at or near a Mission Operation Center (MOC) local to you, serving as the primary technical point of contact for that facility. You'll operate with a high degree of autonomy — often as a team of one or two — while staying closely integrated with our primary office in Denver, CO for feature development, technical direction, and longer‑term project work. This is not a traditional office role. You must be comfortable owning problems end‑to‑end without immediate peer support, communicating proactively across time zones, and context‑switching between hands‑on operational support and collaborative product development. You'll work closely with satellite operators, customers, and the Denver engineering and UI/UX teams to tackle hard problems like: collision avoidance, conjunction analysis, and orbit‑raising maneuver planning; operation center failover and continuity of control; cross‑satellite network maintenance and space‑to‑ground link management; ground station contact scheduling and pass optimization; multi‑vehicle mission coordination. Your work will be deployed in a MOC where it will directly support active missions in orbit. Prior space‑industry experience is not required. Position details: field‑based; typically 1–2 engineers on‑site, integrated with a remote team of 6–8 developers. Remote policy: must be willing and able to travel to Denver, CO for onboarding, training, and periodic team collaboration. On‑call: must be available for on‑call support to serve the
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include details like: York Space Systems founded..., mission, etc. Also mention remote policy, on-call, travel, etc. Also mention team structure, etc. Also mention key responsibilities list. Also mention required qualifications list. Also mention preferred qualifications list. Also mention benefits list. We need to be careful not to duplicate content. Let's parse the posting. Original text: "York Space Systems was founded to radically improve spacecraft affordability and reliability, transforming, and enabling next- generation space mission operations worldwide. Today, York is one of the most innovative aerospace companies, specializing in end-to-end customer solutions and the rapid production of spacecraft platforms. York’s complete Space Segment Solution includes spacecraft production, payload integration, system integration & test, launch services, ground segment services, and mission operations, enabling customers to leverage York’s existing technology solutions to get to orbit rapidly and responsively. We’re looking to expand our team across the board. We are looking for a Senior Full Stack Software Engineer who thrives working independently and is passionate about building software that pushes the bounds of what's possible. Our software is a modern web-based application (React/TypeScript, C# .NET) with a microservice infrastructure (Docker, Kafka, REST) that operators use to monitor and control constellations of spacecraft across several active missions. In this role, you will be embedded at or near a Mission Operation Center (MOC) local to you, serving as the primary technical point of contact for that facility. You'll operate with a high degree of autonomy — often as a team of one or two — while staying closely integrated with our primary office in Denver, CO for feature development, technical direction, and longer-term project work. This is not a traditional office role. You must be comfortable owning problems end-to-end without immediate peer support, communicating proactively across time zones, and context-switching between hands-on operational support and collaborative product development. About The Work You'll work closely with satellite operators, customers, and the Denver engineering and UI/UX teams to tackle hard problems like: Collision avoidance, conjunction analysis, and orbit-raising maneuver planning Operation center failover and continuity of control Cross-satellite network maintenance and space-to-ground link management Ground station contact scheduling and pass optimization Multi-vehicle mission coordination Your work will be deployed in a MOC where it will directly support active missions in orbit. Prior Space-industry Experience Is Not Required. Position Details Team structure: Field-based; typically 1–2 engineers on-site, integrated with a remote team of 6–8 developers Remote Policy: On-Site Travel: Must be willing and able to travel to Denver, CO for onboarding, training, and periodic team collaboration On-Call: Must be available for on-call support to serve the MOC local to you Key Responsibilities Serve as the primary technical resource for your local MOC, providing direct support to operators and resolving issues with a high degree of independence Provide on-call support for mission-critical operations by responding to incidents and escalations at your assigned facility Integrate remotely with the Denver ground software teams for feature development, longer-term technical work, sprint ceremonies, and cross-team coordination Develop key user-facing features to support both current and future missions using TypeScript, React, C#, MSSQL, InfluxDB, Kafka, and Python Translate designs and requirements into high-quality, maintainable code Build reusable components, shared libraries, and scalable services for use across the platform Engineer algorithms and business logic to promote scalability and automation Write unit and integration tests, including tests against simulation tools to validate behavior against realistic mission scenarios Write documentation for internal users and customers Team Leadership Act as the technical face of the engineering team at your local site, building strong relationships with operators and customers Mentor junior engineers (on-site or remote) through code reviews, pair programming, and design discussions Contribute to sprint planning, technical scoping, and cross-team alignment with the distributed engineering organization Communicate proactively and clearly with remote teammates. Written communication and async collaboration are essential in this role Help establish and advocate for engineering best practices across the team Required Qualifications Bachelor's degree in Computer Science or related field 6+ years of full-stack software engineering experience Active Secret security clearance Demonstrated ability to work independently with minimal day-to-day supervision and comfort operating as a primary technical resource without immediate peer support Strong remote collaboration skills with experience working effectively as part of a geographically distributed team, including async communication and documentation habits Demonstrated ability to independently troubleshoot and resolve deployment failures, runtime issues, and environment-specific defects, including in isolated and/or air-gapped environments without immediate escalation paths Deep expertise in strongly typed backend languages, particularly C#, including multithreaded applications, concurrency patterns, and near-realtime data handling Experience designing and consuming REST APIs at scale Experience with SQL databases, including schema design and query optimization Experience with Git in a collaborative, multi-contributor environment Willingness and ability to provide on-call support for operational facilities Ability to travel to Denver, CO for onboarding, training, and periodic team visits Strong verbal and written communication skills, including presenting technical concepts to non-technical audiences Proven ability to thrive in a fast-paced, mission-driven environment with ambiguous requirements Preferred Qualifications Eligibility for Top Secret security clearance Proficiency in modern React and its core principles, including component architecture and performance optimization Proficiency with common front-end tooling such as Yarn, Babel, or Material-UI Experience working across a polyglot stack including Python, Kafka, and InfluxDB Experience with modern state management tools such as TanStack Query Experience designing and executing forward and backward compatible database migrations and deployment strategies in live production environments Experience with feature flagging strategies, including gradual rollouts, environment-based toggles, and flag lifecycle management Experience with container-based installation and deployment strategies, including Docker and CI/CD pipeline integration Benefits In addition to compensation, York Space Systems is proud to offer a comprehensive benefits package including medical, dental, and vision insurance along with PTO and a 401K. How To Apply ..." We need to remove How To Apply and EEO statements. Now we need to structure. Section About the role: Could combine the introductory paragraphs about York and the role description up to "About The Work". But we have a separate "About The Work" heading in the posting; but we are to use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. So we can treat "About the role" as general overview. Could include the description of York, the role, the work description (the bullet list of hard problems). Also maybe include team structure, remote policy, on-call, travel. Those could be part of About the role or maybe under Responsibilities? But they are more about position details. We could include them under About the role. Responsibilities: list from "Key Responsibilities" and "Team Leadership" bullet points. Requirements: maybe the "Required Qualifications" list. Qualifications: maybe the "Preferred Qualifications" list. Skills: Could be a separate section for technical skills? But we already have required and preferred qualifications which include many skills. The instruction says use sections like Skills if there is real specific content. We could create a Skills section summarizing the technical stack: React/TypeScript, C# .NET, Docker, Kafka, REST, MSSQL, InfluxDB, Python, etc. However that may duplicate content from qualifications. But we can still include a Skills section if we have specific content not covered elsewhere. However we must not invent or summarize away detail; we can list the technologies mentioned. That's not summarizing away detail; it's extracting. But we need to preserve all substantive information; if we put them in Skills, we still need to keep them elsewhere? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but we should avoid losing info. If we put them in Skills and also keep them in Required/Preferred, that's duplication but okay. However we might avoid duplication by moving some details to Skills and removing from qualifications? That would be summarizing away detail (removing). So better to keep qualifications as is and maybe not add a Skills section unless there is distinct skill list not already captured. The posting already lists many skills in qualifications. So we could skip Skills section to avoid thin sections. But the instruction says "Prefer a few substantive sections over many thin ones." So we can omit Skills if not needed. Thus sections: About the role, Responsibilities, Requirements (Required Qualifications), Qualifications (Preferred Qualifications), Benefits. We need to ensure we don't include Pay or Schedule. Now we need to format. We'll produce:
About the role
York Space Systems was founded to radically improve spacecraft affordability and reliability, transforming, and enabling next‑generation space mission operations worldwide. Today, York is one of the most innovative aerospace companies, specializing in end‑to‑end customer solutions and the rapid production of spacecraft platforms. York’s complete Space Segment Solution includes spacecraft production, payload integration, system integration & test, launch services, ground segment services, and mission operations, enabling customers to leverage York’s existing technology solutions to get to orbit rapidly and responsibly. We’re looking to expand our team across the board. We are looking for a Senior Full Stack Software Engineer who thrives working independently and is passionate about building software that pushes the bounds of what's possible. Our software is a modern web‑based application (React/TypeScript, C# .NET) with a microservice infrastructure (Docker, Kafka, REST) that operators use to monitor and control constellations of spacecraft across several active missions. In this role, you will be embedded at or near a Mission Operation Center (MOC) local to you, serving as the primary technical point of contact for that facility. You'll operate with a high degree of autonomy — often as a team of one or two — while staying closely integrated with our primary office in Denver, CO for feature development, technical direction, and longer‑term project work. This is not a traditional office role. You must be comfortable owning problems end‑to‑end without immediate peer support, communicating proactively across time zones, and context‑switching between hands‑on operational support and collaborative product development. You'll work closely with satellite operators, customers, and the Denver engineering and UI/UX teams to tackle hard problems like: collision avoidance, conjunction analysis, and orbit‑raising maneuver planning; operation center failover and continuity of control; cross‑satellite network maintenance and space‑to‑ground link management; ground station contact scheduling and pass optimization; multi‑vehicle mission coordination. Your work will be deployed in a MOC where it will directly support active missions in orbit. Prior space‑industry experience is not required. Position details: field‑based; typically 1–2 engineers on‑site, integrated with a remote team of 6–8 developers. Remote policy: must be willing and able to travel to Denver, CO for onboarding, training, and periodic team collaboration. On‑call: must be available for on‑call support to serve the