Job search
Functional Safety Software Jobs: Match ISO 26262 Work, Safety Analysis, and Embedded Experience
Use actual US automotive and autonomous-vehicle responsibilities to distinguish implementation, safety analysis, validation infrastructure and approval authority.
A functional safety software search can lead to embedded implementation, system-level safety analysis, or verification infrastructure. Identify what you would deliver and who would review or approve it before treating those jobs as interchangeable. ISO 26262 appearing in a description does not establish a personal certification requirement, and writing reliable C++ does not establish ownership of an automotive safety argument.
Compare the employer’s assigned work with evidence you can explain from your own projects. This article reviews public ISO information and employer-hosted US postings checked October 22, 2026; it does not assess an individual’s hiring eligibility or product compliance. LandOffer publishes this guide. You can browse recent roles on LandOffer.ai, then use the original employer description to establish the actual responsibility.

Read ISO 26262 as a work context
The public ISO 26262-6:2018 summary covers automotive software development, including requirements, architecture, implementation and verification. Its scope concerns safety-related electrical and electronic systems in series-production road vehicles. That describes a development framework; the standard number alone is not a credential held by a candidate.
Version matters too. On the checked date, ISO identified the 2018 edition as current, confirmed in 2024, while showing ISO/DIS 26262-6 as a replacement under development. The page also marked the published edition as due for revision; the under-development replacement was not shown as an already published new edition. This guide uses the public abstract and status information, not the purchased standard’s full requirements.
For a job search, ask which activities you would perform under the employer’s process. Would you implement reviewed software requirements, derive them from system concerns, investigate failure behavior, or assemble evidence for a reviewer? These questions turn a standards keyword into a discussion of work. They do not determine which standard applies to a particular product or whether its development complies.
Separate implementation from safety analysis
Zoox’s Embedded Software Engineer — Drive Systems posting describes production embedded code, supplier subsystem integration, and simulation and hardware-in-the-loop infrastructure. Hardware-in-the-loop, or HIL, combines software testing with physical hardware. The role names C/C++, Python testing, real-time operating systems and automotive communications. Familiarity with ISO 26262 appears among bonus qualifications, alongside development tools and practices.
That is a different center of responsibility from Zoox’s Sensing and Perception System Safety Engineer. The latter defines safety requirements and metrics across sensing and perception, coordinates evidence supporting safety arguments, and examines field and simulation data. It names hazard analysis and functional safety concepts, with ISO 26262 and ISO 21448/SOTIF references. The description connects these tasks to camera, lidar, radar and perception-system behavior.
When reading a requirements-tool keyword such as Polarion or Jama, distinguish using the tool from controlling the content within it. Importing tests, proposing a requirement change and approving an analysis assumption are different contributions. A useful interview story explains the disputed point, your own change and the reviewer’s response. Keep any proprietary diagrams, failure rates or controlled documents out of public application materials; describe your responsibility in ordinary language. An original fictional exercise can show how you organize questions, but it cannot supply missing professional process experience.
A developer may contribute to mechanisms specified through that analysis without owning the analysis itself. Conversely, an analysis engineer may coordinate software evidence without being the main embedded implementer. Identify what you authored, what you reviewed, and what another team decided, so your application does not imply approval authority you never held. Having attended a safety review supports a different statement from having developed its argument.
The descriptions also have different experience expectations: the embedded role lists one to three years of relevant real-time work; the system safety role lists three or more years in the stated engineering domains. Keep those experience ranges attached to their individual postings; neither establishes a universal minimum for embedded or safety-analysis work. Both rendered as full-time, hybrid Foster City positions when checked.
Verification can be a coding-intensive responsibility
Zoox’s Senior Software Development Engineer in Test — Verification and Validation puts software infrastructure and validation strategy together. It describes C++/Python sensor emulators, fault-injection support, SIL/HIL frameworks, continuous-integration pipelines, root-cause investigation and gaps between requirements and test implementations. SIL means software-in-the-loop. This is not simply executing an existing regression checklist.
For that job, a strong project discussion would explain framework design, meaningful failure investigation and how evidence reached the responsible reviewers. The posting calls for extensive ownership, including complex Python projects and deep SIL/HIL knowledge. General web automation is relevant to some tools, but it does not by itself demonstrate real-time hardware interaction or the specified validation leadership.
A second employer provides another useful boundary. NVIDIA’s Senior Software Engineer — AV Platform, JR2023594 emphasizes platform and middleware implementation, systems debugging, C/C++, QNX/Linux and CPU/GPU performance. It also assigns design work against functional safety requirements. Its twelve-plus years of system-software experience are specific to this senior vacancy.
The NVIDIA page still displayed its description and Apply control on October 22, although its wording promised application acceptance “at least until” August 29, 2026. That earlier minimum date is not an established closing date. Recheck the page when considering it; this observation does not guarantee ongoing review. A separately indexed Zoox SDET result returned a 404 and was excluded from the current examples.
Hardware analysis and credentials need their own reading
The Zoox Senior Sensor Hardware Functional Safety Engineer description assigns board-level failure analysis, supplier-document assessment and diagnostic requirements with software and electrical teams. It asks for board bring-up, silicon validation or hardware-design experience. FMEDA, failure modes, effects and diagnostic analysis, appears as a hardware responsibility here. A software engineer should not infer that writing a diagnostic routine demonstrates that analysis experience.
This particular posting describes a fifty-fifty division between hardware functional safety and sensor safety/SOTIF. That split belongs to this role. It is not a standard allocation across safety teams. Likewise, the posting’s bonus certification wording is separate from its core engineering requirements; it does not make every ISO 26262 mention a mandatory certificate.
When a credential is named, preserve its exact name and required-versus-bonus placement. Ask what experience the hiring team expects it to accompany before buying training. List a completed course as training, and a credential only if you actually hold it. Neither category should replace an explanation of the work you performed.
Worked example: rewrite an embedded engineer’s evidence
Inez is fictional. Her stipulated experience is three years writing C++ for industrial equipment under a company review process. She maintained a communications component, investigated timeout logs, wrote Python tests and participated in requirements reviews. She has not developed automotive hazard analyses, assigned automotive safety integrity levels, or owned a vehicle safety case. No code, test or safety analysis was run for this example.
Her initial summary says, “Functional safety engineer responsible for ISO 26262 compliance.” That reaches beyond the supplied history. Her completed revision starts by separating the contribution from the authority implied by that sentence:
| Stipulated experience | Evidence Inez can explain | Boundary retained in the application |
|---|---|---|
| Maintained a C++ communications component | Reviewed changes and a description of her implementation responsibilities | Industrial equipment experience; no automotive process claim |
| Investigated timeout logs | How she reproduced an issue and communicated it to the component owner | Investigation contribution; no claimed hazard classification |
| Wrote Python tests | Test design, configurations and failures she personally investigated | Testing experience; no invented diagnostic-coverage result |
| Participated in requirements reviews | Her comments and the engineering questions she raised | Participation; no claim to approve safety requirements |
| Studied the public ISO summary | Topics she wants to understand in the employer’s process | Learning activity; no certification or applied-standard experience |
Her completed application paragraph reads: “I develop and maintain C++ communications software for industrial equipment and write Python tests under our review process. My work includes investigating timeout behavior and contributing implementation feedback during requirements reviews. I am interested in embedded automotive work, while my direct experience has not included automotive hazard analysis or vehicle safety-case ownership.”
Her search decision follows from that record. The implementation responsibilities in the Drive Systems description offer a concrete comparison, but she still needs to examine its automotive protocols and real-time requirements. The sensing-safety role would require a much stronger discussion of systems analysis than her current summary supplies. She retains that distinction instead of adding the standard number to every bullet.
Her unsent question for a recruiter is specific: “Would this opening primarily implement already allocated software requirements, or would it own their derivation and safety analysis? My current examples are implementation and testing work in industrial equipment.” She would record any answer as a clarification of responsibilities and leave the employer’s assessment of her experience open.

Worked example: resolve who owns the evidence
Rowan is another fictional engineer. Their stipulated background is eight years building Python testing infrastructure, including a bench-connected test harness and failure-report tooling. They have led framework maintenance but have not led an automotive validation strategy. They are comparing three responsibilities before choosing which interview stories to prepare.
The following completed record is a job-reading exercise. Its documents are invented conversation notes, not an actual vehicle safety analysis, test report or release decision. No requirement, fault model or acceptance threshold is being specified for operational use.
| Responsibility under discussion | Rowan’s relevant evidence | Missing ownership to discuss | Completed preparation choice |
|---|---|---|---|
| Implement a monitored embedded component | Test-harness collaboration with developers | Direct real-time C++ component ownership | Do not present framework code as production controller code |
| Build and maintain validation infrastructure | Bench integration, Python framework changes and failure investigation | Employer-specific SIL/HIL depth and validation-strategy leadership | Prepare a detailed infrastructure story with limits stated |
| Develop a system safety argument | Reports consumed by engineering reviewers | Hazard analysis, assumptions and argument ownership | Explain contribution to evidence, without claiming authorship of the argument |
Rowan’s initial interview answer was, “My automated tests proved the system safe.” The revised answer is: “I owned the Python framework and the reports it produced for our engineering reviewers. I can explain its interfaces, configuration tracking and failure investigation. The reviewers defined the acceptance criteria and decided how the results supported their wider assessment. I have not owned an automotive safety argument.”
Their completed discussion note adds three unresolved questions: Who defines the fault models and assumptions? Who reviews whether the test implementation addresses the intended requirement? Who has authority to accept limitations or request further evidence? These questions distinguish framework ownership from assessment authority without inventing a universal organizational chart.
For the senior V&V posting, Rowan prepares the infrastructure example first and marks automotive strategy ownership as a gap to discuss. For sensing safety, the missing analysis responsibility remains central. This is a preparation choice based on the stipulated experience, not an employer’s selection decision. A polished example cannot turn an unperformed analysis into work history.
Choose a role through the work you can discuss
Save one current employer description and highlight its main verbs: implement, analyze, derive, verify, review or approve. Attach a concrete contribution to each verb you genuinely performed. Keep the system context and responsible reviewer visible, especially where your code or report supported someone else’s decision.
Then name the most consequential gap. It may be real-time embedded implementation, automotive safety-analysis experience, sensor-domain understanding or validation leadership. Prepare a question about that responsibility before choosing a course or claiming a credential. Choose one lead from your saved search or browse recent roles on LandOffer.ai. Write a bounded contribution paragraph and a note identifying who reviewed the work, then compare both with the employer’s actual responsibilities.
Sources and Further Reading
- ISO 26262-6:2018 public abstract and status, checked October 22, 2026; public information only, not full paid-standard review.
- Zoox Embedded Software Engineer — Drive Systems, current employer description checked on the same date.
- Zoox Sensing and Perception System Safety Engineer, current employer description and analysis responsibilities.
- Zoox Senior Software Development Engineer in Test — Verification and Validation, current employer description and infrastructure ownership.
- NVIDIA Senior Software Engineer — AV Platform, JR2023594, current rendered description; earlier minimum-acceptance date does not establish a closing date.
- Zoox Senior Sensor Hardware Functional Safety Engineer, current hardware scope and bonus credential wording.


