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.
Early flags protect validation windows, but unnecessary holds can starve autonomy metrics of data.
The reconstruction pipeline needs credible data-quality signals while Data Engineers preserve control over what enters evaluation.
Who you’d be doing this for
“I found the bad sensor records after we had already booked the review room.”
Nisha Kapoor · Autonomous Vehicle Validation Engineer · a character in this brief
Reviews closed-loop autonomy results built on reconstructed driving data for an OEM validation program.
What is at stake
Questionable records are reaching autonomy metric reviews after the reconstruction run has already finished. You must decide where the AI's flag on a landing run stops and the Data Engineer's call to hold data feeding autonomy metrics begins.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- early detection vs. unnecessary data holds
- shared threshold rules vs. per-pipeline variation
- flag detail vs. Slack message noise
- reusable pattern vs. bounded pilot
Why Applied Intuition
Neural Simulation depends on reconstructed driving data that OEM validation engineers can trace and trust in closed-loop reviews.
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)
- Prior contributions to systems that connect data-driven model iteration loops (“data flywheel”)
- You'll build the datasets, metrics, and visualizations that tell perception, prediction, and planning developers whether a change improved the stack, where it remains weak, and what to work on next — the signal teams use to steer development and that leadership uses to judge release readiness.
- Software Engineer - Data Pipeline (opens in a new tab)
- Mapping Specialist · no longer posted
- Create, edit, and maintain HD maps to support L4 autonomous vehicle operations.
- These maps are 100x more detailed than standard road maps and serve as foundational inputs to Autonomous Vehicle perception, planning, and localization systems.
- Senior Software Engineer - Data Engine (opens in a new tab)
- As a data engineer experienced in machine learning, you will be responsible for both our edge application which runs perception stacks and our cloud data engine which ingests video data to run the next iteration of the model before we deploy it back down to the edge.
- 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.
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 make a machine-driven decision dependable and fair at the exact real-world moment a customer is counting on it.
Agents are retrieving older interaction summaries after a customer updates a preference.
You must weigh a ranking correction against retrieval latency and safe rollout coverage.
Fourteen percent of Qwen requests now exceed three seconds after the container build.
You must weigh faster batching against the context available to each answer.
Clinicians are rejecting exercise-progression recommendations because the agent retrieves outdated protocol content.
You must weigh a fast retrieval correction against regression risk across shared deployments.
