Job Opportunities API

TL;DR: We build the software behind our autonomous flight systems, plus a surprising amount of the supporting software around it. This role is for the people who want to build the latter. DETAILS Preferred starting date: ASAP Weekly availability: full-time (5 days/week) Location(s): - Aerospace Innovation Hub, Delft, The Netherlands   ABOUT THE COMPANY Fiducial is a young but fast-growing deep-tech start-up with big ambitions at the frontier of autonomy, perception, and defence. We develop and deploy software for on-board UAV 3D vision in military applications. Our software solutions are built for scalability first, using low-cost and widely available sensors and compute. WHY WORK WITH US We develop our software in the field and close to the points of use. Flight testing is key for what we do and we test all across Europe. Our team members have strong academic background in different fields such as Aerospace Engineering, Computational Science and Engineering, Robotics and Computer Graphics. Our main office is located in the TU Delft campus in the faculty of Aerospace Engineering. We work closely with top-tier partners, ranging from drone manufacturers to research institutes. Our projects span from orders in collaboration with operational partners to low-TRL research with government agencies. Whether through formal R&D programs or rapid prototyping tracks, we operate at the intersection of innovation and deployment.   ABOUT THIS ROLE You will build the internal tools, shared libraries, and product-supporting infrastructure the rest of the company runs on. You reach for Python, Rust, C++, or the browser depending on the problem. You drop into an unfamiliar domain and form strong architectural opinions within a week. You’d rather understand a problem deeply than be handed a spec. AI-ASSISTED DEVELOPMENT We build fast, and we expect fluency with vibe coding as a core, daily skill. We expect you to use these tools to get from a well-understood problem to sound, working software quickly. You also know their failure modes: you read the code you ship, and you own its correctness and architecture.   WHAT YOU’LL BUILD Some examples of what a Software Generalist here develops:   - 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.   HOW YOU’LL BUILD You embed with the team you’re building for. You ship them something early and then keep working next to them as it evolves and as you discover the shape of the final solution jointly. Concretely, for the examples above:   - 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.   The empathy you earn on the ground is what lets you build the right thing, fast. Software Generalists build the tool th