Senior Backend Engineer (Rust)

In a world where geopolitical tensions and security threats are accelerating, the way nations protect people and preserve peace is being redefined. At Intelic, we're building the intelligence layer for unmanned systems in defense: software that enables autonomous platforms to operate together, faster, smarter, and more reliably, across complex, mission-critical environments.

Based in Amsterdam and growing fast, we offer a rare opportunity to work on products that don't just move metrics. They directly affect safety, resilience, and Europe's security.

Our drones carry more and more hardware: cameras, gimbals, servos and more. The European market is fragmented, so we need to support many different types of hardware. Right now, adding a new piece of hardware usually means our own engineers have to integrate it. We want to change that. We're building a platform that lets partners and other teams connect their own hardware and write their own driver.

You'll work alongside robotics engineers and help set the team up from the start. The APIs and system design you create will be what everyone else builds on.

If you like hard backend problems where good design directly affects how fast other people can move, this role is worth a look.

You'll spend most of your time in Rust, working out how to abstract the communication with the hardware from the rest of the system. That could mean designing how a new camera gets configured through the API, or writing a simulated camera so you can test an integration before the hardware is on your desk.

• →

  Design and build the platform in Rust

• →

  Define the APIs that other teams and partners use to integrate cameras, gimbals, servos and other hardware

• →

  Make it possible for others to write their own drivers and add hardware without needing support from your team

• →

  Think through how each new module fits into the wider system, and plan for the cases others will run into later

• →

  Write strong unit tests and add integration tests, including tests against simulated hardware

• →

  Work directly with other teams to understand what they need from the platform and agree on how systems talk to each other

• →

  Help set up the team, and hand it over well once the platform is in good shape

At 6 months: You own this part of the system. The platform is set up, and the team is working at the level you helped set.

At 12 months: The platform runs without you in the middle of it, and you're helping on the wider vehicle platform, including the flight side.

• You have around five or more years of engineering experience in a heavy backend language. Rust is ideal, C++ or similar also works

• You've built platforms or APIs that other teams depend on, and you think about how your part fits into the larger system

• You work independently. You take a problem, work it out with the team, and see it through without someone managing every step

• You talk to people. You reach out to other teams, ask questions, and don't wait for work to come to you

• You take testing seriously, and you know how to test code that talks to hardware

• You use AI coding tools like Claude in your day to day work

• You enjoy technical problems more than product decisions. Here, what needs to be built is fairly clear. The job is to build it well

• Basic hardware knowledge: you know how to power a camera and get video out of it

• Experience with drones, robotics or other connected hardware

We're a startup, so we plan about three months ahead and things can change after that. The team you join is small and may not stay in its current form forever. Once the platform is set up, you may move on to work on the wider vehicle platform.

• Strong unit testing is the standard. Integration tests are added where they make sense, often using simulated hardware

• Other teams build on your APIs and integrate their own hardware, so you don't have to do every integration yourself

• Engineers work directly with other teams to agree on interfaces

• The mission is real. We're building technology that makes Europe safer.

• Your work multiplies. Set the platform up well, and every team can integrate new hardware without waiting on anyone.

• You build it from the start. You shape the APIs and the team instead of maintaining someone else's design.

• You can focus on engineering. The problem is clear. Your job is to solve it well.