Robotics Research Engineer (L3)
Perceptyne Technologies Private Limited
·Oct 12, 2026
- Workplace
- Onsite
- Department
- IT
- Education
- Master
- Source
- Keka
Description
- Co-Own the architecture. You will be part of defining how the robot's software stack is structured — module boundaries, interfaces, threading and real-time design, data flow between perception, planning, and control, configuration and versioning across robot variants. You'll be part of making the calls that decide whether shipping robot #50 is routine or painful, and you'll be able to defend those calls from first principles.
- Design motion planning and control algorithms for dual-arm dexterous manipulation, including contact-rich tasks where "plan a collision-free path" isn't enough.
- Build software that scales from one lab robot to a fleet in customer plants — reliable, observable, maintainable by people who didn't write it.
- Squeeze real-time performance out of the stack: multi-threaded C++, tight loops, latency budgets you can measure and defend.
- Prototype hypotheses in simulation, then prove or kill them on hardware. The robot is the referee.
- Work across the full system — perception, planning, manipulation, control, AI model training and deployment, tooling and UI, hardware bring-up, on-site deployment.
- Debug problems that cross domains, where the fault could be in your solver, the driver, the calibration, the gripper, or the mechanics. Find it anyway.
- Translate state-of-the-art robotics and AI research into something testable in days, not quarters.
- Plan and deliver: break large efforts into milestones, estimate honestly, flag slips early, and drive work to completion.
- Bachelor's or Master's in CS, Electrical, Electronics, Instrumentation, or Mechanical Engineering.
- 4+ years building software for real robots, with hands-on manipulator experience.
- Demonstrated software architecture ability — you've designed a non-trivial robotics or real-time system, not just contributed modules to one. You can explain your abstractions, your trade-offs, and what you'd do differently now.
- Excellent C++ and Python. Real multi-threaded, real-time production code.
- Deep hands-on ROS/ROS 2, plus MoveIt, Nav2, OMPL and similar frameworks.
- Strong fundamentals in robotic manipulation: forward/inverse kinematics, Jacobians, dynamics, trajectory generation, control schemes.
- Real command of the underlying math — linear algebra, transforms, coordinate frames, calculus — and genuine physical intuition. You should sanity-check a result on a whiteboard before you trust the plot.
- Hands-on with depth cameras, lidar, and the messy reality of sensor data.
- Deep experience, without losing first-principles thinking.
- A large vision, without losing attention to detail.
- Disruptive technology, shipped to market as fast as possible.