Page 2 of 2
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Tue Apr 07, 2026 11:19 am
by lbianchi
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.
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Fri Apr 10, 2026 7:38 am
by jlefebvre
@lbianchi I'd frame this differently.
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.
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Sat Apr 11, 2026 10:58 pm
by sharonschmidt
@jlefebvre This matches what I've seen too.
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. 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.
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Wed Apr 15, 2026 9:19 am
by james15
Short answer:
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.
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Fri Apr 17, 2026 5:22 pm
by richard36
Yeah, this tracks with what I've read as well.
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. 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.
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Sun Apr 26, 2026 12:05 pm
by jessica_faro
I can speak to this 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. 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.
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Tue May 05, 2026 5:28 pm
by jlefebvre
@jessica_faro I see it a little differently.
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 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.
Re: How much does a strong GitHub/portfolio actually matter for hiring here?
Posted: Thu May 14, 2026 7:08 pm
by choi98
@jlefebvre Speaking from personal experience here,
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.