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.
Mission continuity conflicts with proving that stale commands cannot survive a degraded link.
The final flight must preserve coordinated behavior while preventing one aircraft from acting on an expired mission message.
Who you’d be doing this for
“My operators watched one aircraft keep going after the link dropped, and now they want to know which one to trust.”
Heikki Rasmussen · UAS Operations Manager · a character in this brief
Supervises the customer unit that will run coordinated missions across the two aircraft types.
What is at stake
One aircraft continued its task after the datalink degraded during a mixed-aircraft flight. You must choose a release path that protects mission continuity without accepting stale commands.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- mission continuity vs stale-command rejection
- final flight evidence vs configuration stability
- cross-platform reuse vs OEM-specific behavior
- fast release decision vs causal confidence
Why Applied Intuition
Mixed-aircraft autonomy depends on software that behaves predictably across OEM hardware when communications deteriorate.
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.
- You will collaborate closely with cross-functional teams to deliver robust, scalable solutions for defense and commercial customers, providing seamless hardware-software integration, troubleshooting, and customer-facing demonstrations.
- 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)
- 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.
- This on-site role focuses on the capabilities defense customers rely on to design, train, and validate coordinated UAV behavior.
Reporting read before this brief was written
The pieces closest to the situation in this brief.
On August 17, 2026, the Department of War awarded NODA AI a $100 million contract for autonomous mission command, which NODA says works across any vendor's platforms and continues missions to the commander's intent when communications degrade.
Department of War Awards NODA AI $100 Million to Scale Mission Command for Autonomous Forces Across the Joint Force (opens in a new tab) · prnewswire.com · Aug 17, 2026
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.
Similar problems at other organizations
Like this one, each of these turns on crossing a deadline that can't be undone.
Authentication failures are holding aircraft after network transitions, delaying ready orders despite rapid reconnects.
You must weigh recovered mission throughput against evidence that the fallback still rejects unsafe command sequences.
Reviewed traces show navigation-margin loss under concurrent radios and power loads, but not in every case.
You must weigh fleet capacity against a hardware commitment that becomes expensive to unwind.
Ready orders are missing pickup windows when aircraft hold near tall obstacles despite clear-looking approaches.
You have to weigh conservative safety behavior against a release that keeps deliveries moving.
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 engineer security-critical controls whose correctness holds up even when carefully examined by skeptics.
Held content can be classified in most samples, but nothing proves that every retrieval surface enforces the split.
You have to ship enforcement, define the proof, and get sign-off before the irreversible migration.
A controller trust-path concern must be addressed within seven days across occupied sites.
You must weigh stronger remote protection against the chance of disrupting reliable door access.
An automated grader for AI-generated Python passes 97% of tests, but reviewers found real errors in code it marked safe.
You have to decide what evidence clears this for launch, since the code runs against customer warehouse data.
