Waymo
2027 Summer Intern, BS/MS, Software Engineering, Commercialization
Mountain View, California, United States; San Francisco, California, United States$124.8k–$145.6kinternshipinternAdded today
About this role
Waymo seeks BS/MS interns to develop backend infrastructure and software systems for its autonomous robotaxi platform. You'll work on ride-hailing marketplace optimization, fleet management, ML models for routing and demand prediction, and core infrastructure reliability.
What you'll do
- Develop and maintain backend infrastructure for stability and reliability
- Build features in event response and vehicle maintenance tracking systems
- Optimize robotaxi marketplace supply-demand balancing
- Design backend systems supporting ride-hailing and AV fleet management
- Create ML and optimization models for vehicle routing, demand forecasting, and dispatch
What they're looking for
- Backend development and distributed systems
- C++
- Infrastructure and internal tools development
- Machine learning and optimization modeling
- Software architecture and scalability
- Technical communication with engineers and stakeholders
- Python or similar languages
Benefits
- Hybrid onsite internship in Mountain View or San Francisco
- Eligible to participate in company benefits programs
- Mentorship from industry leaders
- Work on Level 4 autonomous driving technology
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
Likely interview questions
- Describe your experience with distributed systems—what challenges have you encountered and how did you solve them?
- Walk us through a backend infrastructure project you've worked on; how did you approach scaling or reliability?