Team Lead Robotics Software (AMR)
Portugal, PT
Specialist (5+ Years)
Full remote
English Required
Not Accepting Candidates Living Abroad
1. Role Summary (Executive Overview)
We are looking for a hands-on Tech Lead / Team Lead for our Robotics Software Stack Team, responsible for the software “brain” of our Autonomous Mobile Robots (AMRs).
This role combines:
• Deep robotics engineering (ROS, SLAM, navigation)
• System architecture (ROS1/ROS2, distributed systems)
• Technical leadership and delivery ownership
• Discuss and shape the product together with three other team leaders
• Direct report to Director R&D
Important:
This is not a traditional management role, but rather a Principal Engineer with leadership responsibility.
2. What We Really Need (Core Candidate DNA)
The ideal candidate brings four key dimensions:
1. Strong Robotics Engineer first
• Hands-on experience in navigation, SLAM, or localization
• Ideally also exposure to perception (object detection, sensor processing, environment understanding)
• Has built production-grade systems, not just prototypes
• Understands real-world problems such as:
Candidates who only “use ROS” without deep system understanding
2. System Architect
• Thinks in systems, not just features
• Strong understanding of:
Make architectural decisions
• Clearly explain trade-offs (performance vs. robustness vs. maintainability)
3. Technical Leader
• Leads a team of currently five heads through technical authority, not hierarchy
• Can:
Not a pure people manager – must be a respected engineer within the team
4. Hands-on Mindset
• Actively writes code (Python + C++)
• Debugs real system-level issues
Strong expectation:
• ~60–70% hands-on work
No go:
Candidates who want to move away from engineering into coordination only
3. Must-Have Skills (Non-Negotiable)
Robotics / Core Tech
• Strong experience with ROS1 and ROS2
• Navigation stack (Nav2 / move_base)
• SLAM / Localization (e.g. LOAM, AMCL, LIO-SAM)
• Sensor fusion (LiDAR + IMU at minimum)
Programming
• Python (primary language)
• C++ (mandatory)
• Rust (ideal)
Systems
• Linux (Ubuntu, debugging)
• Git workflows + CI/CD
4. Nice-to-Have (Strong Differentiators)
• Experience with industrial AMRs
• Knowledge of VDA 5050 and Fleet Manager integration
• Multi-robot systems / fleet management
• Safety / risk prevention knowledge (e.g. ISO 3691-4)
• Simulation (Gazebo / Ignition)
• Docker / container-based robotics architectures
• Rust (nice bonus, not mandatory)
5. What the Candidate Will Actually Do
• Own and evolve the robotics software architecture (navigation, localization, safety)
• Debug complex system issues (hands-on, not delegated)
• Drive R&D topics (e.g. map handling, odometry, multi-floor navigation)
• Lead and mentor the robotics team technically
• Work closely with real customer deployments (industrial environments)
6. Candidate Background (Typical Sources)
Strong sources:
• AMR / AGV companies (e.g. KUKA, ABB, MiR, Fetch, Locus Robotics)
• Robotics startups
• Autonomous driving (if navigation/system focus is strong)
Critical:
• Pure academia without product experience
• Perception-only profiles (often lacking navigation/system depth)
7. Dealbreakers (Critical for Screening)
• No real ROS system expertise
• No C++ experience
• No hands-on experience with navigation or real robots
• Not willing to stay hands-on
• Pure management profile
8. Key Selling Points (Why This Role is Attractive)
Important for attracting strong candidates:
High technical impact
• Software directly controls robots in production environments
End-to-end ownership
• Architecture → implementation → deployment → real-world behavior
High complexity
• SLAM, navigation, multi-robot coordination, real-world constraints
Freedom to shape architecture
• The role has a strong influence on technical direction
Hybrid role
• Deep tech + leadership combined
9. Candidate Outreach Pitch
We are looking for a hands-on Tech Lead who can build and shape the software brain of autonomous mobile robots.
This role combines deep robotics engineering (ROS, SLAM, navigation) with system architecture and technical leadership.
You will design and build systems that operate in real industrial environments — not just simulations.
10. Internal Context (Not for Public Job Ad)
Important to know:
• The current system has evolved over time → needs clearer architecture
• We run real customer deployments (not purely R&D)
• We need someone who structures problems, not just executes tasks
• Customer interaction is part of the role (not a pure backend position)
We are looking for a hands-on Tech Lead / Team Lead for our Robotics Software Stack Team, responsible for the software “brain” of our Autonomous Mobile Robots (AMRs).
This role combines:
• Deep robotics engineering (ROS, SLAM, navigation)
• System architecture (ROS1/ROS2, distributed systems)
• Technical leadership and delivery ownership
• Discuss and shape the product together with three other team leaders
• Direct report to Director R&D
Important:
This is not a traditional management role, but rather a Principal Engineer with leadership responsibility.
2. What We Really Need (Core Candidate DNA)
The ideal candidate brings four key dimensions:
1. Strong Robotics Engineer first
• Hands-on experience in navigation, SLAM, or localization
• Ideally also exposure to perception (object detection, sensor processing, environment understanding)
• Has built production-grade systems, not just prototypes
• Understands real-world problems such as:
- Localization drift
- Sensor noise and inconsistencies
- Edge cases in navigation and safety
Candidates who only “use ROS” without deep system understanding
2. System Architect
• Thinks in systems, not just features
• Strong understanding of:
- Distributed robotic systems
- ROS1 ↔ ROS2 migration and bridging
- Containerized robotics stacks (Docker)
Make architectural decisions
• Clearly explain trade-offs (performance vs. robustness vs. maintainability)
3. Technical Leader
• Leads a team of currently five heads through technical authority, not hierarchy
• Can:
- Facilitate design discussions
- Align engineers on architecture
- Structure and break down complex problems
Not a pure people manager – must be a respected engineer within the team
4. Hands-on Mindset
• Actively writes code (Python + C++)
• Debugs real system-level issues
Strong expectation:
• ~60–70% hands-on work
No go:
Candidates who want to move away from engineering into coordination only
3. Must-Have Skills (Non-Negotiable)
Robotics / Core Tech
• Strong experience with ROS1 and ROS2
• Navigation stack (Nav2 / move_base)
• SLAM / Localization (e.g. LOAM, AMCL, LIO-SAM)
• Sensor fusion (LiDAR + IMU at minimum)
Programming
• Python (primary language)
• C++ (mandatory)
• Rust (ideal)
Systems
• Linux (Ubuntu, debugging)
• Git workflows + CI/CD
4. Nice-to-Have (Strong Differentiators)
• Experience with industrial AMRs
• Knowledge of VDA 5050 and Fleet Manager integration
• Multi-robot systems / fleet management
• Safety / risk prevention knowledge (e.g. ISO 3691-4)
• Simulation (Gazebo / Ignition)
• Docker / container-based robotics architectures
• Rust (nice bonus, not mandatory)
5. What the Candidate Will Actually Do
• Own and evolve the robotics software architecture (navigation, localization, safety)
• Debug complex system issues (hands-on, not delegated)
• Drive R&D topics (e.g. map handling, odometry, multi-floor navigation)
• Lead and mentor the robotics team technically
• Work closely with real customer deployments (industrial environments)
6. Candidate Background (Typical Sources)
Strong sources:
• AMR / AGV companies (e.g. KUKA, ABB, MiR, Fetch, Locus Robotics)
• Robotics startups
• Autonomous driving (if navigation/system focus is strong)
Critical:
• Pure academia without product experience
• Perception-only profiles (often lacking navigation/system depth)
7. Dealbreakers (Critical for Screening)
• No real ROS system expertise
• No C++ experience
• No hands-on experience with navigation or real robots
• Not willing to stay hands-on
• Pure management profile
8. Key Selling Points (Why This Role is Attractive)
Important for attracting strong candidates:
High technical impact
• Software directly controls robots in production environments
End-to-end ownership
• Architecture → implementation → deployment → real-world behavior
High complexity
• SLAM, navigation, multi-robot coordination, real-world constraints
Freedom to shape architecture
• The role has a strong influence on technical direction
Hybrid role
• Deep tech + leadership combined
9. Candidate Outreach Pitch
We are looking for a hands-on Tech Lead who can build and shape the software brain of autonomous mobile robots.
This role combines deep robotics engineering (ROS, SLAM, navigation) with system architecture and technical leadership.
You will design and build systems that operate in real industrial environments — not just simulations.
10. Internal Context (Not for Public Job Ad)
Important to know:
• The current system has evolved over time → needs clearer architecture
• We run real customer deployments (not purely R&D)
• We need someone who structures problems, not just executes tasks
• Customer interaction is part of the role (not a pure backend position)
We connect IT professionals with projects that match their skills, professional experience, and goals, then we offer a career progression program, delivered by in-house specialists - our People Experience Partners - to guide them through our journey with us.
What we offer:
What we offer:
- A project that matches your skills and ambitions, as well as your preferences for working policies and culture.
- A competitive salary with awesome benefits and opportunities to leverage your knowledge and network to earn additional income.
- An empowering and respectful work culture enriched with social and learning events.
- A People Experience Partner specially assigned to you - your go-to career guide, responsible for supporting your growth, facilitating training, and ensuring your work-life balance at KWAN.
At KWAN, they make sure that I feel comfortable with the client I’m working for and that what I’m doing aligns with my career aspirations.
Luis Caldeira, DevOps @ KWAN
At KWAN, I’m given the space to be myself and do what I love. I have control over the projects I work on, as well as the direction of my career.
Pedro Fonseca, Front End Developer @ KWAN
I see my People Experience Partner as someone who is always available to provide me with motivation and constant feedback, which helps me be sure that I am in the right place.
Josimar dos Reis, Software Developer @ KWAN
I know that I’ve contributed to the growth of a company that truly values a “people first culture”, because my ideas, experiences, and individuality were always appreciated.
João Nascimento, Software Developer (KWAN Alumni)
My two years at KWAN were an incredible experience! From the start, I was welcomed into a warm and collaborative environment where I felt truly supported.
Laís Ortiz, Software Developer @ (KWAN Alumni)
Grab this opportunity, apply now!
What You Can Expect as a KWANer
Respect isn’t optional here
Dedicated People Experience Partner
Someone accountable for your growth, not your allocation.
Continuous learning, built in
Recognition that’s visible
A culture you can feel
Flexible spaces to work your way
Didn't find your mission yet?
Strong profiles don’t always match timing. That doesn’t mean there isn’t alignment.
We review every application. If there’s alignment, we won’t let it get lost in a database.