The Challenge
Pick any robot. Integrate it with RideScan.
That's it.
Quadruped, humanoid, industrial arm, drone, mobile platform, your custom-built lab robot, a simulation in Gazebo or Isaac Sim, your call. Your job is to get telemetry flowing into RideScan's monitoring platform and demonstrate something useful: anomaly detection, mission risk scoring, performance insights, predictive maintenance signals, surprise us.
We're keeping this open-ended on purpose. We want to see how you approach an integration problem when nobody's looking over your shoulder.
Why we are running this
RideScan is the independent safety and reliability layer for autonomous robots — the "Fitbit for robots." We're already deployed on a quadruped inspection robot in a regulated industrial environment, with active integrator conversations across the UK, Europe, and Japan. We're backed by YOPE (the Splunk founder's Silicon Valley accelerator), Humanoid Global ($ROBO), and Innovate UK.
We're hiring an Integration Engineer, and we'd rather see you build than read your CV.
Eligibility
1. Open globally (timezone is your problem to solve, not ours)
2. Individual entries only, no teams (we're hiring one person)
3. You retain ownership of your code; by entering, you grant RideScan a non-exclusive licence to evaluate and reference your work
4. You must be legally able to work in the UK or available to relocate / work remotely from a country we can contract with, if you want to be considered for the role afterwards.
Not eligible for the role afterwards? Still enter, we love meeting good engineers and the £500 is real
What you should submit
1. A working integration, code in a public or private GitHub repo
2. A 5-minute demo video showing the integration running end-to-end
3. A short README covering: which robot, why you chose it, how it works, what you learned, what you'd build next
4. Optional but encouraged: notes on edge cases you hit, hardware/sim quirks, things that broke
