Anyone regret specializing too early before the field's direction was clearer?
Anyone regret specializing too early before the field's direction was clearer?
Trying to organize my own thinking on this, so bear with me.
Transitioning from industrial automation into humanoid-specific roles is a increasingly common and viable path, since a lot of the underlying skills (motion control, safety systems, real-time software) transfer directly, even though the specific dynamics and learned-control components are new. Remote work remains genuinely limited for most hands-on humanoid hardware roles, given the need for physical access to robots and test environments, though software-only roles (simulation, perception algorithms, offline learning) increasingly do offer remote or hybrid arrangements.
Interested in both agreement and pushback here.
they/them
-
diego.moore6
- Posts: 155
- Joined: Thu May 08, 2025 8:48 am
Re: Anyone regret specializing too early before the field's direction was clearer?
Same conclusion I've come to. Also worth noting:
A commonly cited skill gap in new-grad applicants is practical systems integration experience - many candidates are individually strong in ML or in mechanical design, but comparatively few have hands-on experience getting perception, planning, and control to work together reliably on real hardware under time pressure.
Building > buying.
Re: Anyone regret specializing too early before the field's direction was clearer?
@diego.moore6 Minor factual note:
A strong, well-documented personal project (even a modest DIY build or a solid simulation-based RL project) reportedly carries real weight in hiring for this field, partly because the field is young enough that a demonstrated hands-on track record can meaningfully substitute for a less-relevant formal credential.
Watching this space closely since 2019.
-
camila.jackson0
- Posts: 225
- Joined: Wed Oct 09, 2024 1:27 am
Re: Anyone regret specializing too early before the field's direction was clearer?
Yeah, this tracks with what I've read as well.
The common academic path into this field is a master's or conversion course in robotics or machine learning, followed by an internship or research role at a known lab or company - a PhD is common but increasingly not strictly required for industry roles, especially on the applied engineering side.
Building > buying.
-
barbara.jones
- Posts: 164
- Joined: Fri Feb 28, 2025 6:12 pm
Re: Anyone regret specializing too early before the field's direction was clearer?
Small correction on one detail:
Internship competitiveness at the well-known humanoid companies has increased sharply as the field's visibility has grown, with the applicant pool now including not just robotics students but a lot of general CS/ML students drawn in by the sector's high profile.
he/him | robotics hobbyist since the DARPA Grand Challenge days
Re: Anyone regret specializing too early before the field's direction was clearer?
@barbara.jones This lines up with my experience.
How much ML background a controls role actually requires varies a lot by company and team - some whole-body control positions remain heavily classical-optimization-focused, while others increasingly expect familiarity with reinforcement learning or imitation learning even for what used to be a purely classical-controls job. RSS (Robotics: Science and Systems), ICRA, and the IEEE-RAS Humanoids conference are commonly cited as the most directly relevant venues for someone specifically interested in legged locomotion and humanoid control research, as opposed to broader AI/ML conferences.
Reminds me a bit of the early drone hobbyist scene, honestly.
-
jessica_faro
- Posts: 95
- Joined: Sat Oct 11, 2025 5:26 am
Re: Anyone regret specializing too early before the field's direction was clearer?
@hill23 Thanks for laying this out, genuinely useful.
24/7 factory-pilot support roles (the engineers keeping a deployed fleet running through real shifts) reportedly carry a real burnout risk, since they combine the unpredictability of early-stage hardware with the operational pressure of a live production environment. Companies like Figure, 1X, Apptronik, and Agility Robotics are reportedly pulling senior ROS, controls, and learning engineers directly out of warehouse-automation and industrial-robotics roles - a sign of real talent competition between adjacent industries, not just fresh grads entering the field.
they/them
Re: Anyone regret specializing too early before the field's direction was clearer?
@jessica_faro I see it a little differently.
A whole-body control engineer's day-to-day work is a mix of formulating and tuning constrained optimization problems, debugging why a controller behaves differently on hardware than in simulation, and a surprising amount of time spent on numerical stability and solver performance rather than pure algorithm design. Robotics engineers in the US were reportedly seeing $150k-$205k total comp at mid-level and $205k-$300k at senior level in 2026, with humanoid- and foundation-model-specialist roles clearing $280k-$475k - a meaningful premium over general robotics/automation roles.
"Torque is a lifestyle."
Re: Anyone regret specializing too early before the field's direction was clearer?
I'd take that specific number with a grain of salt, honestly.
Active employers hiring specifically for humanoid-relevant roles span both established robotics companies (Shadow Robot, Engineered Arts, PAL Robotics) and the newer venture-funded players (Figure, 1X, Apptronik, Sanctuary AI, Boston Dynamics' electric Atlas program) - each with different team sizes, cultures, and hardware-vs-software emphasis.
she/her
Re: Anyone regret specializing too early before the field's direction was clearer?
I can speak to this a bit.
In the UK, base salaries for robotics roles reportedly range from around £50,000 for new graduates up to roughly £200,000 for senior whole-body-control or reinforcement-learning specialists - a notably wide band reflecting how specialized the top end of the field has become.
Ex-automotive, now full-time robots.