Ground Software Engineer Senior - (Security Clearance; Field-Based)
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the "How To Apply", EEO statement, etc. Also remove "Prior Space-industry Experience Is Not Required."? That's substantive? It's a statement about requirement; we should keep it maybe under Responsibilities? Actually it's a note; we could keep as a paragraph under About the role or Responsibilities? It's about experience not required. It's substantive; we should keep it. But it's not a list; we can put as a
.
We need to preserve details like technologies: React/TypeScript, C# .NET, Docker, Kafka, REST, MSSQL, InfluxDB, Python, etc. Also list responsibilities items.
We need to format lists.
Let's extract content:
Company intro: "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."
Then "About The Work" heading but we should not repeat job title as heading. We'll treat as About the role content. The "About The Work" bullet list:
- 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
Then "Your work will be deployed in a MOC where it will directly support active missions in orbit."
Then "Prior Space-industry Experience Is Not Required."
Then "Position Details" with subpoints: Team structure, Remote Policy, On-Site Travel, On-Call. Those are details; we could incorporate into About the role or Responsibilities? Probably they belong to About the role or maybe a separate section like "Position Details" but not in allowed headings. We could fold into About the role as prose.
Then "Key Responsibilities" list:
- 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
Then "Team Leadership" subheading under Responsibilities? It's part of responsibilities. We could include as bullet points under Responsibilities as well.
Team Leadership bullets:
- 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
Then "Required Qualifications" list:
- 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
Then "Preferred Qualifications" list:
- 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
Then "Benefits" paragraph:
"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."
We need to output HTML fragment only.
We must not include markdown fences.
We'll produce:
About the role
... (company intro + about the work bullets? Actually the bullets are responsibilities? But we have separate Responsibilities section. The "About The Work" bullets are more about work tasks; could be considered responsibilities. But we already have Responsibilities section with detailed list. To avoid duplication, we could merge the "About The Work" bullets into About the role as prose? But they are specific tasks; maybe better to include them under Responsibilities as they are duties. However the instructions: Use
- for any list of duties/requirements/benefits. So we should put duties in Responsibilities. The "About The Work" list is duties. So we should include them in Responsibilities. The Key Responsibilities list also duties. We can combine them into one Responsibilities list, preserving all items. We'll need to ensure we don't duplicate. Let's combine both sets.
Responsibilities items:
From About The Work:
- 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
From 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
From 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
We'll combine all into one
.
Now About the role prose: we need to include company intro and role description (embedded at MOC, autonomy, etc.) plus maybe Position Details (team structure, remote policy, travel, on-call) and note about prior space industry experience not required. We'll put that in About the role paragraph(s). Could be multiple elements.
We must not repeat job title as heading. Already not.
Now Required Qualifications list as
.
Preferred Qualifications list as .
Benefits as .
We must not include Pay or Schedule sections.
Now ensure we preserve all specifics: mention technologies, etc.
Let's craft HTML.
We'll need to escape any special characters? Not needed.
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
for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to strip the "How To Apply", EEO statement, etc. Also remove "Prior Space-industry Experience Is Not Required."? That's substantive? It's a statement about requirement; we should keep it maybe under Responsibilities? Actually it's a note; we could keep as a paragraph under About the role or Responsibilities? It's about experience not required. It's substantive; we should keep it. But it's not a list; we can put as a
. We need to preserve details like technologies: React/TypeScript, C# .NET, Docker, Kafka, REST, MSSQL, InfluxDB, Python, etc. Also list responsibilities items. We need to format lists. Let's extract content: Company intro: "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." Then "About The Work" heading but we should not repeat job title as heading. We'll treat as About the role content. The "About The Work" bullet list: - 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 Then "Your work will be deployed in a MOC where it will directly support active missions in orbit." Then "Prior Space-industry Experience Is Not Required." Then "Position Details" with subpoints: Team structure, Remote Policy, On-Site Travel, On-Call. Those are details; we could incorporate into About the role or Responsibilities? Probably they belong to About the role or maybe a separate section like "Position Details" but not in allowed headings. We could fold into About the role as prose. Then "Key Responsibilities" list: - 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 Then "Team Leadership" subheading under Responsibilities? It's part of responsibilities. We could include as bullet points under Responsibilities as well. Team Leadership bullets: - 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 Then "Required Qualifications" list: - 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 Then "Preferred Qualifications" list: - 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 Then "Benefits" paragraph: "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." We need to output HTML fragment only. We must not include markdown fences. We'll produce:
About the role
... (company intro + about the work bullets? Actually the bullets are responsibilities? But we have separate Responsibilities section. The "About The Work" bullets are more about work tasks; could be considered responsibilities. But we already have Responsibilities section with detailed list. To avoid duplication, we could merge the "About The Work" bullets into About the role as prose? But they are specific tasks; maybe better to include them under Responsibilities as they are duties. However the instructions: Use
- for any list of duties/requirements/benefits. So we should put duties in Responsibilities. The "About The Work" list is duties. So we should include them in Responsibilities. The Key Responsibilities list also duties. We can combine them into one Responsibilities list, preserving all items. We'll need to ensure we don't duplicate. Let's combine both sets.
Responsibilities items:
From About The Work:
- 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
From 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
From 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
We'll combine all into one
- .
Now About the role prose: we need to include company intro and role description (embedded at MOC, autonomy, etc.) plus maybe Position Details (team structure, remote policy, travel, on-call) and note about prior space industry experience not required. We'll put that in About the role paragraph(s). Could be multiple
elements. We must not repeat job title as heading. Already not. Now Required Qualifications list as
- .
Preferred Qualifications list as
- .
Benefits as
. We must not include Pay or Schedule sections. Now ensure we preserve all specifics: mention technologies, etc. Let's craft HTML. We'll need to escape any special characters? Not needed. 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