Home › Resources › Templates › Safety-critical Manager (ISO 26262, Program / project management)
Job description template · Safety-critical

Safety-critical Manager (ISO 26262, Program / project management)

Have CSA staff this role
StageDirectory listedStandardsISO 26262 · ISO 13849IndustryAutomotiveSeniorityLead / ManagerRegionOxfordWork modeHybridSource year2026Role familyProgram / project managementSegmentAV truckingEmployerEmployer profileToolsJira · Confluence · Git
Show unavailable metadata (2)
Company sizeUnknownEmploymentUnknown

This role is currently open. See the open role on FSTalent.

Hover or focus an underlined term for a plain-language definition.

Role summary

You will join the Hardware Abstraction layer of the organization Driver: the teams that sit between our autonomy software and the vehicles it drives. They make one autonomy stack run safely on many different industrial vehicles, so their scope scales with each vehicle platform we integrate.

Responsibilities

  • safety-rated collision avoidance, and the evidence that supports product certification
  • vehicle and driving models that turn planned motion into commands each vehicle can execute
  • the on-vehicle safety controllers and the software that runs on them
  • the vehicle interface: the configuration and signal mapping that adapt the stack to each vehicle type
  • bringing new vehicle types into service, including retrofit drive-by-wire

The teams work closely with Integration & Test, Autonomy Applications, Vehicle Engineering, our safety team, and external hardware suppliers and vehicle manufacturers.

You are the delivery enabler for the Hardware Abstraction teams. You coordinate delivery so the teams can plan, build, test and ship with less friction, and their leads can focus on engineering.

You will work with engineering, product and solutions leaders across the stack who own customer outcomes. Your focus is to make sure the Hardware Abstraction layer delivers what it committed to, predictably, with its dependencies visible early.

This layer succeeds or fails on real vehicles and test rigs, so you will spend one to two

  • Plans the teams can deliver: Take the layer's commitments in our product engineering plan and, with the leads, turn them into sequenced work with dates and a clear definition of done.
  • A delivery rhythm that fits: Run planning, stand-ups and retros in a format that suits each team, including the fast cadence that hardware bring-up needs. Keep Jira as the source of truth.
  • Dependencies, seen early: Track what the teams need from others and what others need from them, raise conflicts early and broker the trade-offs
  • hardware kits, test vehicles, rigs and track time
  • supplier and vehicle-manufacturer software releases
  • handoffs to Integration & Test and Autonomy Applications
  • On-site coordination: Be the delivery presence at our vehicle sites. Get vehicle and rig time booked, and parts and people in the right place. Feed test results back into the plan.
  • Risk and change control: Keep risks visible and acted on. Make sure changes to safety-critical software and vehicle configuration follow the agreed change process, working with our safety team.
  • Reporting that saves leads' time: Report monthly progress against plan, and the health of the defect and field-issue backlog. Use simple metrics to show whether delivery is getting more predictable.
  • Better ways of working: Find the friction, such as manual steps, unclear ownership or missing test gates, and drive fixes with the teams.
  • What you need to succeed
  • A career started in engineering (a degree in electrical, mechatronic, automotive, software, robotics or similar) and have moved into delivery, with 2+ years as a TPM, project engineer or delivery manager on a technical product.
  • Knowledge of the hardware–software lifecycle: You know how work moves through requirements, supplier and ECU integration, bring-up, bench and vehicle testing, release and field support. Hands-on experience of hardware or vehicle bring-up and testing is preferred but not essential.
  • Vehicle-systems fluency: Enough to follow the engineering and ask good questions: CAN, ECUs, embedded and Linux platforms, sensors.
  • Organised and clear: You break down work, map dependencies and forecast from data (using tools like Jira, Confluence and Miro), and you build trust with engineers when priorities shift.
  • Experience in automotive, robotics, off-highway or industrial vehicles.
  • Exposure to functional safety (ISO 13849, ) or CE marking.
  • Experience working with hardware suppliers or vehicle OEMs, or on vehicle bring-up and commissioning.
  • Experience running agile delivery in a mixed hardware and software environment.
  • Comfort with Git-based planning, documentation-as-code, or AI tools for reporting.

Standards

  • ISO 26262 Road Vehicles - Functional Safety
  • ISO 13849 Safety-Related Parts of Control Systems

Use this template

Get the Word document, or let CSA scope, staff or post the role for you.