(Senior) Software Engineer, Robot control (f/m/d)

Job description

About TACTILIA: At TACTILIA, we are building the industry-ready robotic hand that closes one of the biggest gaps in Physical AI. Spun out of SCHUNK, the global market leader in gripping technology, we combine a decade of robotic-hand expertise and real industrial access with the speed and ambition of a deep-tech startup. This isn't a research project waiting for its first customer. We already have a product, customers are ready to use it, and we are launching now. Your work will directly shape the electronics, actuators, and embedded systems that make that possible. You will join at the moment when the hard engineering questions become real product decisions: how do we make a highly capable robotic hand reliable, manufacturable, serviceable, and simple enough to deploy on a real shop floor? The Role: As a (Senior) Software Engineer, Robot Control at TACTILIA Robotics, you will help design and build the software that turns our robotic hardware into a reliable, scalable product. You will work across embedded, control, and application software, taking ownership of complex technical problems and helping shape the architecture as the platform evolves. You will work closely with the CTO and engineering team, with the autonomy to make important technical decisions and see them through to working systems. This is a hands-on role. You will move between architecture, implementation, and the lab, solving the challenges that arise when software meets real hardware What you will do: Set the architecture. Embedded, control, and application layers — modular and reusable across product variants, not a one-off for a single prototype. Write the control loops that can't miss a beat. Deterministic firmware on the embedded target: hardware abstraction, sensor/actuator integration, fault handling, hard real-time constraints. No room for "usually works." Turn commands into grasps. Position, torque, force impedance and admittance control, coordinated multi-finger motion, and handle all different states to make the grasp stable and reliable Build the simulation before hardware pays the price Simulation models for control development, regression testing, and sim-to-real validation — most iteration should happen before anyone touches a real hand. Ship SDKs people actually want to integrate. ROS 2, fieldbuses, and customer-facing interfaces — documented and version-stable, not tribal…