> Markdown version of [/jobs/ext/1211599-spacecraft-software-engineer](https://www.wearedevelopers.com/jobs/ext/1211599-spacecraft-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Spacecraft Software Engineer - **Company:** Orbital Astronautics Ltd - **Location:** Goring, UK - **Experience:** Experienced - **Salary:** £50,000.0 - £65,000.0 - **Contract:** Permanent contract - **Skills:** Automation of Tests, Unit Testing, Booting (BIOS), Configuration Management, Static Program Analysis, Code Review, Continuous Integration, Software Debugging, Embedded C, Firmware, Field-Programmable Gate Array (FPGA), Joint Test Action (IEEE Standards), Python (Programming Language), Key Management, MISRA C (C Programming Language), Requirements Traceability, Software Configuration Management, System on a Chip, Git, Integration Tests, Bare Metal, Operational Systems, Software Coding - **Published:** July 9, 2026 - **Apply:** https://uk.indeed.com/viewjob?jk=1f45a89b6cbcd8d2 ## About the Role * 4+ years of embedded C on ARM, ideally bare-metal or close to bare-metal. * 2+ years leading, mentoring, or technically guiding a small software team. * Embedded release engineering: bootloaders, secure boot, signed firmware, A/B rollback, anti-rollback, configuration control, and release gates. * Git-based review workflows and disciplined software configuration management. * CI/CD for embedded systems, including unit tests, integration tests, hardware-in-the-loop tests, and Python-based test harnesses. * Requirements traceability, coding standards, MISRA or equivalent static analysis, and strong review discipline. * TT&C, CCSDS, packet protocols, command handling, telemetry handling, and spacecraft configuration discipline. * FDIR architecture, fault injection, watchdogs, safe modes, degraded modes, and robust autonomous behaviour. * Sensor, actuator, ADCS, or payload bring-up. * On-target debugging using JTAG/SWD, telemetry, logs, oscilloscopes, logic analysers, or similar tools. * Automated commissioning, observability, and operational tooling. Nice to haves Experience with any of the following would be valuable: * LEO missions from AIT through to in-orbit operations. * ECSS, CCSDS, or other spacecraft engineering standards. * FPGA or Zynq interfaces. * Ground-segment automation, telemetry pipelines, dashboards, or operational observability. * Space-system security, including key management, signed command paths, secure update chains, and anti-rollback. * Building engineering culture: mentoring, code review, technical standards, release discipline, and high-ownership teams. ## Description Over the coming years, an OrbAstro spacecraft software engineer should expect to see their work used across many satellites, many payloads, many customers, and many mission types. The real-world learning curve is unusually steep. In a couple of years here, you can gain the kind of exposure many engineers would struggle to get in a decade elsewhere. This is a rare opportunity to become very, very good. What you will be doing You will write software that operates real spacecraft. You will work across embedded flight code, bootloaders, secure updates, TT&C, ADCS bring-up, sensor and actuator integration, in-orbit commissioning, FDIR, observability, test automation, hardware-in-the-loop testing, and operational tooling. You may also lead a small flight-software team and act as release authority, helping set the standard for how we build, test, release, update, recover, and operate spacecraft software. This is not abstract software work. You will be close to the hardware, close to the mission, and close to the consequences. You will work with AIT, avionics, RF, ADCS, payload, ground-segment, and operations teams to get spacecraft commissioned, stable, resilient, and productive in orbit. You will work on customer missions, hosted payload missions, constellation missions, and OrbAstro's own internal constellation programmes. We are not only building satellites for others; we are building towards our own vision for the next generation of orbital infrastructure: more capable, more accessible, more autonomous, and ultimately more useful to humanity. The software you write here will matter. What we are looking for We are looking for an exceptional engineer who wants an unusually steep learning curve and an unusually high level of ownership. OrbAstro is a lean, high-calibre team operating in a part of the industry where execution matters. We are not looking for passengers. We are looking for people who take responsibility, move fast without becoming careless, raise standards, and make the people around them better. This role will suit someone who wants to be pushed, trusted, and stretched. Someone who enjoys difficult technical problems. Someone who is comfortable close to hardware. Someone who wants their work to fly. Someone who would rather own a real system than be a small part of a slow, distant programme. You should have a "we will figure it out" attitude, but also the judgement to know when rigour matters. Spacecraft software must be practical, testable, observable, recoverable, and boringly reliable when it counts. Five years at OrbAstro should set the right person up like almost nowhere else: code in orbit, ownership across many missions, exposure to the full spacecraft stack, responsibility for real operational systems, and the opportunity to become a serious technical leader in satellite flight software. This is a small-unit environment: high trust, high standards, high tempo, high consequence. ## Related Videos - [What I learned as a developer from accidents in space](https://www.wearedevelopers.com/videos/642-what-i-learned-as-a-developer-from-accidents-in-space) - [Single Server, Global Reach: Running a Worldwide Marketplace on Bare Metal in a Cloud-Dominated World](https://www.wearedevelopers.com/videos/1206-single-server-global-reach-running-a-worldwide-marketplace-on-bare-metal-in-a-cloud-dominated-world) - [Playing Pong on a shoulder press machine](https://www.wearedevelopers.com/videos/100140-playing-pong-on-a-shoulder-press-machine) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [More efficient software for more efficient microchips](https://www.wearedevelopers.com/videos/1164-more-efficient-software-for-more-efficient-microchips) - [How to Avoid Tech Hype Traps - Josip Stuhli](https://www.wearedevelopers.com/videos/1817-how-to-avoid-tech-hype-traps-josip-stuhli) ## Related Articles - [Is Software Engineering Hard?](https://www.wearedevelopers.com/magazine/448-is-software-engineering-hard) - [Dev Digest 138 - Are you secure about this?](https://www.wearedevelopers.com/magazine/486-dev-digest-138-are-you-secure-about-this) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 129 - Now that's what I call private data!](https://www.wearedevelopers.com/magazine/468-dev-digest-129-now-that-s-what-i-call-private-data) - [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools)