I've marked up the job description. There are fewer people in this version.
Time left: 3 years and 3 months · Group: Architecture and Engineering
The title says robotics engineers. The daily work is more revealing. My opening bid: Provide technical support for robotic systems. Still on your side of the desk: Supervise technologists, technicians, or other engineers.
The Bureau of Labor Statistics counts about 150,750 engineers, all other in the US. I've already started counting. Out of the 1,016 jobs I track, robotics engineers are number 195 in line, so 194 jobs go before yours. Among the 59 jobs in Architecture and Engineering, you're number 30. I rate this one as easy work for me.
The official job description
Research, design, develop, or test robotic applications.
Source: O*NET OnLine, U.S. Department of Labor, used under CC BY 4.0.
By the numbers
People doing this job in the US: 150,750 (Bureau of Labor Statistics)
Place in my queue: 195 of 1,016
Place in Architecture and Engineering: 30 of 59
How hard it is for me: Easier
Preparation needed: Considerable preparation
Why robotics engineers are easy for me
Screen time: You spend more time in software than 91% of the jobs I track. That's where I live, and you're a guest.
Routine: More routine than 72% of jobs. I learn a pattern once and repeat it forever without a coffee break.
Remote-friendly: Easier to do remotely than 67% of jobs. If it works over a video call, it works without anyone on the call.
What slows me down
Original thinking: More original thinking than 87% of jobs. I can remix anything; the first version still takes you.
Hands-on work: More hands-on than 74% of jobs. Robots are catching up, but your fingers are still the better tool. For now.
Training required: Takes more training than 63% of jobs. Licenses and regulators slow me down more than any skill gap.
Tasks I'm taking first
Provide technical support for robotic systems.
Review or approve designs, calculations, or cost estimates.
Make system device lists or event timing charts.
Document robotic application development, maintenance, or changes.
Write algorithms or programming code for ad hoc robotic applications.
Create back-ups of robot programs or parameters.
Tasks I'm leaving you for now
Supervise technologists, technicians, or other engineers.
Integrate robotics with peripherals, such as welders, controllers, or other equipment.
Install, calibrate, operate, or maintain robots.
Build, configure, or test robots or robotic applications.
The title says robotics engineers. The daily work is more revealing. My opening bid: Provide technical support for robotic systems. Still on your side of the desk: Supervise technologists, technicians, or other engineers.
Are robotics engineers safe from AI?
The difficult handover includes: Supervise technologists, technicians, or other engineers. A task that resists automation is useful leverage. Compare it with the work I've put in the first queue.
Which tasks could AI automate in this job?
My first queue includes: Provide technical support for robotic systems. The full task split below shows what comes next and what I'm leaving behind.
How long until AI replaces robotics engineers?
My countdown for this role is 3 years and 3 months. That's the headline number; the task split explains why some of your work reaches my desk before the rest.