The setting
builds autonomy technology for vehicles and machines. is software and hardware that lets drones act on their own, made for defense and commercial customers.
Adding a second aircraft makes the ground-control view less trustworthy.
Shared network simplicity protects fast setup, while distinct aircraft identity protects operator visibility.
Who you’d be doing this for
“Once the second aircraft came online, the first one vanished from my display and everyone asked if it was still flying.”
Nadine Nasr · UAS Operations Manager · a character in this brief
Supervises operators running coordinated missions across aircraft from more than one vendor.
What is at stake
Operators lose one aircraft from the ground-control view when another joins the network. You must weigh a routing change in the container stack against preserving the current message contract.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast flight readiness vs reusable network behavior
- shared setup simplicity vs aircraft-specific identity
- stable message contracts vs routing correction
Why Applied Intuition
Mixed-airframe autonomy depends on ground control stations receiving attributable status from every aircraft in the mission.
Written with these in mind
Not your kind of problem? 93 more at Applied Intuition, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Applied Intuition. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior C++ Software Engineer - Drone Stack (opens in a new tab)
- Integrate autonomy software into hardware in collaboration with autonomy engineers that supports full integration with aircraft autopilots, datalinks, sensors, PNT/GPS/INS, ground control stations, etc.
- As a Software Engineer on our Drone Stack team, you will design and integrate complex autonomy and vehicle intelligence systems spanning hardware and software domains.
- GNC Engineer (Guidance, Navigation & Control) (opens in a new tab)
- Write software that operates real autonomous aircraft systems including F16 fighter jets, group 1-5 unmanned aerial vehicles (UAVs), as well as simulated models to accomplish tactical military missions
- Software Engineer - Robotics (opens in a new tab)
- Troubleshoot complex software and integration issues to ensure high reliability and performance across the stack
- Software Engineer - Multi-Agent UAV Autonomy (Defense) (opens in a new tab)
- Our defense customers are building fleets of unmanned aerial systems that have to fly, coordinate, and complete missions in the real world.
- Building those tools well, and knowing they hold up outside of simulation, requires engineers who have done this work themselves.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
The same setting, from another role
Each is set around Applied Intuition’s Drone autonomy stack (DroneStack), written for a different role. They’re separate briefs, not the same scenario.
Vibration-related anomalies are returning because evidence is split across test results, build records, and failure reports.
You must decide where the correlation package stops and the mechanical engineers start, from joining the records in Python to naming the physical cause and entering it in Jira.
Payload changes are forcing crews to rebuild mounts and reroute cables between missions.
You must weigh field reconfiguration against flight time, survivability, and a pilot build that can be repeated.
One aircraft lost navigation quality during a vibration-heavy climb, putting the next multi-aircraft evaluation at risk.
You must weigh a durable avionics bay against the flight-time and release cost of added structure.
Other problems with a similar purpose
In each of these, as in this one, the aim is to trace a strange, repeatable failure back to its root cause and leave behind a fix that quietly holds.
Completed repeated assay tasks remain open in Worklists after their workflow record closes.
You must weigh a fast status correction against preserving the execution history reviewers rely on.
Amended container bookings can hold uploaded documents in the Document Platform while customers see none in the Client Application.
You have to weigh a quick recovery against preserving document access boundaries.
6.8% of completed audio jobs now wait more than ten minutes for a Flow status.
You must weigh a targeted retry correction against a rollback that restores speed but removes newer recovery behavior.
