Functional safety (ISO 26262) talent: what's actually scarce in 2026

Why functional safety matters in modern vehicles

Functional safety addresses the risk of unreasonable hazards arising from malfunctioning behaviour of electrical and electronic systems. As braking, steering, propulsion and driver assistance functions become electronically mediated, the consequence of a systematic design fault or a random hardware failure grows.

The discipline is therefore less about adding a review step and more about how requirements, architecture, implementation and verification are connected. Safety argumentation depends on evidence produced throughout development, which is why late-stage safety effort is usually expensive and incomplete.

Understanding ISO 26262

At a high level, the standard describes a safety lifecycle and the activities that support it:

• Hazard analysis — identifying hazardous events arising from malfunctioning behaviour
• Risk assessment — evaluating those events in terms of severity, exposure and controllability
• ASIL — a classification used to determine the rigour of activities required
• Safety lifecycle — the structured progression from concept through development to production and operation
• Verification — confirming that work products meet their specified requirements
• Validation — confirming that safety goals are achieved at vehicle level
• Safety documentation — the traceable evidence supporting the safety argument

Where the talent gap appears

Demand is strongest for engineers who combine safety understanding with hands-on system or software experience. The commonly requested profiles include:

• Functional safety engineering — lifecycle planning, safety concepts and safety case support
• Systems engineering — requirements, architecture and traceability across disciplines
• Embedded systems — real-time software behaviour, resource constraints and diagnostics
• AUTOSAR platform experience, including configuration and integration
• Safety analysis methods such as FMEA, FMEDA, FTA and dependent-failure analysis
• Verification and validation, including test strategy, coverage and evidence generation
• Automotive electronics — hardware metrics, failure modes and diagnostic coverage

The scarcest combination

Engineers who can perform quantitative hardware safety analysis and connect it credibly to system-level safety goals remain the hardest group to source. Safety process knowledge alone is more widely available than the analytical and implementation depth that supports it.

Experience matters more than job titles

Job titles are a weak indicator of safety capability. Two engineers with identical designations may have very different exposure — one may have authored analyses and defended them in assessment, another may have maintained documentation produced elsewhere.

Practical program experience is more informative. Useful evaluation questions focus on what the engineer produced, which decisions they influenced and how they handled evidence gaps:

• Which work products did they author rather than review?
• Which analyses have they performed end to end, and on what system scope?
• How did safety requirements influence architecture or implementation choices they made?
• How did they handle traceability and evidence during change?

How organizations can build safety capability

Because the scarce profiles cannot be hired at scale quickly, most organizations build capability through a combination of approaches:

1. 1Internal training that connects safety methods to the organization's own products and processes
2. 2Specialised hiring focused on the few roles that must be held internally, such as safety architecture ownership
3. 3Upskilling experienced systems and embedded engineers, who often transition effectively into safety roles
4. 4External engineering expertise for defined analysis scopes and independent review
5. 5Structured talent pipelines so safety-capable engineers can be deployed to program phases predictably

The sequencing that works best keeps ownership of the safety concept internal while using external capacity for bounded, well-specified analysis work.

Conclusion

As automotive electronics grow more complex, developing specialised functional-safety capability becomes a sustained organizational commitment rather than a hiring exercise. Organizations that identify precisely which parts of the lifecycle they must own — and build for those first — tend to reach dependable safety delivery sooner.