Software Engineer - C++ On-Vehicle Data
About the role
, etc. We must not repeat job title. No metadata like Job ID. Remove boilerplate: accommodations, final note, AI tools, etc. Also remove duplicated lines. We need to preserve all substantive info. Let's extract. Role description: "Shipping the software that powers Zoox’s autonomous vehicles is an extremely challenging job. As a Software Engineer on the Core Data team, you will help build the foundational systems that capture, persist, move and retrieve the critical data generated by our fleet of robots. Our systems connect real-time vehicle software with the engineering and operational workflows requiring fleet data. This includes making critical data available for development, validation, fleet operations, incident investigation, and continuous improvement of the autonomous driving stack. You will tackle complex challenges involving high-speed data, constrained compute & storage resources, multi-host architectures, and fault-tolerant design. This role combines hands-on implementation and systems-level problem solving with opportunities to influence the long-term architecture of Zoox’s vehicle data systems. You will collaborate across the organization to define requirements and deliver practical, reliable solutions to ambiguous cross-functional problems." Then bullet list under "In This Role, You Will": - Contribute to the technical architecture and implementation of Zoox’s on-vehicle data systems - Design and develop reliable, high-performance systems for capturing, storing, retrieving, and transmitting vehicle data with strict real-time and resource constraints - Own complex technical problems from initial investigation through design, implementation, validation, and rollout - Collaborate across teams through requirements definition, design reviews, and code reviews Qualifications: Bachelor’s degree in computer science, engineering, mathematics, or a related field and 3+ years of professional software development experience Strong proficiency in modern C++ Experience with multithreading, concurrency, inter-process communication, or networking Strong problem-solving skills and the ability to investigate issues across multiple software and hardware layers Ability to communicate technical ideas clearly and collaborate effectively across teams Bonus Qualifications: Experience with robotics, autonomous vehicles, or other distributed real-time systems Familiarity with filesystems, storage hardware, or high-throughput data systems Experience with performance analysis and profiling Pay: $175,000 - $250,000 a year. There are three major components to compensation: salary, Amazon RSUs, Zoox Stock Appreciation Rights. A sign-on bonus may be offered. The listed range applies only to base salary. Compensation will vary based on geographic location and level. Leveling, as well as positioning within a level, is determined by a range of factors, including, but not limited to, a candidate's relevant years of experience, domain knowledge, and interview performance. The salary range listed in this posting is representative of the range of levels Zoox is considering for this position. Benefits: Zoox also offers a comprehensive package of benefits, including paid time off (e.g. sick leave, vacation, bereavement), unpaid time off, Zoox Stock Appreciation Rights, Amazon RSUs, health insurance, long-term care insurance, long-term and short-term disability insurance, and life insurance. No schedule info. We need sections: About the role (maybe the introductory paragraph), Responsibilities (the bullet list), Requirements (maybe the qualifications?), Qualifications (maybe education/experience?), Skills (maybe technical proficiencies), Benefits, Pay. We need to avoid duplication. Let's map: About the role: first paragraph describing role. Responsibilities: the bullet list under "In This Role, You Will". Requirements: maybe the core qualifications (Bachelor's degree + 3+ years, proficiency in C++, multithreading, problem-solving, communication). Could be separate. Qualifications: maybe the bonus qualifications? Or we could treat "Qualifications" as the required qualifications and "Skills" as bonus? But we need to follow instruction: Use sections only when posting has real specific content. We have both required and bonus qualifications. Could put required under "Qualifications" and bonus under "Skills". Or "Requirements" for required, "Qualifications" for bonus? Let's decide. We have: "Qualifications Bachelor’s degree..." then list of strong proficiency etc. That's required qualifications. Then "Bonus Qualifications" list. Thus we can put required underQualifications
and bonus underSkills
. Or we could put required under Requirements and bonus under Qualifications. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: intro paragraph. - Responsibilities: bullet list. - Requirements: maybe the required qualifications (Bachelor's + 3 years, etc.)? But we already used Qualifications for required. Let's think: Usually Requirements = required qualifications. Qualifications = maybe preferred/bonus. But we have both required and bonus. Could put required under Requirements and bonus under Qualifications. Then Skills could be technical proficiencies (C++, multithreading, etc.) but those are also required. Hmm. Better: Use Requirements for the mandatory education/experience. Use Qualifications for the technical proficiencies (C++, multithreading, etc.). Use Skills for bonus qualifications (robotics, filesystems, performance analysis). That seems plausible. Let's extract: Requirements: Bachelor’s degree in computer science, engineering, mathematics, or a related field and 3+ years of professional software development experience. Qualifications: Strong proficiency in modern C++; Experience with multithreading, concurrency, inter-process communication, or networking; Strong problem-solving skills and the ability to investigate issues across multiple software and hardware layers; Ability to communicate technical ideas clearly and collaborate effectively across teams. Skills (bonus): Experience with robotics, autonomous vehicles, or other distributed real-time systems; Familiarity with filesystems, storage hardware, or high-throughput data systems; Experience with performance analysis and profiling. Benefits: list. Pay: salary range and components. Now produce HTML. We need- for any list of duties/requirements/benefits. For prose use
. Thus:
About the role
Shipping the software that powers Zoox’s autonomous vehicles is an extremely challenging job. As a Software Engineer on the Core Data team, you will help build the foundational systems that capture, persist, move and retrieve the critical data generated by our fleet of robots. Our systems connect real-time vehicle software with the engineering and operational workflows requiring fleet data. This includes making critical data available for development, validation, fleet operations, incident investigation, and continuous improvement of the autonomous driving stack. You will tackle complex challenges involving high-speed data, constrained compute & storage resources, multi-host architectures, and fault-tolerant design. This role combines hands-on implementation and systems-level problem solving with opportunities to influence the long-term architecture of Zoox’s vehicle data systems. You will collaborate across the organization to define requirements and deliver practical, reliable solutions to ambiguous cross-functional problems.
Responsibilities
- Contribute to the technical architecture and implementation of Zoox’s on-vehicle data systems
- Design and develop reliable, high-performance systems for capturing, storing, retrieving, and transmitting vehicle data with strict real-time and resource constraints
- Own complex technical problems from initial investigation through design, implementation, validation, and rollout
- Collaborate across teams through requirements definition, design reviews, and code reviews
Requirements
Bachelor’s degree in computer science, engineering, mathematics, or a related field and 3+ years of professional software development experience.
Qualifications
- Strong proficiency in modern C++
- Experience with multithreading, concurrency, inter-process communication, or networking
- Strong problem-solving skills and the ability to investigate issues across multiple software and hardware layers
- Ability to communicate technical ideas clearly and collaborate effectively across teams
Skills
- Experience with robotics, autonomous vehicles, or other distributed real-time systems
- Familiarity with filesystems, storage hardware, or high-throughput data systems
- Experience with performance analysis and profiling
Benefits
- Paid time off (e.g. sick leave, vacation, bereavement)
- Unpaid time off
- Zoox Stock Appreciation Rights
- Amazon RSUs
- Health insurance
- Long-term care insurance
- Long-term and short-term disability insurance
- Life insurance
Pay
$175,000 - $250,000 a year base salary. Compensation includes salary, Amazon Restricted Stock Units (RSUs), and Zoox Stock Appreciation Rights; a sign-on bonus may be offered. The listed range applies only to the base salary. Compensation will vary based on geographic location and level. Leveling, as well as positioning within a level, is determined by a range of factors, including, but not limited to, a candidate's relevant years of experience, domain knowledge, and interview performance. The salary range listed in this posting is representative of the range of levels Zoox is considering for this position.
Check we didn't include schedule. Good. We removed boilerplate: accommodations, final note, AI tools, etc. Also removed duplicated lines like "About Zoox" paragraph? Actually we omitted the About Zoox paragraph. That is substantive? It describes company mission. Could be considered substantive. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The About Zoox paragraph is substantive. Should we include it? Possibly under About the role? But we already have About the role describing role. The About Zoox paragraph is about company. Could be included as a separate section? There's no heading for company overview. Could we add it to About the role? Might be okay to append after role description. But we must not invent headings. We could add a paragraph after the role description within About the role section. That would preserve the info. Let's incorporate. Thus About the role section will have two paragraphs: first about role, second about Zoox. Let's extract About Zoox paragraph: "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 robotics, machine learning, 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. Follow us on LinkedIn" We should remove "Follow us on LinkedIn" as it's maybe boilerplate? It's a call to action, maybe considered navigation? Might be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Follow us on LinkedIn" is like social media link, could be considered navigation. Safer to remove it. Keep the rest. Thus About the role paragraph: combine role description and Zoox description. Let's craft:Shipping the software that powers Zoox’s autonomous vehicles is an extremely challenging job. As a Software Engineer on the Core Data team, you will help build the foundational systems that capture, persist, move and retrieve the critical data generated by our fleet of robots. Our systems connect real-time vehicle software with the engineering and operational workflows requiring fleet data