> Markdown version of [/jobs/ext/4743249-senior-software-safety-manager](https://www.wearedevelopers.com/jobs/ext/4743249-senior-software-safety-manager). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Safety Manager - **Company:** NVIDIA Corporation - **Location:** Santa Clara, CA, United States - **Experience:** Expert - **Salary:** $183,750 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Static Program Analysis, Code Coverage, Computer Engineering, Linux, Formal Verification, Open Source Technology, Software Safety, Software Engineering, System Software, Concurrency, Functional Dependencies, Information Technology, Hardware Acceleration, DO-178B, Automation Anywhere - **Published:** November 16, 2026 - **Apply:** https://nvidia.wd5.myworkdayjobs.com/NVIDIAExternalCareerSite/job/US-CA-Santa-Clara/Senior-Software-Safety-Manager_JR2029915 ## About the Role * 8+ years in engineering, including at least 5 years in safety-critical embedded systems and responsibility for safety plans, reviews, analyses, or arguments. * A master's degree in computer science, computer engineering, electrical engineering, or a related field, or equivalent experience. * Experience applying ISO 26262, including SEooC development and integration assumptions. Experience assessing architecture, dependencies, failure behavior, and verification evidence in embedded or system software. * Background with safety-related Linux or operating-system kernels, plus virtualization, hardware acceleration, or other complex platform software. Experience assessing third-party or open-source components in a defined product configuration. * Experience demonstrating claims with sufficient evidence, assessing changes and reuse, and simplifying workflows to reduce recurring exceptions while preserving assurance and accountability. Clear communication of uncertainties and recommendations, and experience resolving disagreements and completing work across teams and locations. Ways to stand out from the crowd: We welcome experience with automotive AI or autonomous-systems software, IEC 61508, DO-178C, SOTIF, data driven arguments, evidence reuse across product domains, formal verification, modeling, concurrency, interference, or dependent failures. We also value experience mentoring safety practitioners and putting verified automation or AI workflows into use with clear ownership. We look forward to learning from your experience! ## Description * You'll help define safety objectives, ASIL scope, intended use, and integration assumptions. We'll rely on you for program safety plans, with approved tailoring, responsibilities, and acceptance criteria before work begins. You'll be responsible for the safety argument, Safety release collateral, linking claims to requirements, architecture, analyses, and verification evidence. You'll work with owners to resolve differences among product scope, SEooC assumptions, manuals, and supported uses. * We review requirements, design, analyses, and test evidence early. You'll assess assumptions, static analysis, fault injection, structural coverage, and verification independence. With engineering, you'll review and coordinate software safety analyses, and targeted inspections. We'll use findings to guide requirements, verification, and risk reduction. Our work spans software components like Linux, virtualization, drivers, graphics, compute, and communication. You'll assess configurations, interfaces, interference, fault reactions, and degraded operation. * We need safety evidence that evolves as software changes. You'll plan reuse across releases, branches, and variants, identifying further analysis or verification needs. We'll also adapt safety processes and work products for reuse across industry domains. With build and tooling teams, you'll trace evidence to software versions and configurations. You'll align work with release achievements and secure program commitments for multi-functional dependencies. * You'll maintain the risk backlog, including releases, owners, approvals, and traceability, and serve on the Safety Review Board. You'll raise unresolved concerns with product impact, a recovery plan, and a date. We'll work with customer-facing teams on integration assumptions and evidence, using customer and field findings to update safety plans. We'll also improve workflows through measurement, automation, and AI, verifying outputs and applying qualification or validation for the intended use.