Mission: Help ship real robot software and OORB Studio ROS2/simulation/deployment workflows—through hands-on bring‑up, simulation, and field testing.

Responsibilities:

• Contribute to OORB Studio ROS workflows (templates, bring‑up scaffolding, deployment tooling)
• Build and debug a clean ROS2 Jazzy stack (packages, launch files, lifecycle nodes, tf frames)
• Work with DDS/QoS basics and build simulation workflows (URDF/xacro, ros2_control, Gazebo/MuJoCo)
• Integrate embedded interfaces using micro‑ROS on MCUs (e.g., STM32) and connect them into ROS2
• Implement or improve navigation behaviors with Nav2 and common packages (tf2, robot_localization, SLAM Toolbox, rosbag2)

Example projects (assigned based on priorities/profile):

• RALLP: ROS2 Stack + Nav2 + simulation + Electrical + Deployment for an all‑terrain platform
• RoboDog: ROS2 Stack + Nav2 + simulation + Electrical + Deployment for a quadruped legged robot

What you’ll bring:

• Solid fundamentals in ROS2, C/C++ and Python; ability to read docs, debug, and ship weekly
• Comfort on Linux (terminal, logs, networking basics); willingness to touch embedded concepts (STM32, protocols)
• Familiarity with ROS2 Jazzy, Nav2, micro‑ROS, DDS, URDF/xacro, ros2_control, Gazebo/MuJoCo, Raspberry Pi–class compute, STM32‑class MCUs
• Nice to have: Practical ROS2 debugging (tf, rosbag2, QoS, launch/lifecycle) and embedded familiarity (STM32 toolchain/RTOS) or Rust

Logistics:

• Duration: 4–6 months (PFE / Final Year or regular internship)
• Location: Flexible — in‑person, hybrid, or remote (HQ: Zaouiet Sousse, Tunisia)

How to apply:

• Apply ONLY through the application form referenced in the PDF (deadline: 25 January 2026). Applications by email are not accepted per the document.