Skip to main content

Waymo

Software Engineer, Simulation Infrastructure

Mountain View, CA, USAFrom $216kfull-timemidAdded today

About this role

Waymo seeks a Software Engineer to build scalable simulation infrastructure that evaluates autonomous driving software at massive scale. You'll design systems, develop features, and maintain production services supporting engineers across multiple teams in a hybrid Mountain View role.

What you'll do

  • Design and architect simulation infrastructure features and systems
  • Write and debug code in C++ and/or Golang
  • Develop new simulation-based products and tools
  • Participate in on-call rotation for production systems
  • Collaborate with software engineers, data scientists, and system engineers

What they're looking for

  • C++ or Golang programming (3+ years)
  • FAANG-scale infrastructure design and maintenance
  • Distributed systems and scheduling
  • Observability and monitoring in large-scale systems
  • System design and architecture
  • Production troubleshooting and debugging
  • Google infrastructure experience (preferred)

Benefits

  • Discretionary annual bonus program
  • Equity incentive plan
  • Generous company benefits
  • Hybrid work arrangement
  • Work on autonomous driving technology
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Waymo

Waymo develops autonomous driving technology and vehicles, building the AI systems, simulation platforms, and infrastructure that power the Waymo Driver. The company is hiring for ML infrastructure engineers, platform engineers, labeling system developers, backend software engineers, and automotive systems engineers to scale its autonomous driving capabilities.

Website
waymo.com
View all jobs at Waymo

Likely interview questions

  • Describe your experience building or maintaining infrastructure at FAANG scale—what were the biggest scalability challenges you faced?
  • Tell us about a time you debugged a complex production issue in a distributed system. How did you approach it?