Location:
Madrid, Spain
Our client is looking for a Robotics Integration Engineer.
About the company
They build simulation and validation infrastructure for autonomous systems. They want robotics teams to connect the autonomy stacks they already run, test them against reproducible scenarios, and bring evidence from field failures back into simulation without requiring them to rebuild their systems around the platform.
Their near-term users may be building warehouse and industrial robots or civilian drones. Their interfaces differ — ROS2 and machine telemetry on one side, PX4/MAVLink and control-system models on the other — but the product loop is the same:
external autonomy stack → simulation → evidence → field log → replay → diagnosis and tuning
You will own that loop.
About the role
They make autonomy stacks work with the platform even when those systems were not originally designed for it, and they own the diagnosis when the first integration attempt fails. Boundary conditions, timing assumptions, build compatibility, protocol drift, and mismatched models are where integrations actually break.
It’s a hands-on software and systems role. They design interfaces, write or extend adapters, inspect runtime behaviour, and turn field evidence into reproducible tests. The work starts with the ROS2 surface and field-evidence loop, then extends the same product pattern to civilian-drone stacks as priorities and available evidence evolve.
They work directly with the engineers responsible for the deterministic simulation core and evaluation runtime. Their role is to make external systems work reliably with the product without turning each integration into a bespoke project.
What You Will Do
- Design, implement, and version interfaces between the platform and external autonomy stacks, including middleware graphs, flight controllers, control-system models, and their data contracts.
- Build and extend the adapters, bridges, and wrappers required for closed-loop operation, including systems-level code rather than configuration alone.
- Diagnose failures across software, middleware, networking, timing, and model boundaries, then isolate which side of the interface is responsible.
- Turn logs and telemetry from real or representative systems into reproducible replay, comparison, and tuning workflows.
- Build automated integration tests, regression fixtures, compatibility records, and a replayable failure corpus so that each integration improves the product.
- Work with the core and evaluation-runtime owners to define clear interface contracts and readiness criteria.
What Success Looks Like
- External robotics and autonomy stacks can connect to the platform through clear, reliable interfaces without being rebuilt around it.
- Integration failures can be isolated across the runtime boundary and resolved through durable product or adapter improvements.
- Field logs and telemetry can move through a reproducible replay, diagnosis, and comparison workflow.
- Each integration leaves behind reusable compatibility knowledge, failure cases, and regression evidence that make the next integration easier.
- The same validation product can support different robotics domains through focused adapters rather than separate one-off projects.
What You Bring
Core evidence - you have made an external autonomy stack work against a simulation or validation platform it was not designed for, and you personally diagnosed and resolved why the integration broke.
Required
- Substantial production experience with robotics, autonomy, or another distributed real-time system.
- Experience owning a robotics runtime or middleware boundary, such as ROS2/DDS, PX4/MAVLink, a proprietary autonomy stack, or a comparable control-system interface.
- Ability to read, write, and debug systems-level integration code in C++ on Linux.
- Demonstrated depth in at least one of the following areas: PX4/MAVLink SITL, Simulink/MATLAB co-simulation, or production field-log replay and tuning.
- Clear written and verbal communication across software, controls, and product boundaries.
*ROS2 experience is valuable, but this role also requires depth in at least one of the three areas above.
Strongly preferred
- Production-level ROS2 experience in a system that was shipped and operated in the field.
- Experience with a second interface or technology from the list above; experience spanning both ground robotics and civilian drones is particularly valuable.
- Experience with software-in-the-loop or hardware-in-the-loop validation, distributed-system timing, networking, or time synchronization.
- Python or shell scripting experience for diagnostic tooling and test automation.
- Experience integrating a third-party simulation platform, autonomy stack, or robotics API.
- Experience building compatibility matrices, diagnostic tooling, or regression fixtures based on recurring field failures.
Not required
- Deep expertise in aerodynamics or blade-element rotor modelling.
- Perception model training or graphics specialization.
- Sales or pre-sales ownership.
Role Boundaries
Collaborate closely with the owners of simulation-core reliability, perception fidelity, and product packaging, while keeping the primary focus on integration. This role is for an integration owner rather than a specialist in aerodynamics, perception-model training, cloud infrastructure, or commerce.
Who Tends to Fit
This trait often appears in robotics platform engineers, field robotics engineers, flight-controller integration engineers, and control-systems engineers who also write production software. If your work repeatedly placed you between a simulator, a controller and a real machine — and you became the person who could explain which assumption was wrong — that is the shape we are looking for.
What They Offer
- Relocation support and visa sponsorship for joining the team in Madrid.
- Direct product ownership of the interoperability and field-evidence loop, with room to improve the underlying product rather than repeatedly work around it.
- Close collaboration with the core team responsible for deterministic simulation and evaluation-runtime behaviour.
- Cross-domain impact: build one validation product that can support warehouse, industrial, and civilian-drone systems through reusable interfaces and evidence.
Hiring process:
- Recruitment interview.
- Intro Call with HM.
- Technical interview.
- Final interview with CEO.
Interested in learning more? Apply and let's talk!
