Home › Resources › Templates › Lead Safety-critical Architect (ISO 26262, Systems safety)
Job description template · Safety-critical

Lead Safety-critical Architect (ISO 26262, Systems safety)

Have CSA staff this role
StageSeries CStandardsISO 26262 · ISO 21448 · UL 4600 · ISO/SAE 21434 · ASPICEIndustryAutomotiveSeniorityPrincipalRegionCanadaWork modeOnsiteSource year2026Company size201-500Role familySystems safetySegmentAV truckingEmploymentFull-timeEmployerEmployer profileToolsPolarion · C / C++ · Rust · SysML / UML

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

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

Role summary

As a Systems Engineer on our Embedded Systems team, you'll own that translation. Our overarching systems and safety group defines the vehicle-level safety concept — the hazard analysis, the safety goals, the functional safety concept. You'll be their embedded counterpart: taking that concept and decomposing it into an embedded architecture and technical safety requirements that our electrical engineering and embedded software groups can build against. You'll live on the left side of the V at the embedded level, turning a functional safety concept into technical requirements and a hardware/software architecture the whole team can trust — and you'll be the person who keeps the embedded org fluent in the wider world of automotive standards.

Requirements

  • BS/MS in Electrical Engineering, Computer Engineering, Systems Engineering, or a related field — or equivalent hands-on experience.
  • 8+ years in embedded systems, with real depth spanning both hardware and software.
  • Strong experience concentrated on the system-design phase (Part 4) and its handoffs to hardware (Part 5) and software (Part 6): deriving technical safety requirements from a functional safety concept, system architectural design, and hardware/software allocation.
  • Working familiarity with the broader automotive standards landscape — and the judgment to operationalize it — including (), automotive cybersecurity (ISO/SAE 21434), autonomous-product safety cases (), Automotive SPICE (ASPICE), and component/coding standards such as AEC-Q10.
  • Fluency with requirements management and traceability — you've lived in a tool like Polarion and know why traceability matters when the safety case is questioned.
  • Enough range to read a schematic and reason about embedded C/C++/Rust, so your hardware/software partitioning is grounded in what each side can actually implement.
  • A clear grasp of the full V, so the left-side work you produce genuinely sets the right side up to succeed.
  • Experience standing up or maturing a standard (ASPICE, 21434, or similar) inside an engineering org, not just complying with one.
  • SysML or model-based systems engineering.
  • AV, ADAS, or other complex safety-critical domain experience.
  • Direct experience authoring or negotiating DIAs with an OEM.

Standards

Use this template

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

Have CSA staff this roleGet a scoped quoteTalk to an engineerHire through CSAPost this role on FSTalent