Robotics Software Architect

Applicants should have unrestricted right to work in the Netherlands. We will not sponsor visa. The role and first six months: We have working hardware: a large robotic ground system with heavy moving assemblies. This is a hands-on software architecture and integration role, not a hardware concept waiting to be built. For the first six months, your core responsibility is to understand the existing system. Strengthen the interfaces and integration of electromechanical subsystems, multiple embedded controllers and PLCs. In parallel, you will develop, implement and test a modular software architecture with well-defined interfaces and appropriate open standards on the working hardware. The task is to build on what works, identify gaps and validate improvements through controlled changes. Why this role, or the company exists: Because the last layer of air defense (non-missile) does not exist! We are building counter systems to protect people, high value assets and critical assets. This role builds a scalable software architecture, reliability and interoperability of the system. The software must support edge autonomy for deploying, recovering and managing UAV fleets, including coordinated multi-vehicle operations. Your focus is the ground system (System-of-Systems) and fleet-level integration. We are in the business of intercepting adversarial armed effects. So “Impact” has a very real, very loud meaning at Scura. What you will own: Electromechanical integration: Map, document and validate existing interfaces between PLCs, embedded controllers, drives, actuators, sensors and supervisory software. Improve integration, commission additions and change, and resolve faults that cross subsystem boundaries.Machine behaviour: Develop and verify robust coordination and sequencing algorithms for complex machine operations. Make readiness, error handling, recovery and operator intervention explicit and testable.Modular software architecture: Assess the existing implementation and develop cohesive, loosely coupled software modules with clear responsibilities and documented interfaces. Select suitable, widely supported, consensus-based open standards and verify conformance. Make components independently testable and replaceable, while managing the constraints of the existing hardware.Edge autonomy: Architect and test local software supporting fleet deployment, recovery and management. Define the responsibilities and interfaces between the ground platform, operator tools and aircraft-side systems.Interoperability and supplier independence: Maintain versioned interface contracts and compatibility tests so components from different suppliers can be integrated, upgraded or replaced with limited impact elsewhere. Identify interface-documentation, licensing and technical-data access requirements that could otherwise create supplier lock-in.Safety and verification: Work with mechanical, electrical, controls and safety specialists on safe machine behaviour. Build simulation, hardware-in-the-loop and regression tests, while keeping machinery safety functions distinct from higher-level autonomy.Knowledge gaps and team growth: Identify and flag knowledge gaps, help define additional roles. Assist in on-boarding new team members through system walkthrough, clear interface documentation and practical mentoring. Initial success means better-understood interfaces, repeatable integration of priority subsystems, and an architecture supported by working code and tests. You will also make the remaining technical risks and specialist-support needs visible. What you bring: Delivered machinery: You have personally taken a substantial robotic or industrial machine through software integration and commissioning. You can explain your contribution, the failures you encountered and how you verified the result.Hands-on controls: PLC programming, controller integration, industrial communications and motion-control experience. You can read electrical schematics and troubleshoot on physical equipment; expertise in every vendor's platform is not expected.Modular software architecture: Proven ownership of reusable machine-control libraries, component-based software or comparable architectures with well-defined interfaces. You can show how modules were tested, extended or replaced without redesigning the whole system.Application software: Strong production C++ experience, practical Linux knowledge and the ability to use Python for testing, diagnostics or tooling. You understand concurrency, timing constraints and communication between software and controllers.Engineering judgement: Disciplined testing, hazard-aware commissioning and clear communication. You recognise when a test should stop and when specialist controls, safety or autonomy expertise is needed. Your strongest background may be industrial automation, machine building, robotics, material handling, precision equipment or vehicle systems. What matters is your ability to connect software architecture with a physical machine that works reliably, not a particular degree or job title. Useful, but not required: Familiarity with the Modular Open Systems Approach (MOSA) is preferred, not required. UAV ground-system or fleet-software experience is useful. What we offer: 1 year fixed term contract, followed by permanent contract.Long-term upside: Generous Stock Appreciation Rights. You grow with the company.Responsibility and ownership: Direct collaboration with stakeholders and meaningful authority over engineering, test quality and safety. You own the stack.Growth: Founding architect is a long-term commitment, you are expected to grow. You will shape the engineering culture as well as the product. If you are interested because of a defense-tech boom/trend, this is certainly not for you. Join for the right reason.