The setting
's is a set of software tools for defense that covers simulation, hardware and software integration, and mission control. It helps teams build, test and deploy autonomous systems that work together.
The assumptions that make a simulated mission credible can disappear before the live exercise begins.
Mission engineers need reusable context for field preparation, while evaluators need each program’s approvals to remain explicit.
Who you’d be doing this for
“I spent half the morning asking whether that comms assumption still holds for the range run.”
Pieter Becker · Mission Engineer · a character in this brief
Prepares multi-vendor mission scenarios for field exercises after simulation campaigns.
What is at stake
Mission engineers keep rebuilding live-exercise assumptions after simulation campaigns. You must decide what travels from Axion Sim into Axion and what remains program-specific.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- repeatable handoff vs program-specific approvals
- simulation context vs field-ready simplicity
- self-serve preparation vs delivery flexibility
- shared components vs mission-specific needs
Why Applied Intuition
Axion Sim sits at the point where Digital Proving Grounds move autonomous systems from simulation into HIL, LVC, and live exercises.
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.
- Product Manager - Digital Proving Grounds (opens in a new tab)
- Run discovery with program offices, test and evaluation organizations, mission engineers, and autonomy vendors.
- Shape how a team goes from a mission and its concept of operations to test scenarios, then to SIL at scale, HIL rig checkout, LVC, and live events, with results that carry across each stage.
- Product Manager - DefenseOS (opens in a new tab)
- Partner closely with engineering, hardware/integration, and operations to sequence delivery across simulation, integration lab, and live-platform testing on unmanned surface vessels and traditional surface combatants.
- Lead customer and user discovery directly with Navy program offices, operators, and crews to translate operational needs, acquisition requirements, and field constraints into a prioritized product roadmap.
- Product Manager - Drone Stack (opens in a new tab)
- You know how to learn a market from scratch: talking to users, studying workflows, reading doctrine, attending field exercises, and synthesizing what you find into actionable product direction.
- Our technology — from the Acuity ISR+Strike autonomy stack to the Axle edge compute hardware — is deployed on real platforms with real operators, across multiple airframe vendors and mission sets.
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.
Tracked vehicles disappear during video dips in concurrent missions, even when aircraft stay on route.
You must weigh mission continuity against a release decision that cannot be cheaply undone.
Operator reviews rely on screenshots that do not reliably tie evaluation results to one software version.
You must weigh a useful first evidence dataset against the time needed to validate its lineage.
Pilot sites are finding missing mission details at launch after planning looked complete.
You have to weigh earlier guidance against making a software result look like flight authorization.
The same setting, from another role
Each is set around Applied Intuition’s Axion, written for a different role. They’re separate briefs, not the same scenario.
Program managers reconstruct mission events from separate views and leave reviews without one agreed follow-up decision.
You have to weigh a fast shared narrative against preserving the uncertainty in the underlying evidence.
Operators cannot tell whether a degraded-link reroute was approved or merely reported.
You must weigh mission continuity against an intervention model operators can trust under pressure.
Operators see an old approval state after reconnecting, even when a vehicle is already executing.
You must weigh immediate task clarity against keeping routine approvals fast.