Robotics software engineer (nuclear)Salary, qualifications, career path and hiring demand, 2026 edition
A nuclear robotics software engineer builds the control, perception, autonomy and operator-interface software that lets advanced robotic systems work where human workers should not. Typical applications include radioactive waste sorting, hot-cell manipulation, inspection, radiation mapping, decommissioning, remote maintenance and fuel-cycle work. The role combines C++/Python, robot operating system (ROS/ROS2), motion planning, sensor fusion, simulation and real-time integration with a strong understanding of physical robot behaviour and engineering principles. Nuclear adds harder failure consequences, restricted access and a premium on predictable recovery when software, communications or sensors fail, requiring collaboration closely with hardware engineers and autonomy and simulation teams.
Nuclear robotics software is not separately coded in official salary statistics. TRX models US established specialists around $122,000–$158,000, with senior/principal work at $148,000–$188,000. UK established specialists generally model around £55,000–£72,000, rising to £65,000–£85,000 senior and higher where the engineer owns architecture, autonomy or complex field deployment.
No professional licence is required. Employers screen for production C++/Python, ROS/ROS2, Linux, controls, perception, simulation, software quality and evidence that code has run on real robots rather than only in simulation. Nuclear work adds radiological constraints, fail-safe behaviour, remote recovery, communications limits, cyber/security controls, mock-up testing and the ability to commission systems safely in environments where physical access may be expensive or hazardous.
The role at a glance
everything an employer will ask about in the first fifteen minutes of a screening call.
.webp)
- Also called
- robotics software developer · autonomous systems engineer · robot controls software engineer · ROS engineer · remote handling software engineer · robotics R&D engineer
- Entry qualification
- BSc/BEng/MEng in robotics, computer science, software, electrical/electronic, mechatronics or control engineering; practical robotics projects can materially strengthen non-robotics degree routes.
- Typical entry pay
- $100,000–$128,000 US · £45,000–£58,000 UK.
- Senior pay
- $148,000–$188,000 US · £65,000–£85,000 UK, with technical leads modelled to approximately $220,000 or £105,000.
- Contract day rates
- approximately £450–£600/day UK established specialist and £600–£800/day for autonomy, teleoperation, perception or architecture; US equivalents approximately $70–$125/hr.
- Professional gate
- no statutory licence; shipped robot software, field commissioning, failure recovery, software quality and employer technical-authority arrangements are the practical gates.
- Security
- UK BPSS common and SC/higher on sensitive nuclear/defence work; US DOE/national-laboratory programmes can add citizenship, export-control and clearance requirements.
- Where the work sits
- nuclear decommissioning, remote handling, national laboratories, fusion programmes, advanced reactors, waste retrieval, inspection robotics and specialist technology suppliers.
- Travel
- moderate; software development is office/lab based, but integration, mock-up trials and nuclear-site commissioning require field work.
- Shift pattern
- mainly office/day work; site trials, outage windows and deployment failures can create early, late or weekend support.
- TRX segments
- Decommissioning & dismantling · Fusion · Operating fleet · New technology development · Waste management · Digital engineering
Six versions of the same job title
nuclear robotics software changes with how much authority the robot has and what task it performs. The core role is always to make a physical machine behave predictably in a hazardous environment.
Teleoperation and remote handling
Develops software that maps operator commands into safe, intuitive robot motion for manipulators, robot arms and remote tooling. Haptic feedback, latency, joint limits, collision avoidance and graceful recovery dominate this version.
Autonomous inspection and navigation
Builds localisation, mapping, path planning and autonomy for ground, aerial, underwater or legged robots inspecting nuclear facilities. The software must handle poor lighting, clutter, communications loss and uncertain maps.
Perception and sensor fusion
Integrates cameras, LiDAR, radiation detectors, force/torque sensors, IMUs and other instrumentation to estimate robot and environment state. Nuclear applications often combine geometry with radiological measurements to support remote characterisation.
Manipulator motion planning and control
Develops inverse kinematics, trajectory generation, collision-aware planning and low-level control for arms performing cutting, sorting, dismantling or handling. The strongest work bridges mathematical control and practical tooling constraints.
Robotics simulation and digital mock-up
Builds Gazebo, Isaac Sim, Unity/Unreal, MATLAB/Simulink or bespoke environments to test robot behaviour before hardware deployment. Simulation supports collision checking, operator rehearsal, algorithm development and decommissioning sequence planning.
Robotics platform / middleware engineering
Owns ROS2 architecture, drivers, message interfaces, lifecycle management, telemetry, logging and reusable software components across multiple robot types. This is the platform-heavy route that enables teams to deploy common tooling faster.
What the week actually looks like
a composite day for an established robotics software engineer supporting a teleoperated robotic arm being prepared for active radioactive-waste sorting trials.
What nuclear robotics software engineers are paid in 2026
Nuclear robotics software engineering is not separately coded in official wage statistics. The ladders below are a TRX market model anchored to BLS Software Developers, live 2026 robotics software salary data and the specialist premium for hazardous-environment deployment. Pay rises most sharply with architecture, autonomy and successful field commissioning.
How nuclear robotics software compares to adjacent roles
General robotics salaries provide a market anchor, while nuclear specialist bands are a TRX model reflecting hazardous deployment, security, remote-operation and field-integration responsibilities.
| Occupation | Median | P10 | P90 | What moves the number |
|---|---|---|---|---|
| Robotics software engineer (nuclear, TRX model) | $164,000 senior midpoint | $100,000 | $198,000+ | Field deployment, autonomy, ROS2, hazardous-environment integration |
| Software developers, all industries (BLS May 2025) | $135,980 | $82,460 | $214,670 | Industry, architecture, technical depth and geography |
| Robotics software engineer, US market Sep 2026 | about $124,000–$127,000 | about $106,000 | about $147,000+ | Robotics stack, location, experience and employer |
| UK robotics software engineer market | £55,000–£75,000 live range | — | — | C++/ROS2 depth, real robots and autonomy responsibilities |
General robotics salaries provide a market anchor, while nuclear specialist bands are a TRX model reflecting hazardous deployment, security, remote-operation and field-integration responsibilities.
Teleoperation / haptics in hazardous environments
Proven remote manipulation with force feedback, latency management and operator validation is scarce and directly relevant to decommissioning.
Autonomy with real field deployment
Engineers who have moved localisation, planning or perception from lab tests onto robots in uncontrolled facilities command a premium over simulation-only experience.
ROS2 platform architecture
Engineers who can design reusable lifecycle, communications, diagnostics and logging architecture across a robot fleet are valued above feature-only developers.
Three ways in
The strongest candidates usually arrive from robotics, embedded/software engineering or control systems. Nuclear conversion comes through hazardous-environment deployment, remote handling and the extra assurance required when humans cannot easily intervene.
Robotics / computer science route
Controls / mechatronics route
Software engineer transfer
Are you actually ready to compete for a nuclear robotics software engineer role?
“ROS2 and C++” are not enough. Recruiters want the robot, sensors, control architecture, autonomy level, simulation stack, failure modes and field deployment you personally owned. Strong CVs show how software behaved when communication dropped, sensors degraded or the robot encountered geometry the test environment did not predict.
Free resume scoring on avua. Your score is yours; it is not shared with employers.The common gap is deployment evidence: candidates show algorithms and simulations but not integration, failure recovery, operator use or hazardous-site constraints.
Illustrative TRX shortlisting pattern only.
The credentials that actually gate the work
the role is competence-gated by real-robot software, field integration and the safety/security controls that apply to nuclear deployment.
| Credential | Jurisdiction | Required for | Time | Notes |
|---|---|---|---|---|
| Robotics / software / engineering degree | All | Typical professional entry | 3–4 yrs | Computer science, mechatronics, controls and electrical engineering all transfer. |
| C++ / Python production competence | All | Core software development | Role-specific | Strong coding, debugging and testing matter more than language certificates. |
| ROS / ROS2 competence | All | Most modern robotics programmes | Role-specific | Nodes, topics, services, actions, TF, lifecycle, DDS and diagnostics are common expectations. |
| Functional / machinery safety awareness | All | Physical robot deployment | Role-specific | Risk assessment, emergency stop, safe states and controlled motion are essential even where no single standard dominates. |
| Nuclear site / radiation worker training | Nuclear sites | Field commissioning | Days–weeks | Requirements depend on contamination, dose and facility. |
| BPSS / SC or higher | UK | Sensitive nuclear/defence work | Weeks–months | RAICo/NDA programmes may require controlled access depending on task. |
| DOE / export-control / site access | US | National-lab and cleanup missions | Weeks–months | Requirement depends on facility and robot deployment. |
Robotics software is judged on the physical system it controls. Nuclear employers therefore value engineers who understand mechanical limits, safe states and field recovery as much as software architecture.
What appears on a 2026 nuclear robotics software engineer shortlist
the shortlist tests whether the engineer can make a physical robot behave reliably outside a lab, under communication, sensing and access constraints that are common in nuclear facilities.
Named on the specification
- Modern C++ and Python — production code, debugging, concurrency, memory/resource awareness, interfaces, packaging and testing.
- ROS/ROS2 and Linux — nodes, topics, services, actions, TF frames, launch/lifecycle management, DDS/QoS, device integration and system diagnostics.
- Robot kinematics and controls — coordinate transforms, inverse/forward kinematics, trajectory generation, PID/model-based control and joint/actuator constraints.
- Motion planning / autonomy — collision checking, path planning, localisation, state machines/behaviour trees and graceful fallback when autonomy cannot continue.
- Sensors and perception integration — cameras, LiDAR, force/torque, IMUs, radiation sensors, calibration, filtering and data synchronisation.
- Simulation, testing and field debugging — Gazebo, Isaac Sim, MATLAB/Simulink or equivalent plus hardware-in-the-loop, logs, regression tests and disciplined deployment.
What decides between two shortlisted candidates
- Haptic teleoperation — force-feedback devices, bilateral control, latency compensation and intuitive operator interfaces.
- Radiation / contamination-aware robotics — understanding shielding, electronics tolerance, contamination control, recoverability and remote maintenance.
- Underwater / aerial / quadruped platforms — experience beyond conventional wheeled robots for ponds, elevated inspections or difficult terrain.
- Computer vision / AI for manipulation — object detection, pose estimation, segmentation or learned control used with conservative fallbacks.
- Digital twins / operator interfaces — virtual robot visualisation, predictive motion preview, task overlays and live operational data.
- Real nuclear site commissioning — deployed software under permits, access constraints and operator acceptance rather than research-only demonstrations.
The 2026 demand map
demand is being driven by decommissioning missions that must remove people from hazardous environments and fusion programmes that will require routine remote maintenance. The 2026 market is especially active in the UK, with significant US cleanup applications.
| Programme | Location | Phase in 2026 | Engineering demand |
|---|---|---|---|
| RAICo robotics programme | Whitehaven / UK | 2026–27 programme active across robot control, tooling, AI data and digital infrastructure | Very high for controls software, ROS, teleoperation, simulation and deployment |
| NRS Oldbury FED robotic sorting | Gloucestershire, UK | Inactive on-site demo completed March 2026; active-trial preparation underway | Direct demand for haptic control, robot-arm software and operator interfaces |
| Auto-SAS radioactive waste sorting | Oldbury, UK | Robotics trials active; commissioning/testing planned around mid-2027 | High for autonomy, perception, manipulation and risk-controlled deployment |
| Sellafield remote operations / RAICo1 | Cumbria, UK | Active high-hazard reduction and robotics deployment ecosystem | Very high for remote handling, inspection, digital interfaces and field robotics |
| UKAEA fusion / remote maintenance | Culham / Rotherham / STEP ecosystem, UK | 2026–2030 strategy accelerates robotics deployment across nuclear and fusion | High for remote maintenance, robotics software and reusable control platforms |
| Idaho Cleanup Project calcine retrieval robot | Idaho, US | Robotic retrieval system development active in 2026 | High for remote manipulation, integration and hazardous waste retrieval |
| Oak Ridge hot-cell cleanup robotics | Tennessee, US | Robotic demolition/removal equipment actively supporting contaminated-facility cleanup | High for remote systems, tooling and field integration |
| DOE Environmental Management sites | US cleanup complex | Long-duration decommissioning and waste missions | Sustained demand for robotic inspection, retrieval and worker-exposure reduction |
| ORNL Remote Systems Group | Tennessee, US | Ongoing hazardous-environment robotics and remote handling R&D | Specialist demand for controls, HMI, simulation and field-deployable remote systems |
Programme phases move, and rewinds are planned years ahead. Confirm current status before making a relocation decision; TRX tracks these weekly.
RAICo’s current programme is explicitly focused on moving robotics onto real decommissioning sites, not stopping at research demonstrations.
Oldbury’s 2026 work combines haptic teleoperation, bespoke robot-control software and a digital interface showing camera, sensor and virtual robot data. DOE cleanup programmes likewise continue using robotic systems where contaminated equipment must be manipulated without putting workers directly into the hazard.
Robotics research graduates often know planning and perception, while nuclear engineers understand site hazards and work control.
The difficult hire can write high-quality C++, debug timing and networks, tune a physical robot, understand operator needs and still design a recovery path for deployment in a radioactive environment. That combination is why field-tested nuclear robotics software engineers remain scarce.
Adjacent and onward roles
nuclear robotics software sits between controls, autonomy, remote handling and digital systems, so progression can deepen technically or broaden into whole-system leadership.
Questions we get asked every week
How much does a nuclear robotics software engineer earn in 2026?
There is no exact official nuclear salary series. TRX models US entry pay around $100,000–$128,000 annually mid level, established specialists at $122,000–$158,000 annually senior level and senior/principal work at $148,000–$188,000. The broader BLS software developer median is $135,980, while September 2026 US robotics software engineer salary estimates are around $124,000–$127,000. UK pay models around £45,000–£58,000 at entry and £65,000–£85,000 senior/principal. These figures reflect demand in the nuclear robotics field and incorporate cost efficiency and production reliability factors.
Which programming languages and frameworks matter most?
Modern C++ and Python are the strongest recurring languages, with ROS2 increasingly the standard robotics frameworks middleware. Linux, Git, CMake, networking, and strong debugging skills are essential. Depending on the role, engineers may also use Gazebo, Isaac Sim, MATLAB/Simulink, OpenCV, MoveIt, CUDA, or machine learning algorithms frameworks. Employers value hands-on experience with real robots over a long tool list. Knowledge of artificial intelligence and machine learning methods is increasingly important.
Do I need nuclear experience to enter robotics software?
Not always. Strong engineers can transfer from autonomous driving evaluation, industrial automation, defence, aerospace, medical robotics, or warehouse automation. Nuclear conversion requires learning radiological hazards, restricted access, remote recovery, equipment contamination, and site work controls. Senior roles usually expect evidence that you understand why failure recovery and system reliability matter differently when a technician cannot simply walk up to the robot.
What is the difference between a robotics software engineer and a remote handling engineer?
The robotics software engineer owns code: controls, autonomy software, perception, middleware, interfaces, and software integration. The remote handling engineer owns the wider system and may be more mechanical or systems focused, covering manipulators, tooling, loads, maintainability, installation, and operator procedures. Mature nuclear robotics teams need both because software behaviour depends strongly on physical tooling and environment, requiring lead cross functional integration.
Where is demand strongest in 2026?
The UK decommissioning market is especially active through RAICo, Sellafield, and NRS sites. RAICo’s 2026–27 programme includes robot control, automation, tooling, and digital infrastructure, while Oldbury is trialling robotic waste sorting with bespoke haptic-control software. In the US, DOE Environmental Management continues applying robotics to Idaho and Oak Ridge cleanup, and ORNL maintains specialist remote-systems capability for hazardous environments. These areas represent top job opportunities in the nuclear robotics field.
What makes a nuclear robotics software engineer stand out at interview?
A deployment failure that you recovered from is stronger evidence than a perfect simulation. Explain what the robot was doing, which software component failed, how you diagnosed the interaction between code, sensors, communications, and mechanics, and how the system was made recoverable. Senior interviewers value engineers who treat autonomy, teleoperation, and failure recovery as one integrated design problem, demonstrating problem solving skills and system performance awareness.
We only recruit in nuclear. That is the whole point.
TRX can assess whether your background fits teleoperation, ROS2 platforms, autonomous inspection, manipulator control, perception, robotics simulation or remote decommissioning systems. The strongest evidence is the robot you deployed, the failure modes you designed around and the hazardous task your software allowed people to perform from a safer distance.