Robotics Software Developer

HireSetu's note

Four seats, one advert

Four openings in the same team is a lot for a single posting, and the band runs from fresher to four years. The same advert is being read by a 2025 graduate and by someone with three years behind them, so the panel is likely filling more than one level. The degree is the hard filter: BE, B.Tech, M.Tech or MS. A diploma with strong robot projects won't clear that bar here.

Noida, in the office, near the robots

The job is permanent and onsite in Noida. Robotics software has a physical half: a machine to flash, a test floor to run, a fleet that behaves differently once it is moving. Being in the office keeps that part close, and it also means the job won't bend around a long commute. Noida's tech corridors are spread out, so know the sector before you sign up for a daily run.

A week of code and robot time

Work out the standard robotics toolkit before you apply: C++ and Python, ROS or ROS 2, simulation, and plenty of hours in logs. You build or tune one piece of a robot's behaviour, test it in simulation, then find out what the real machine does with it. When the fix isn't in the code, you are talking to mechanical and electrical engineers.

Have one system you can walk through end to end: what it did, what broke, what you changed.

The next two years

Warehouse and industrial robotics is expanding in India, and Addverb builds in that space. From a generalist start, people move into navigation and perception, motion planning and controls, fleet scheduling, or the platform layer that keeps deployments running. Two years deep in one of those beats four years of general fixes. Which one you get depends on the team you land in, so it is fair to ask about that when you talk to them.

Drafted with AI from Addverb's job posting and checked by Prashanth Jakkula before publishing. See our Editorial Policy.