Is it better to specialize early (perception, controls, ML) or stay generalist?

[nicole57]

Curious what people here think about this. 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. 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. 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. Curious to hear how others see this.

[ethan17]

@nicole57 I'd frame this differently. 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.

[benjaminsanchez]

@ethan17 I can speak to this a bit. 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.

[cynthia.muller]

@benjaminsanchez Same conclusion I've come to. Also worth noting: 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.

[gary.tanaka2]

@cynthia.muller Thanks for laying this out, genuinely useful. 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. 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.

[nancy_lewi]

This raises a question for me - 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.

[jwang]

@nancy_lewi I'd push back on this a bit. A field-deployment or reliability engineer's day-to-day work leans much more toward diagnosing real-world failure patterns, managing spare-parts logistics, and working directly with the customer site than toward algorithm development - a genuinely different role than a lot of new grads expect going in. 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. This whole thread is a good reminder how young this field still is.

[carol.robinson]

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.

[sarah.santos3]

@carol.robinson Slight correction, though the overall point stands: 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. 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.

[ethan17]

@sarah.santos3 This lines up with my experience. 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. 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.