Robotics Software (ROS 2) Intern
Six months on the autonomy stack behind our agri rovers and warehouse AMRs — ROS 2 nodes, sensor bring-up and field runs on real hardware, not only in simulation.
What you will do
- Write and test ROS 2 nodes in Python and C++ for navigation, teleoperation and sensor handling.
- Bring up sensors — IMU, GNSS, lidar and depth cameras — and verify their data on real hardware.
- Run the stack in Gazebo, then reproduce the same runs on a rover in the yard.
- Record and replay rosbags to trace failures, and write up what actually went wrong.
- Help tune navigation and control parameters, logging the before and after.
- Keep launch files, URDF and setup notes current so a teammate can reproduce a run.
What we look for
- Python, plus enough C++ to read and modify an existing node.
- Linux at the command line — building a workspace, reading logs, working over SSH on a robot.
- Any exposure to ROS or ROS 2, including coursework or a personal project.
- A working understanding of coordinate frames and transforms.
- Git for day-to-day work.
- Gazebo, OpenCV or PyTorch experience is a plus, not a requirement.
Who can apply
- B.Tech in ECE, E&TC, CSE, IT, Robotics, Mechatronics or equivalent.
- Third-year and final-year students, plus candidates who graduated within the last 12 months.
- Able to attend on-site in Jajpur Town for the full six months.
- Registered on the AICTE National Internship Portal — preferred, not mandatory.
What you get
- A stipend of ₹5,000 per month, paid monthly.
- Six months on robots that run outside the lab, with real sensor noise and real failures.
- Access to the rover platform, test area and the full sensor suite.
- One-to-one mentoring from a senior engineer, with a weekly review.
- An internship completion certificate, and the AICTE portal record filed on completion.
- First consideration when we next open a junior engineer role.
How we select
- 1Apply through the form — tell us your college, branch, year and internship window.
- 2A short technical call, around 30 minutes.
- 3A small take-home task: a short Python or C++ exercise, or reading an existing ROS node.
- 4Offer, with start date and reporting details confirmed in writing.