Pronto Safety Engineering Manager - Mining Deployments at Pronto AI to build and maintain off-road truck safety cases and lead a small team. Responsible for hazard analysis, test preparation, commissioning readiness, and incident triage.
Responsibilities
Build the off-road truck safety case. Claims, evidence, limits, and what remains open. Keep it current as trucks, sites and software change, and be clear about what it does not cover.
Hazard analysis. What the installation introduces on a given truck, what the site already carries, and what the combination creates. Drive the results into requirements and into site controls.
Test preparation. Define what has to be demonstrated before a truck operates autonomously at a site: the procedures, the acceptance criteria, and what evidence each test actually produces.
Commissioning readiness. Hold the gate between installed and operating. This is a real gate, and you are the person who helps specify when a site is not ready.
Incidents and triage. Own the intake path, the severity model, the investigations, and corrective actions through to verified closure.
Change assessment. Decide what a software release, a new truck variant or a new site layout does to the argument, and what has to happen before it goes live.
Grow and lead a small team. You will hire one or two engineers as the work justifies them, and lead them. This is not a management role in the usual sense: the safety case, the commissioning gate and the investigations that matter stay with you, while your team takes the recurring load. If you are looking for a path to a large org, this is not that job yet.
We expect this role to be materially more productive than the same role was three years ago, and we expect AI tooling to be the reason. A small team covers a surface that would otherwise need several, and the tooling is how that becomes possible rather than a fiction.
Use it as a working instrument: drafting and maintaining site risk assessments from a common baseline, adapting procedures per site, triaging an event backlog, and finding patterns across sites that nobody reading one site's reports would see.
Build your own tooling rather than filing tickets for it, and keep it running once other people depend on it.
Be rigorous about the boundary. A generated hazard list is a hypothesis to verify, never a risk assessment. Safety determinations need a human who has looked at the evidence and walked the site.
Qualification
8+ years in systems safetyOff-road
Required
8+ years in systems safety, safety engineering or a closely related systems discipline in a safety-critical domain. Mining experience is not required.
You have built a safety argument from scratch — claims, evidence, structure — and defended its sufficiency to someone who pushed back.
Structured hazard analysis depth at both the system and the operational level, and the judgment to pick the method the situation actually warrants.
You have written the process rather than inherited one: investigation, triage, qualification, or their equivalents. Tell us who ran it after you wrote it and what broke.
Comfortable leading one or two people while still being the person who writes the safety case rather than reviewing it.
Python or SQL sufficient to work event data yourself rather than waiting for an analyst.
Willingness to travel to sites when needed.
Preferred
Off-road, heavy vehicle or industrial machinery experience — mining, quarrying and aggregates, construction, ports or agriculture.
Working knowledge of US mine safety regulation, including MSHA Part 46 and 48 training requirements and Part 50 reporting.
Experience commissioning autonomous or remotely operated equipment on a customer's site.
Experience adapting an existing safety method into a new domain rather than starting over.
Experience building a small team from a standing start.
