The setting
makes software for building and testing intelligent vehicles and autonomous machines. turns real-world driving data into photorealistic simulation environments for training and validating autonomous driving systems.
Turning-scenario volume is rising while coverage evidence remains fragmented.
Generated variety protects breadth, while provenance protects the credibility of each validation claim.
Who you’d be doing this for
“I spent half the review explaining where cases came from instead of what the stack did.”
Aung Kurniawan · Autonomous Vehicle Validation Engineer · a character in this brief
Builds closed-loop test cohorts and presents coverage evidence for an OEM autonomy program.
What is at stake
Turning reviews are assembled from separate real and synthetic case collections, so coverage claims are hard to trace. You have to weigh broad generated variety against provenance that holds up in release review.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- synthetic breadth vs reviewable provenance
- automated labels vs sampled human judgment
- reusable schema vs fast pilot adoption
- planning relevance vs perception confidence
Why Applied Intuition
Neural Simulation turns recorded drives into controllable scenarios, so OEM validation depends on knowing how synthetic coverage relates to the source evidence.
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.
- Software Engineer (SDS Core - Evaluation) (opens in a new tab)
- Build and curate the datasets — real and synthetic — that those metrics run against
- You'll work closely with stack developers to turn their open questions into rigorous metrics, drawing on both real road data and novel synthetic scenario generation to evaluate behaviors too rare or too dangerous to encounter on the road.
- Software Engineer - Data Pipeline (opens in a new tab)
- Mapping Specialist · no longer posted
- These maps are 100x more detailed than standard road maps and serve as foundational inputs to Autonomous Vehicle perception, planning, and localization systems.
- This is an excellent opportunity for professionals with a background in HD map creation, GIS mapping, spatial annotation, or 3D modeling for autonomy, robotics, simulation, or gaming who are comfortable with technical workflows and fast paced, iterative feedback cycles.
- Senior Software Engineer - Data Engine (opens in a new tab)
- Engineering Manager - Autonomy Storage Infra (opens in a new tab)
- Drive engineering decisions around scalable data ingestion, indexing, storage, and retrieval for high-volume autonomous vehicle and physical AI workloads
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 deciding on evidence that's still thin.
Vehicles with missing diagnostic coverage are being read as healthy in maintenance reporting.
You must weigh a useful fleet-status signal against the risk of labeling incomplete telemetry as normal.
Program managers lack a reliable way to find the route cohorts most likely to regress after expansion.
You must weigh a useful early ranking against the risk of overstating what sparse history can predict.
Degraded-mode investigations are being reopened because engineers begin from different traces and reach different plausible causes.
You must decide what AI can assemble, what evidence it must preserve, and where engineers retain confirmation.
The same setting, from another role
Each is set around Applied Intuition’s Neural Simulation, written for a different role. They’re separate briefs, not the same scenario.
A known Kubernetes deployment failure keeps pushing scheduled simulation regressions past their window.
You must choose what AI can classify and run, and where an engineer must take over.
Validation engineers are rebuilding cloud setup details before comparable closed-loop campaigns can begin.
You have to weigh fast self-service against the controls that make reruns defensible.
A 12,000-run validation campaign is about to lose its AWS GPU capacity, and paired reruns are not fully matching.
You have to weigh a protected review window against a cutover that could alter trusted evidence.
Other problems with a similar purpose
In each of these, as in this one, the aim is to build machine-learning systems that earn trust by staying explainable where their errors carry real consequences.
An audit found sensitive fields in 7% of shared artifacts that manual review missed, and the classifiers disagree on the edge cases.
You have to build evidence for a production commitment you cannot easily reverse.
One threshold sends very different numbers of drivers into coaching in each region, and reviewers there agree less often.
You have to balance fair treatment of drivers against enough coverage to improve coaching.
Confirmed takeover messages are reaching guests, while legitimate pre-check-in threads are also being blocked.
You must weigh fraud prevention against a guest losing the instructions needed to enter a booked stay.
