Senior/Staff Software Engineer, Core Connectivity

Zoox

  • Foster City, CA ; Seattle, WA
  • Hybrid
  • Staff/Principal level
  • 7+ yrs experience
  • Backend Engineering
  • Visa: not specified
  • $255k–$320k

The role in 30 seconds

Zoox is building the world's most advanced self-driving hardware and software solution, and nearly every part of it depends on moving data reliably across process, host, and network boundaries under hard latency and reliability budgets. The Software Core Connectivity team owns that data path end to end, including in-vehicle messaging and vehicle-to-cloud connectivity, and sets the transport and serialization abstractions the rest of the software organization builds on.

Is this role a fit for you?

The backgrounds this role is most likely to hire from, as RoleStack reads the posting.

Strong match

  • B2B infrastructure / API / developer tools
  • Internal tooling / back-office systems
  • Software, SaaS & AI Platform
  • Enterprise-scale (high availability, compliance, large distributed systems)
  • Growth-stage (scaling existing systems, reliability concerns)

Workable stretch

  • B2C consumer-facing application
  • Marketplace / multi-sided platform
  • Startup / greenfield (build from scratch, speed over polish)

Harder transition

  • Embedded systems / hardware-adjacent
  • Data platform / ML pipeline
  • Regulated environment (healthcare, finance, government)

Industry: Automotive & Transportation. See your personal match score

What they're really screening for

Must-haves

  • CORE Bachelor's or Master's degree in computer science, electrical / computer engineering, or equivalent experience, and 7+ years of experience in software development.
  • CORE Strong modern C++ on Linux, in large codebases with performance-critical paths.
  • CORE A background in transport or networking software, such as messaging systems, network protocols, or communication between distributed systems.
  • CORE Experience building low-latency systems, and a track record of measuring and reducing tail latency, using techniques such as zero-copy, shared memory, lock-free data structures, and cache-aware data layout.
  • CORE Solid systems fundamentals: concurrency, memory management, process lifecycle, sockets and the Linux networking stack.
  • CORE Hands-on experience with shared-memory IPC, pub/sub or RPC middleware such as DDS, ROS 2, or iceoryx, or serialization frameworks such as Protocol Buffers, nanopb, or FlatBuffers.
  • PLUS Experience with PTP (IEEE 1588) or other time synchronization across machines, or with UDP multicast, MTU and fragmentation behavior, or time-sensitive networking.
  • PLUS Robotics, automotive, aerospace, or another real-time or safety-relevant domain.

Nice-to-haves

  • PLUS Experience with PTP (IEEE 1588) or other time synchronization across machines, or with UDP multicast, MTU and fragmentation behavior, or time-sensitive networking.
  • PLUS Robotics, automotive, aerospace, or another real-time or safety-relevant domain.

Résumé keywords for this role

Terms the posting stresses. Include the ones you can honestly back up.

Tools & technologies

  • C++
  • Linux
  • Protocol Buffers
  • nanopb
  • FlatBuffers
  • DDS
  • ROS 2
  • iceoryx
  • PTP (IEEE 1588)
  • UDP multicast
  • MTU
  • IPC
  • zero-copy
  • shared-memory
  • lock-free queues

Concepts & phrases

  • Senior/Staff Software Engineer, Core Connectivity
  • world's most advanced self-driving hardware and software solution
  • moving data reliably
  • Sensor frames to perception
  • planner decisions to vehicle controls
  • telemetry to the cloud
  • remote operator video
  • hard latency and reliability budgets
  • process, host, and network boundaries
  • Software Core Connectivity team
  • data path end to end
  • in-vehicle messaging
  • inter-process and inter-host transport
  • vehicle's internal network
  • vehicle-to-cloud connectivity

Words that count as the same thing: "self-driving hardware and software solution" ≈ autonomous vehicle technology, autonomous driving systems · "self-driving" ≈ autonomous driving · "latency budgets" ≈ latency requirements, performance targets · "reliability budgets" ≈ reliability requirements, uptime targets · "end to end latency" ≈ overall latency, total latency

Check my résumé against these keywords

Hiring at Zoox

All Zoox hiring data

Open senior roles RoleStack tracks right now, posted in the last 30 days.

More open roles at Zoox

Full job description from Zoox

From Zoox's posting. View the original

Zoox is building the world's most advanced self-driving hardware and software solution, and nearly every part of it depends on moving data reliably. Sensor frames to perception, planner decisions to vehicle controls, telemetry to the cloud, and remote operator video back down again. All of it crosses process, host, and network boundaries under hard latency and reliability budgets, on a vehicle that has to keep working when a link degrades or a network gets congested.
The Software Core Connectivity team owns that data path end to end: in-vehicle messaging (pub/sub, RPC, inter-process and inter-host transport), the vehicle's internal network, and vehicle-to-cloud connectivity. It also owns the transport and serialization abstractions the rest of the software organization builds on. Every one of those paths crosses a team boundary, so the work happens alongside firmware, product security, simulation, manufacturing, and IT, and those partners rely on this team for transport and networking depth to achieve their goals. As the team leader you will own the roadmap and the release commitments, and you will spend a real share of your time in those partnerships.

Show full description Show less

• Design and build low-latency inter-process and inter-host transport in C++: zero-copy data paths, shared-memory buffers, and lock-free queues. Measure and drive down end-to-end latency and jitter as message volume grows.

• Make the transport hold up when processes crash or restart, hosts start out of order, and networks drop or delay packets. Chase fleet and simulation issues to root cause and fix them in the design.

• Build the pub/sub and RPC messaging APIs application teams build on, so they get the delivery, ordering, and latency guarantees they need without having to understand the transport underneath.

• Evolve message schemas and the Protocol Buffers based serialization layer: schema evolution, compact encodings, and moving existing users onto new formats without breaking anyone.

• Set technical direction for a part of the stack and lead designs that span several teams.

• Bachelor's or Master's degree in computer science, electrical / computer engineering, or equivalent experience, and 7+ years of experience in software development.

• Strong modern C++ on Linux, in large codebases with performance-critical paths.

• A background in transport or networking software, such as messaging systems, network protocols, or communication between distributed systems.

• Experience building low-latency systems, and a track record of measuring and reducing tail latency, using techniques such as zero-copy, shared memory, lock-free data structures, and cache-aware data layout.

• Solid systems fundamentals: concurrency, memory management, process lifecycle, sockets and the Linux networking stack.

• Hands-on experience with shared-memory IPC, pub/sub or RPC middleware such as DDS, ROS 2, or iceoryx, or serialization frameworks such as Protocol Buffers, nanopb, or FlatBuffers.

• Experience with PTP (IEEE 1588) or other time synchronization across machines, or with UDP multicast, MTU and fragmentation behavior, or time-sensitive networking.

• Robotics, automotive, aerospace, or another real-time or safety-relevant domain.

FAQ

How much does a Senior/Staff Software Engineer, Core Connectivity at Zoox make?

The posted pay for this role is $255k–$320k a year.

How much experience do you need?

The posting asks for 7+ years in software development. It is a staff/principal-level role.

Does Zoox sponsor visas for this role?

The posting does not say whether visa sponsorship is available. Ask the recruiter before you apply.

Is this role remote?

It is a hybrid role: part remote, part in the office.

What tools and technologies does the posting mention?

C++, Linux, Protocol Buffers, nanopb, FlatBuffers, DDS, ROS 2, iceoryx, PTP (IEEE 1588), UDP multicast, MTU, IPC, zero-copy, shared-memory, lock-free queues.