The setting
's lets heavy mining trucks and equipment operate on their own at customer mine sites. It combines vehicle controls, sensors, computers and fleet software.
The driverless schedule needs six trucks, while the enclosure evidence supports only a hard hardware decision.
Mine operations protects hauling capacity, while the safety case protects against releasing a dust-compromised perception system.
Who you’d be doing this for
“Dispatch has already rebuilt the shift twice, and they keep asking when that truck comes back.”
Javad Mansour · Mine Operations Manager · a character in this brief
Accountable for fleet availability and material movement during the driverless operating window.
What is at stake
One haul truck leaves autonomous service when dust reaches its lidar enclosure. You must choose what gets installed across six trucks before drilling makes the retrofit hard to undo.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- driverless availability vs. sensor survivability
- fleet-wide consistency vs. site-specific evidence
- structural retrofit commitment vs. reversible containment
- production schedule vs. safety-case proof
Why Applied Intuition
Autonomous haul trucks depend on sensor hardware that survives dust and vibration across customer mine sites.
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.
- Engineering Technician (opens in a new tab)
- Support the build, installation, integration, commissioning, and maintenance of autonomous vehicle hardware and supporting systems.
- Practical experience working in a workshop, field, lab, or assembly environment and a commitment to high-quality workmanship.
- Hardware Systems Lead, Industrials (opens in a new tab)
- Define and drive survivability: determine how sensors, compute, harnesses, connectors, and enclosures will hold up to vibration, shock, dust, water ingress, thermal extremes, EMI, and years of heavy use
- You'll work in the field as much as at the bench, and your decisions will define how Applied's hardware performs on real machines in dust, vibration, heat, mud, and shock.
- Hardware Integration Engineer (Mining) (opens in a new tab)
- You will work directly with our hardware engineers, engineering technicians, operators and safety drivers.
- Own the fleet reliability and be first line of triage and issue resolution for issues found at the customer site
- Robotics Integration Engineer (TL) · no longer posted
- Lead and coordinate a team of engineers: set technical direction, prioritize across competing workstreams, and manage cross-functional dependencies with internal teams
- As a Senior Robotics & Integration Engineer, you will own the software and hardware platform that our intelligent autonomy stack runs on — everything from networking, time synchronization, sensors and drivers, and middleware, down to embedded systems, drive-by-wire, and low-level controls actuation.
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.
Sensor resets after rain exposure could remove the remaining pilot-build path.
You have to weigh a tooling commitment against evidence that still supports more than one failure mechanism.
AI Dashcams are resetting during shifts on rough-service vehicles, leaving fleet managers without some safety footage.
You must weigh a physical change that protects uptime against the evidence and production time needed to trust it.
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 Mining Autonomy and Drive-by-Wire System, written for a different role. They’re separate briefs, not the same scenario.
Mine operations managers are waiting on fixes while reviews reopen for missing vehicle evidence.
You must decide whether AI marks uncertain evidence or holds the change for an engineer to investigate.
Mine managers cannot compare autonomous shifts without rebuilding truck data by hand.
You must decide which fleet measures belong in one view without hiding meaningful vehicle differences.
Autonomous haul trucks are stopping after brake commands should have expired.
You must choose a control-interface release that restores availability without accepting unverified braking behavior.
Other problems with a similar purpose
In each of these, as in this one, the aim is to trace a strange, repeatable failure back to its root cause and leave behind a fix that quietly holds.
Completed repeated assay tasks remain open in Worklists after their workflow record closes.
You must weigh a fast status correction against preserving the execution history reviewers rely on.
Amended container bookings can hold uploaded documents in the Document Platform while customers see none in the Client Application.
You have to weigh a quick recovery against preserving document access boundaries.
6.8% of completed audio jobs now wait more than ten minutes for a Flow status.
You must weigh a targeted retry correction against a rollback that restores speed but removes newer recovery behavior.
