> Markdown version of [/jobs/ext/4635478-robotics-software-engineer-multiple-levels](https://www.wearedevelopers.com/jobs/ext/4635478-robotics-software-engineer-multiple-levels). 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).

---

# Robotics Software Engineer (multiple levels)

- **Company:** Katalyst Talent Agency
- **Location:** Broomfield, CO, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Artificial Intelligence, C++ (Programming Language), Software Debugging, Middleware, Ethernet, Python (Programming Language), Real-Time Operating Systems, Robot Operating System, Information Technology, C++14
- **Published:** November 8, 2026
- **Apply:** https://www.juju.com/job/28_25303_4c890f4805cec3b607c492a6e3a416df

## About the Role

* Strong C++ on real systems, and working Python
 * Hands-on experience making software meet hardware: bring-up, debugging with real instrumentation, serial buses (CAN, RS-422, SPI/I2C, Ethernet)
 * The instinct to challenge an assumption, back the challenge with data, and convince people. Engineers here make the call and defend it.
 * Engineer: 2+ years. Senior: 6+ years. Principal: 10+ years. Years are a guide, not a gate. Robots, vehicles, instruments, or spacecraft all count, and aerospace experience is not required to succeed here. Plenty of what we need was learned on things that never left the ground.
 * BS in engineering, computer science, robotics, or mechatronics, or equivalent proficiency. We mean the "or".
 * US person (ITAR). No security clearance required, this is commercial servicing.

## Description

* Own robotics-facing flight software end to end: motion and actuator control applications, the vision-to-GNC data path, and safe degraded behavior when hardware misbehaves
 * Write modern C++ that commands real actuators, arms, gimbals, and mechanisms, and Python where it moves faster
 * Take pose from camera to control loop: consume, validate, and gate vision solutions so guidance never acts on stale or bad data
 * Prove your work on our hardware-in-the-loop bench and flatsat before it flies, then watch it fly and own what happens next
 * Work directly with GNC, avionics, and operations, and defend your design decisions to the people who depend on them, * Real-time/RTOS or embedded Linux flight software
 * HIL or SIL test infrastructure you built or ran yourself
 * ROS/ROS2, cFS, or other robotics and space middleware. We fly our own framework today, and we evolve it deliberately: if you bring strong patterns from somewhere else, you get a real voice in where the architecture goes, not a foreign codebase you are stuck with.

How we interview, because we think it matters:

Three conversations and one working session, all of it with us in the room. A short screen, a 45-minute technical conversation, then a 2-hour on-site: a small synthetic codebase seeded with a real class of bug from orbit, your choice of problem track and level, using any tools you normally would, AI assistants included. You present and defend what you did to a small panel and walk a few ops scenarios. Everyone gets the same session, scored against the level you chose. Every stage is scheduled within 5 business days of the last, we fly you in for the on-site, and if you need an accommodation for any of it, say so and we work it out.

Additional Requirements:

Must be willing to work extended hours and weekends as needed.