> Markdown version of [/jobs/ext/4654734-lead-robotics-software-engineer](https://www.wearedevelopers.com/jobs/ext/4654734-lead-robotics-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Lead Robotics Software Engineer - **Company:** Marentis - **Location:** Berlin, Germany - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Application Integration Architecture, Automated Storage and Retrieval Systems, C++ (Programming Language), Python (Programming Language), Kinematics, Language Modeling, Motion Planning, Software Deployment, Software Engineering, Robot Operating System, Machine Learning Operations - **Published:** November 10, 2026 - **Apply:** https://www.adzuna.de/details/5959491735 ## About the Role * Deploying software on industrial robot cells and working with a manufacturer specific controller environment. * Robot kinematics, coordinate frames, calibration, motion planning and sensor integration. * Strong software engineering, preferably Python and C++, with versioned APIs, testing and release practices. * Simulation and physical validation, including failure analysis and timing measurements. * Technical leadership across research, product and partner teams. Useful additional experience includes force controlled assembly, ROS 2, URDF, applied language models, retrieval systems, model deployment on industrial computers and commissioning in manufacturing environments. A doctorate should not substitute for demonstrated integration work, and need not be mandatory. ## Description CTO, with product and commercial priorities agreed with the product owner and CEO Mission Deliver a reproducible workflow from industrial evidence and task descriptions to validated robot program proposals, then coordinate the integration needed for controlled real robot trials and later productisation. The role should own integration architecture, interface contracts, technical dependencies, demonstration quality, benchmark design and the transfer of research outputs into maintainable Marentis software. It needs enough practical robotics depth to challenge unrealistic controller, sensing and simulation assumptions.