Robotics Research Engineer - L1

What We’re Looking For

We care most about strong fundamentals, hands-on evidence that you like building things, and the persistence to investigate a problem until the robot behaves better.

Bachelor’s degree in Computer Science, Electrical, Electronics, Instrumentation, Mechanical Engineering, Robotics, or a related discipline—or equivalent demonstrated project experience.

1+ years of experience in building software or hardware for robot arms, mobile robots, drones, autonomous vehicles, or custom mechatronic systems.

Working proficiency in C++ and/or Python. You should be comfortable reading existing code, debugging it, and writing clean additions to it.

Familiarity with Linux, Git, command-line tools, and standard software-development workflows.

Basic experience with ROS or ROS 2, and a clear willingness and ability to master it quickly.

Understanding of core robotics concepts: coordinate frames, transformations, forward and inverse kinematics, trajectories, sensors, feedback, and control.

Comfort with linear algebra and geometry: vectors, matrices, rotations, transforms, and coordinate systems.

A practical debugging mindset: you can use logs, plots, measurements, and experiments to narrow down why something fails.

Willingness to work directly with physical robots in our Hyderabad lab and deployment environments.

Nice to Have

These are helpful, not mandatory. Please apply if the core role fits you even if you do not check every box.

Prior industry / academic Internship, research, personal-project in relevant field is an added advantage

ROS 2 packages such as MoveIt, RViz, Gazebo, Isaac Sim, rosbag, TF2, or ros2_control.

Familiarity with motion planning, trajectory interpolation, PID control, impedance control, force/torque sensing, or grasp planning.

Experience with cameras, depth sensors, LiDAR, IMUs, encoders, or sensor calibration.

Exposure to OpenCV, computer vision, object detection, pose estimation, or machine learning.

Familiarity with embedded systems, microcontrollers, CAN, EtherCAT, serial protocols, motor drivers, or actuator control.

Contributions to a GitHub project, robotics competition, research project, hackathon, internship, or a robot you built yourself.

How We Work

At Perceptyne, the robot is the referee.

A simulation result, a paper result, or a beautiful architecture diagram matters only when it helps the physical machine perform a useful task reliably. We move quickly, test ideas early, and work across disciplines because real robots do not respect team boundaries.

We look for people with grit and dedication: engineers who keep working at a problem when the first prototype fails, who care about the unglamorous details that determine whether a system survives outside the lab, and who take ownership from first experiment to reliable deployment.

You will thrive here if you:

Prefer building and testing over discussing ideas indefinitely.

Stay curious when the first explanation for a failure turns out to be wrong.

Persist through difficult debugging cycles and learn systematically from failed tests.

Take ownership of details, follow through on commitments, and care about reliable outcomes.

Can move between software, sensors, mechanisms, and control loops without losing attention to detail.

Communicate clearly, ask good questions, and document what you learn.

Are comfortable being early in your career while taking real ownership of meaningful work.

Want to help build robots that operate in factories, not just videos.