May Mobility
Robotics Engineer II
Ann Arbor, MIFrom $155kmidAdded 1 month ago
About this role
May Mobility is seeking a Robotics Engineer II to contribute to the development of autonomous vehicles that enhance urban transportation. The role involves training and testing machine learning models, optimizing software, and validating systems in real-world scenarios.
What you'll do
- Train and test machine learning models for autonomy software
- Optimize software for reliability and low latency
- Coordinate on-vehicle tests for software validation
- Diagnose issues through May Field Response process
- Design data collection strategies for ML models
- Develop performance analysis tools for support engineers
What they're looking for
- 2+ years of robotics software experience
- Bachelor's in Robotics, Computer Science, or related field
- Basic ML model understanding
- Knowledge of lidar, camera, or radar systems
- Strong programming in C/C++/Python
- Familiarity with software concepts and development tools
- Experience with perception and planning in autonomous driving
- CUDA and GPU processing knowledge
Benefits
- Comprehensive healthcare plans
- Health Savings and Flexible Spending Accounts
- Retirement benefits with employer match
- Generous paid parental leave
- Flexible vacation policy
- Total Wellness Program
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
May Mobility
May Mobility develops autonomous vehicle technology for urban transportation. The company is hiring for engineering roles including systems engineers, robotics engineers, machine learning engineers, and release engineers to advance autonomous driving capabilities.
- Website
- maymobility.com
Likely interview questions
- Tell us about your experience integrating and testing machine learning models in commercial robotics systems. What challenges did you face and how did you overcome them?
- Describe your experience with perception sensors like lidar, camera, or radar. How have you debugged hardware interface issues in a production environment?