We build autonomous UAV swarms for defense — multiple aircraft coordinating a mission in the field, with nobody flying any of them.
A customer brings an operational problem, and engineering builds the solution. This role sits in between — turning requirements into clear scopes, coordinating delivery and demos, and building the processes and structures that help the team scale.
What you will do :
Running projects — and building how we run them
The day-to-day is timelines, dependencies, documentation, and action items that do not get lost.
But we are growing faster than our structures are, so you will not just work inside the system — you will help build it. Where a process is missing, you design it. Where one only exists in someone's head, you get it out and make it usable for everyone else.
You have leadership's mandate for this, so it is not a junior person trying to convince senior engineers to change their habits. Of everything you do here, this is the part that should still be in use long after your internship ends.
Presentations and commercial documents :
Customer decks, proposals, capability briefs, scoping documents and requirement matrices.
You build them, not just format them. That means understanding the problem, gathering the right input, structuring the information, and building an argument that makes sense to the customer.
Demos and field engagements
Organise and run demos, field days, and industry events, from the narrative down to the logistics.
That means being on the airfield when preparations start, making sure everything is ready, and being there when the swarm goes up in front of the customer — not reading the report afterwards.
Ihre E-Mail-Jobbenachrichtigung ist jetzt aktiv!
