Software Generalist — Tools, Dashboards, Frameworks & Performance (Python / Rust / C++ / Web)

You will build internal tools, shared libraries, and product-supporting infrastructure for autonomous flight systems. You work across Python, Rust, C++, and web stacks, embedding with teams to understand their workflows and ship solutions that make their jobs easier. Examples include flight operations dashboards, deployment tools, camera-interfacing libraries, data annotation software, and CI dashboards.

Responsibilities

• Flight operations dashboard: Flight planning, weather integration, and test-location scouting for our internal flight ops team. Python + web.
• A Rust deployment tool: For fast compile → build → deploy from our servers out to edge devices, over links unreliable enough that normal deployment tooling falls over.
• A high-performance C++ camera-interfacing library: Used across our fiducial products. Latency and throughput matter here in a way most application code never has to think about.
• Data annotation software: The tooling our annotators use every day. Its quality sets the ceiling on the quality of the data our models learn from.
• Product-metric CI dashboards: Surfacing critical performance metrics against reference datasets, across commits and branches, so regressions are caught the moment they land.
• You deploy to the field with flight ops before there’s a dashboard, again with an early version in hand, and again once they’ve been living with it.
• You take deployment shifts, and you keep taking them after the tool exists.
• You work inside our product codebases until you understand how they consume a camera library, and you stay close as both sides change.
• You annotate data yourself, sitting next to the annotators. You feel the thousandth repetitive click, eliminate it, and go back to annotating to find the next one.

Requirements

• You own outcomes. You don’t throw software over a wall. You talk to the people who’ll use what you build, most often colleagues down the hall, sometimes the users of our products. You sit with them, watch where they stumble, and find usability friction. "Done" means someone’s job got easier.
• You orient fast in unfamiliar territory. Dropped onto an arbitrary problem, you build an accurate mental model quickly of two things: the unfamiliar codebase or domain, and the unfamiliar human workflow underneath it.
• You architect for use and for change. Your software is well-built in the ordinary sense and shaped around how it will be used and how it will need to grow. You tend to pre-build the next feature request, because you know the user well enough to see it.
• Language-agnostic. You’ve shipped real software in more than one of Python, Rust, C++, and modern web stacks, and you treat languages as tools you pick up as needed rather than as an identity. You don’t need mastery of all of them on day one, you need to be someone who becomes competent in a new one fast.
• Strong systems and performance instinct. Some of our work lives or dies on performance. You have a felt sense for where the time and bytes go, and you reach for a profiler by reflex. A computer graphics or game-development background is a real plus. Other work barely touches any of it, and you can tell the difference and right-size your effort accordingly.

Nice to have

• Background in graphics, game dev, or real-time systems
• Networking depth — you understand what happens when topologies get ugly
• Rust and/or modern C++ in production
• Experience owning internal tooling or developer-experience work
• Comfort with hardware-in-the-loop or field-deployed systems
• You’ve built the in-house version of something other teams usually buy

Benefits

• Money, of course.
• 25 vacation days per year.
• Reimbursed travel expenses and company laptop.
• (Really) flexible working hours and option to work from home 2 days per week when in the Netherlands.
• Working in an international, world-class team of engineers and entrepreneurs solving real-life problems with amazing technology.
• Large freedom in how you work and implement solutions, project ownership is incredibly important to us.
• The opportunity to take technical risks, to implement stuff the ‘right’ way and to iterate quickly with tight feedback loops. We are innovating, learning is to be expected.
• Responsibility over the things you implement, you are the expert on what you build.
• Traveling abroad to test the solutions you built in relevant environments.