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.
Emergency-braking gains are pulling against the credibility of the dataset that reports them.
The release review needs stable evidence, while disputed synthetic labels may be hiding or inventing a safety improvement.
Who you’d be doing this for
“I’ve got reviewers asking why the pass rate jumped, and I can’t point to one label set.”
Bruna Almeida · Autonomous Vehicle Validation Engineer · a character in this brief
Prepares closed-loop emergency-braking evidence for an OEM release review.
What is at stake
Emergency-braking agreement must reach 98% across 500 reviewed scenarios before the release review. You have to weigh a stable release dataset against evidence that may overstate a safety gain.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- release timing vs. label verification
- synthetic coverage vs. comparison continuity
- perception gains vs. planning confidence
- automated labeling vs. human-reviewed evidence
Why Applied Intuition
Neural Simulation turns reconstructed and synthetic drives into validation evidence that OEM engineers must be able to trace and reproduce.
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
- 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)
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 is about an irreversible change forced by a fixed date.
A planning gain appears in the dashboard, but rare scenes entered only one comparison cohort.
You must weigh a five-day release decision against evidence that stays defensible after deployment.
Simulation shows a 3.6% late-lane-change rate, while 19 on-road traces remain inconclusive.
You must weigh a locked fleet branch against evidence that is expensive to verify.
Recent dock missions could leave a perception model with untested operating conditions.
You must choose whether incomplete provenance excludes needed data or delays the release.
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.
