Zoox
Part-Time Student Worker Software Engineer (6-month Contract)
About this role
Zoox seeks a part-time student software engineer to support the System Design and Mission Assurance team for 6 months. You'll develop full-stack tools and automation that measure safety metrics for autonomous robotaxis, working under senior mentorship on real-world autonomous vehicle challenges.
What you'll do
- Design and develop full-stack applications supporting safety evaluation processes
- Build tools and automation for tracking and analyzing Zoox safety metrics
- Collaborate with product managers and engineers on software enhancements
- Contribute to fail-operational design and safety case documentation
- Participate in code reviews and quality assurance practices
- Document technical implementations and engineering decisions
What they're looking for
- Full-stack web development (front-end and back-end)
- Software design and architecture fundamentals
- Database design and management
- Version control (Git)
- API development and integration
- Problem-solving and debugging
- Communication and collaboration
- Python or similar programming languages
Benefits
- Hands-on experience with cutting-edge autonomous vehicle technology
- Mentorship from senior engineers at an innovative company
- Real-world application of classroom learning
- Exposure to safety-critical systems design
- Flexible part-time schedule for students
Opens the official application on the employer’s site. No login required.
Zoox
Zoox develops autonomous vehicle technology and robotaxi systems, supported by manufacturing operations and AI validation infrastructure. The company is hiring for part-time student roles in hardware-software integration, manufacturing software engineering, AI testing and evaluation, and QA automation, as well as experienced engineers for simulation and AI performance assessment.
- Website
- zoox.com
Likely interview questions
- Tell us about a full-stack project you've built — what technologies did you use and what challenges did you overcome?
- How do you approach debugging when a feature isn't working as expected?