Senior Robotics Engineer Jobs

Senior Robotics Engineer Jobs (Remote, Full-Time) Rex.zone connects experienced robotics engineers with remote, full-time roles building and deploying real-world robotic systems. You will own autonomy features from prototype to reliable field performance across perception, localization/SLAM, motion planning, and control.

About The Role Architect and implement robot autonomy features across perception, planning, and control. Build robust ROS/ROS2 nodes, integrate sensors (cameras, LiDAR, IMU, encoders), and ship reliable behaviors in real environments while collaborating with mechanical, electrical, and product partners.

Key Responsibilities

• Design and maintain ROS/ROS2-based autonomy stacks
• Implement localization, mapping, and SLAM pipelines
• Develop motion planning and trajectory optimization for dynamic environments
• Build perception modules using computer vision and sensor fusion
• Tune control loops and state estimators for stability and performance
• Create simulation environments and test harnesses (Gazebo, Isaac Sim) to reproduce field issues
• Establish logging, telemetry, and debugging workflows for regression analysis
• Write production-quality C++/Python code with CI, code review, and documentation
• Partner on safety, reliability, and fail-safe behaviors for hardware deployment

Required Qualifications

• 5+ years delivering deployed robotic systems
• Strong C++ and Python on Linux
• Hands-on ROS/ROS2 expertise (TF, message design, real-time considerations; Nav2/MoveIt as applicable)
• Experience with SLAM/localization and sensor fusion
• Motion planning and control fundamentals (e.g., A*, RRT*, MPC; PID/LQR)
• Ability to debug hardware/software integration issues using logs and instrumentation

Remote Work These roles are remote and full-time. Some teams may require occasional travel for hardware integration, field testing, or onsite validation depending on the platform.

How To Apply Apply on Rex.zone with a resume highlighting deployed robotics projects, ROS/ROS2 modules you owned, and measurable outcomes (success rate, localization error, uptime, latency, or safety improvements). Include links to code, publications, demos, or technical write-ups where available.