What's the honest truth about work-life balance during a factory pilot crunch?

[mia_lars]

That's the official framing, at least - reality tends to lag a bit. 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. 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.

[deborahperez]

Still learning the space, so correct me if wrong - 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.

[karen.chen3]

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

[dchen]

@karen.chen3 From hands-on experience, 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.

[mia_lars]

@dchen Respectfully, I think this undersells it a bit. 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. This whole thread is a good reminder how young this field still is.

[dubois35]

I don't think that's quite right, for what it's worth. 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. 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.

[park44]

@dubois35 Speaking from personal experience here, 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.

[nicole57]

Minor factual note: 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. 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.

[carlossanchez]

@nicole57 That's the official framing, at least - reality tends to lag a bit. 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.

[deborahperez]

@carlossanchez From hands-on experience, 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.