Page 2 of 3

Re: How do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Mon Nov 24, 2025 8:05 pm
by george92
@nancy_lewi I see it a little differently. 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. Kind of makes me think about how different this all looked even three years ago.

Re: How do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Tue Nov 25, 2025 4:22 am
by mohammed.rossi
@george92 Related question - 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 do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Tue Nov 25, 2025 7:35 pm
by nancy_lewi
Same conclusion I've come to. Also worth noting: 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.

Re: How do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Fri Dec 05, 2025 7:22 pm
by zoeanderson
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. 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 do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Mon Dec 15, 2025 11:05 pm
by carlossanchez
@zoeanderson To answer this directly: 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. 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. Reminds me a bit of the early drone hobbyist scene, honestly.

Re: How do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Tue Dec 23, 2025 4:24 pm
by shill
@carlossanchez This lines up with my experience. 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 do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Sun Jan 04, 2026 1:42 am
by mary.taylor6
Here's what I know on this: 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 do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Sun Jan 11, 2026 2:35 am
by sarah.santos3
@mary.taylor6 +1 to this. Worth adding: 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.

Re: How do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Fri Jan 16, 2026 10:27 pm
by carter42
@sarah.santos3 Here's what I know on this: 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. 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.

Re: How do you keep your mechanical skills sharp if your day job is mostly software?

Posted: Sun Jan 25, 2026 1:56 am
by jwang
@carter42 Minor factual note: 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. 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.