New

Lead Software Safety Architect

Stellantis
United States, Michigan, Auburn Hills
Aug 28, 2026
The Lead Software Safety Architect drives the translation of Safety Goals, Functional Safety Concepts, and Technical Safety Requirements (TSRs) into robust software architectures implemented using AUTOSAR Classic, AUTOSAR Adaptive, Linux, QNX, and mixed-criticality platforms. The Lead Software Safety Architect serves as the technical authority for software safety and works closely with System Engineering, Hardware Architecture, Functional Safety Managers, Platform Architects, BSW teams, and application developers. Key Responsibilities: Define and maintain software safety architectures compliant with ISO 26262. Translate: Safety Goals, Functional Safety Concept (FSC), Technical Safety Concept (TSC), Technical Safety Requirements (TSRs) into software requirements and architecture decisions. Allocate safety requirements across application software, middleware, operating system, communication stack, and hardware-dependent software. Safety Mechanisms Definition: Watchdog supervision, Alive monitoring, Program flow monitoring, Timing supervision, End-to-End protection (E2E), Memory protection, Inter-core protection, Communication monitoring, Redundancy management, Diagnostic event handling, Safe state transitions, Degraded mode management, Fault containment regions, Freedom From Interference (FFI) Perform and support: Software FMEA, Failure Propagation Analysis, Dependent Failure Analysis, Safety Mechanism Analysis, FMEDA contribution, Freedom From Interference assessments Basic Qualifications: Bachelor's degree in Computer Science, Software Engineering, Computer Engineering, Electrical Engineering, Automotive Engineering or related field. A minimum of 10 years' experience in design and development of embedded software architecture including a minimum of 5 years in software architecture and functional safety Expert knowledge of ISO 26262 Preferred Qualifications: Knowledge of cybersecurity (ISO 21434) and interaction with functional safety. Experience with zonal architectures and software-defined vehicle platforms. The Lead Software Safety Architect drives the translation of Safety Goals, Functional Safety Concepts, and Technical Safety Requirements (TSRs) into robust software architectures implemented using AUTOSAR Classic, AUTOSAR Adaptive, Linux, QNX, and mixed-criticality platforms. The Lead Software Safety Architect serves as the technical authority for software safety and works closely with System Engineering, Hardware Architecture, Functional Safety Managers, Platform Architects, BSW teams, and application developers. Key Responsibilities: Define and maintain software safety architectures compliant with ISO 26262. Translate: Safety Goals, Functional Safety Concept (FSC), Technical Safety Concept (TSC), Technical Safety Requirements (TSRs) into software requirements and architecture decisions. Allocate safety requirements across application software, middleware, operating system, communication stack, and hardware-dependent software. Safety Mechanisms Definition: Watchdog supervision, Alive monitoring, Program flow monitoring, Timing supervision, End-to-End protection (E2E), Memory protection, Inter-core protection, Communication monitoring, Redundancy management, Diagnostic event handling, Safe state transitions, Degraded mode management, Fault containment regions, Freedom From Interference (FFI) Perform and support: Software FMEA, Failure Propagation Analysis, Dependent Failure Analysis, Safety Mechanism Analysis, FMEDA contribution, Freedom From Interference assessments At Stellantis, we assess candidates based on qualifications, merit, and business needs. We welcome applications from all people without regard to sex, age, ethnicity, nationality, religion, sexual orientation, disability, or any characteristic protected by law. We believe that diverse teams reflect our identity as a global company, enabling us to better address the evolving needs of our customers and care for our future.