Staff Compute & Controls Systems Engineer
Zoox · Foster City, CA · 1 mo ago
On-siteEngineering$226k–$311k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description. We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse content: The posting includes:
- Intro about Zoox (company description). Could be "About the role"? Actually "About the role" is typical heading for role description. We can put the paragraph describing role responsibilities under "Responsibilities". The intro about Zoox maybe could be "About the role"? But they said do NOT repeat job title as heading. Use headings for sections. We need to decide which sections have content.
We have:
- Responsibilities: list of duties: "In This Role, You Will Apply compute, controls, and systems engineering principles to define traceable computing requirements from product goals Engage with product, HW/SW engineering, production, safety, and business teams to author detailed requirements for compute and control modules. Analyze tradeoffs and drive consensus with product, hardware, and software teams to converge on compute architecture for current and new vehicle platforms. Gather and analyze critical data to define metrics, qualify systems for release, and influence system design decisions based on evidence-based insights. Create and maintain clear, precise documentation to support system designs, architectural decisions, and processes while ensuring cross-team alignment. Work with software and firmware teams during implementation to ensure requirements are met. Lead the sign-off of compute and autonomy systems with cross-functional teams. Assist with the development and review of Verification and Validation (V&V) plans, and analyze test results for compute and controls systems. Conduct System FMEA (SFMEA) and failure mode analysis in the context of part-level reliability to identify and mitigate potential failure modes early in the design cycle. Support Root Cause Analysis (RCA) for safety-related compute platform field failures. Collaborate with partner teams to improve diagnostic coverage against single-point and multiple-point latent failures on existing hardware platforms. Support functional safety analyses to ensure the safety concept remains compatible with the core objectives of ISO 26262."
That's a long paragraph; we can break into bullet list for responsibilities.
- Qualifications: list: "B.S., M.S., or equivalent degree in Aerospace, Automotive, Robotics, Computer Science, Electrical, Mechanical, or Systems Engineering. 8+ years of relevant, staff-level experience in automotive, ADAS, autonomous vehicles, aerospace, or robotics, with an emphasis on systems-level design, validation, and safety analysis for complex, mission-critical systems with high levels of fail-operational redundancy. Analytical skills and a passion for writing clear, concise, and verifiable requirements for owned compute and controls systems. Strong EE fundamentals, including knowledge of compute architectures (e.g., x86, ARM), communication protocols (I2C, UART, SPI, CAN, LIN, USB, GMSL, FPD-Link), high-speed signals, sensing, and power electronics. Experience with FMEDA or FMEA for safety-critical systems, as well as automotive safety standards such as ISO 26262 (Functional Safety) and ISO 21448 (SOTIF)."
- Bonus Qualifications: "PhD in a related technical field. Experience working on high assurance compute solutions and GPU hardware, along with knowledge of AI models used for perception, behavior planning, and trajectory planning. Experience with sensor interface design and data throughput analysis, including bandwidth, latency, and timing/synchronization requirements across the compute architecture. Experience with hazard analysis, functional decomposition, validation, and verification."
- Pay: "$226,000 - $311,000 a year"
- Benefits: Not explicitly listed. There's no benefits section. So we should not include Benefits.
- Schedule: Not mentioned. So no Schedule.
- Skills: Could be derived from qualifications? But we have Qualifications and Bonus Qualifications. Could combine as Qualifications and maybe Skills? The instruction says use headings for sections like Skills if posting has real specific content. The posting does not have a separate "Skills" section; qualifications cover skills. We could still include a Skills section if we extract skills from qualifications, but that might be considered inventing? It's okay to rephrase but must preserve all substantive info. We could put skills under Qualifications; better to have Qualifications and Bonus Qualifications as separate sections? The instruction only lists certain headings; but we can also create other headings? It says use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse content: The posting includes:
- Intro about Zoox (company description). Could be "About the role"? Actually "About the role" is typical heading for role description. We can put the paragraph describing role responsibilities under "Responsibilities". The intro about Zoox maybe could be "About the role"? But they said do NOT repeat job title as heading. Use headings for sections. We need to decide which sections have content.
We have:
- Responsibilities: list of duties: "In This Role, You Will Apply compute, controls, and systems engineering principles to define traceable computing requirements from product goals Engage with product, HW/SW engineering, production, safety, and business teams to author detailed requirements for compute and control modules. Analyze tradeoffs and drive consensus with product, hardware, and software teams to converge on compute architecture for current and new vehicle platforms. Gather and analyze critical data to define metrics, qualify systems for release, and influence system design decisions based on evidence-based insights. Create and maintain clear, precise documentation to support system designs, architectural decisions, and processes while ensuring cross-team alignment. Work with software and firmware teams during implementation to ensure requirements are met. Lead the sign-off of compute and autonomy systems with cross-functional teams. Assist with the development and review of Verification and Validation (V&V) plans, and analyze test results for compute and controls systems. Conduct System FMEA (SFMEA) and failure mode analysis in the context of part-level reliability to identify and mitigate potential failure modes early in the design cycle. Support Root Cause Analysis (RCA) for safety-related compute platform field failures. Collaborate with partner teams to improve diagnostic coverage against single-point and multiple-point latent failures on existing hardware platforms. Support functional safety analyses to ensure the safety concept remains compatible with the core objectives of ISO 26262."
That's a long paragraph; we can break into bullet list for responsibilities.
- Qualifications: list: "B.S., M.S., or equivalent degree in Aerospace, Automotive, Robotics, Computer Science, Electrical, Mechanical, or Systems Engineering. 8+ years of relevant, staff-level experience in automotive, ADAS, autonomous vehicles, aerospace, or robotics, with an emphasis on systems-level design, validation, and safety analysis for complex, mission-critical systems with high levels of fail-operational redundancy. Analytical skills and a passion for writing clear, concise, and verifiable requirements for owned compute and controls systems. Strong EE fundamentals, including knowledge of compute architectures (e.g., x86, ARM), communication protocols (I2C, UART, SPI, CAN, LIN, USB, GMSL, FPD-Link), high-speed signals, sensing, and power electronics. Experience with FMEDA or FMEA for safety-critical systems, as well as automotive safety standards such as ISO 26262 (Functional Safety) and ISO 21448 (SOTIF)."
- Bonus Qualifications: "PhD in a related technical field. Experience working on high assurance compute solutions and GPU hardware, along with knowledge of AI models used for perception, behavior planning, and trajectory planning. Experience with sensor interface design and data throughput analysis, including bandwidth, latency, and timing/synchronization requirements across the compute architecture. Experience with hazard analysis, functional decomposition, validation, and verification."
- Pay: "$226,000 - $311,000 a year"
- Benefits: Not explicitly listed. There's no benefits section. So we should not include Benefits.
- Schedule: Not mentioned. So no Schedule.
- Skills: Could be derived from qualifications? But we have Qualifications and Bonus Qualifications. Could combine as Qualifications and maybe Skills? The instruction says use headings for sections like Skills if posting has real specific content. The posting does not have a separate "Skills" section; qualifications cover skills. We could still include a Skills section if we extract skills from qualifications, but that might be considered inventing? It's okay to rephrase but must preserve all substantive info. We could put skills under Qualifications; better to have Qualifications and Bonus Qualifications as separate sections? The instruction only lists certain headings; but we can also create other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. We have Qualifications and Bonus Qualifications; we could combine them into Qualifications (including bonus). Or we could have Qualifications and Skills separate. Since bonus qualifications are extra, we could put them under Qualifications as well.
We also have "About the role": maybe the introductory paragraph about Zoox and the role summary: "Zoox is developing the first ground-up, fully autonomous vehicle fleet and the supporting ecosystem required to bring this technology to market. Sitting at the intersection of artificial intelligence, robotics, and design, Zoox aims to provide the next generation of mobility-as-a-service in urban environments. We're looking for top talent that shares our passion and wants to be part of a fast-moving and highly execution-oriented team. As a Staff Compute & Controls Systems Engineer in Advanced Hardware Engineering (AHE), you will be responsible for developing and documenting requirements for compute and control system modules, while also driving key functional safety analyses for our compute platforms. You will work across departments at Zoox to build a system-level understanding of how AHE hardware enables critical operational functions, and you will lead the Compute Safety Analysis (FMEDA) that ensures those functions fail safely. You will work closely with hardware and software architects, and with design, safety, manufacturing, and test engineers, to ensure requirements are verified throughout the engineering development process. Your assessments will be critical to meeting milestones as we develop new generations of hardware."
That could be "About the role". Then responsibilities as separate.
We also have "Requirements" maybe same as Qualifications? The instruction includes Requirements heading. Could use Requirements for the mandatory qualifications, and Skills for bonus? But we have both Qualifications and Bonus Qualifications. Let's map:
- About the role: intro paragraph.
- Responsibilities: bullet list of duties.
- Requirements: mandatory qualifications (B.S., 8+ years, analytical skills, EE fundamentals, FMEDA/FMEA experience, ISO 26262, ISO 21448).
- Skills: maybe bonus qualifications (PhD, high assurance compute, GPU hardware, AI models, sensor interface design, hazard analysis, functional decomposition, validation, verification). Or we could treat Skills as the technical skills list (compute architectures, protocols, etc.) but those are in Requirements. Better to put bonus under Skills.
- Pay: salary range.
We should not include Benefits or Schedule.
We must not include boilerplate like AI hiring process etc. That's boilerplate? It's about hiring process; maybe we should remove as it's not substantive about the role. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The AI hiring process note is not exactly those but could be considered boilerplate? It's about hiring process; maybe we should keep? It's not about role. I'd say remove it as it's not substantive about the job. Also the line "We may use artificial intelligence (AI) tools..." is not about role; remove.
Now produce HTML fragment:
About the role
About the role
Zoox is developing the first ground-up, fully autonomous vehicle fleet and the supporting ecosystem required to bring this technology to market. Sitting at the intersection of artificial intelligence, robotics, and design, Zoox aims to provide the next generation of mobility-as-a-service in urban environments. We're looking for top talent that shares our passion and wants to be part of a fast-moving and highly execution-oriented team. As a Staff Compute & Controls Systems Engineer in Advanced Hardware Engineering (AHE), you will be responsible for developing and documenting requirements for compute and control system modules, while also driving key functional safety analyses for our compute platforms. You will work across departments at Zoox to build a system-level understanding of how AHE hardware enables critical operational functions, and you will lead the Compute Safety Analysis (FMEDA) that ensures those functions fail safely. You will work closely with hardware and software architects, and with design, safety, manufacturing, and test engineers, to ensure requirements are verified throughout the engineering development process. Your assessments will be critical to meeting milestones as we develop new generations of hardware.
Responsibilities
- Apply compute, controls, and systems engineering principles to define traceable computing requirements from product goals.
- Engage with product, HW/SW engineering, production, safety, and business teams to author detailed requirements for compute and control modules.
- Analyze tradeoffs and drive consensus with product, hardware, and software teams to converge on compute architecture for current and new vehicle platforms.
- Gather and analyze critical data to define metrics, qualify systems for release, and influence system design decisions based on evidence-based insights.
- Create and maintain clear, precise documentation to support system designs, architectural decisions, and processes while ensuring cross-team alignment.
- Work with software and firmware teams during implementation to ensure requirements are met.
- Lead the sign-off of compute and autonomy systems with cross-functional teams.
- Assist with the development and review of Verification and Validation (V&V) plans, and analyze test results for compute and controls systems.
- Conduct System FMEA (SFMEA) and failure mode analysis in the context of part-level reliability to identify and mitigate potential failure modes early in the design cycle.
- Support Root Cause Analysis (RCA) for safety-related compute platform field failures.
- Collaborate with partner teams to improve diagnostic coverage against single-point and multiple-point latent failures on existing hardware platforms.
- Support functional safety analyses to ensure the safety concept remains compatible with the core objectives of ISO 26262.
Requirements
- B.S., M.S., or equivalent degree in Aerospace, Automotive, Robotics, Computer Science, Electrical, Mechanical, or Systems Engineering.
- 8+ years of relevant, staff-level experience in automotive, ADAS, autonomous vehicles, aerospace, or robotics, with an emphasis on systems-level design, validation, and safety analysis for complex, mission-critical systems with high levels of fail-operational redundancy.
- Analytical skills and a passion for writing clear, concise, and verifiable requirements for owned compute and controls systems.
- Strong EE fundamentals, including knowledge of compute architectures (e.g., x86, ARM), communication protocols (I2C, UART, SPI, CAN, LIN, USB, GMSL, FPD-Link), high-speed signals, sensing, and power electronics.
- Experience with FMEDA or FMEA for safety-critical systems, as well as automotive safety standards such as ISO 26262 (Functional Safety) and ISO 21448 (SOTIF).
Skills
- PhD in a related technical field.
- Experience working on high assurance compute solutions and GPU hardware, along with knowledge of AI models used for perception, behavior planning, and trajectory planning.
- Experience with sensor interface design and data throughput analysis, including bandwidth, latency, and timing/synchronization requirements across the compute architecture.
- Experience with hazard analysis, functional decomposition, validation, and verification.
Pay
$226,000 - $311,000 a year
We must not include extra sections