Robotics Software Engineer

About the role

ALTEN Technology builds software for aerospace, medical devices, automotive, and similar sectors. This role focuses on building and maintaining software for robots that navigate and manipulate objects. You will collaborate with senior engineers and roboticists on real robotic prototypes.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

Software components for navigation, manipulation, perception, controls, and system integration are designed, developed, tested, and maintained across the robotics platform.

Robotics applications are developed and deployed using ROS 2 with C++ and Python for real robotic systems.

Sensors, actuators, compute platforms, and control frameworks are integrated through software to enable system functionality.

Requirements

A Bachelor's or Master's degree in Computer Science, Robotics, Electrical Engineering, Mechanical Engineering, or a related technical discipline, or equivalent practical experience is required.

Professional experience developing software for robotics or autonomous systems is required.

Strong hands-on experience with ROS 2, modern C++ and/or Python, and Linux-based development environments is required.

Complex software systems must be integrated and debugged effectively.

Understanding of robotics software fundamentals, including communication frameworks, system architecture, and hardware/software integration, is required.

Problem-solving skills must be strong, and effectiveness in a collaborative engineering environment is required.

Nice to have

Experience in robotic perception, motion planning, controls systems, machine learning for robotics, and autonomous navigation is valued.

Experience with hardware bring-up, sensor integration, and low-level system debugging is valued.

Hands-on experience deploying and troubleshooting software on physical robotic systems, not only simulation environments, is valued.

Familiarity with robotic manipulators, mobile robots, autonomous vehicles, or industrial robotics platforms is valued.

Experience working with real-time or embedded systems is valued.

Practical notes

Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Robotics software roles involve real-time systems and close collaboration with hardware teams. Common tools in this field include ROS 2, C++, Python, and Linux-based embedded environments. Professionals often validate software through simulation and physical robot testing. This role contributes to core capabilities in autonomous navigation and manipulation. The work applies to sectors such as aerospace, medical devices, and autonomous vehicles.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.