Robotics Software Engineer - AMR
Unbox Robotics (company site, opens in a new tab)2–5 yrsPuneOn-siteDirect career pageEst. 10–20 LPA
Posted 3d ago
Reach people at Unbox Robotics
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Unbox Robotics you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own the design, development, and deployment of production AMR software spanning autonomy, localization, motion control, and fleet integration.
- Build and tune SLAM, sensor fusion, obstacle avoidance, path planning, and robot behavior for dynamic industrial workflows and docking.
- Validate releases in simulation and on hardware; profile edge-device performance and lead field-issue diagnosis to improve reliability.
Minimum Requirements
- Work Experience Required: 2–5 years in robot software engineering focused on mobile robotics or AMRs.
- B.E./B.Tech./M.Tech in Computer Science, Robotics, Electronics, Mechatronics, Mechanical, or an allied engineering field.
- Strong modern C++ and Python; hands-on ROS/ROS 2 and Nav2; practical experience with SLAM/localization, planning and control, sensor integration/fusion, and robot hardware interfaces.
- Work location and mode: Pune, in-campus.
Ideal Candidate Profile
- Has worked on real AMRs or mobile robots, applying navigation and autonomy software in dynamic operating environments—not only simulation.
- Can work across the robotics stack, from modular C++/Python and ROS 2 software to sensors, controllers, edge hardware, testing, and field debugging.
- Fleet-management integration, precision docking, perception/edge inference, industrial functional safety, or Docker experience are useful shortlist signals.