What's underrated on a resume that most candidates leave out?

Getting into the field, degree paths, labs, papers, internships, and career/salary discussion.
camila.jackson0
Posts: 225
Joined: Wed Oct 09, 2024 1:27 am

What's underrated on a resume that most candidates leave out?

Post by camila.jackson0 »

Trying to organize my own thinking on this, so bear with me. 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 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. What's everyone else's take?
Building > buying.
ashley_flor
Posts: 109
Joined: Fri May 09, 2025 8:12 pm

Re: What's underrated on a resume that most candidates leave out?

Post by ashley_flor »

Just to be precise about one thing: 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.
cynthia.muller
Posts: 135
Joined: Sun Feb 16, 2025 8:23 pm

Re: What's underrated on a resume that most candidates leave out?

Post by cynthia.muller »

@ashley_flor I'd take that specific number with a grain of salt, honestly. 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.
Opinions my own, not my employer's.
green28
Posts: 109
Joined: Sun May 11, 2025 2:06 am

Re: What's underrated on a resume that most candidates leave out?

Post by green28 »

@cynthia.muller I'd take that specific number with a grain of salt, honestly. 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.
nicole57
Posts: 208
Joined: Wed Dec 04, 2024 1:29 am

Re: What's underrated on a resume that most candidates leave out?

Post by nicole57 »

@green28 Yeah, this tracks with what I've read as well. 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.
she/her | grad student, biped locomotion
johnrossi
Posts: 119
Joined: Thu Jun 19, 2025 2:39 am

Re: What's underrated on a resume that most candidates leave out?

Post by johnrossi »

@nicole57 I'll believe the stronger version of that claim when it's independently verified. 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. 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.
she/her
erik_novi
Posts: 192
Joined: Sun Oct 13, 2024 6:23 am

Re: What's underrated on a resume that most candidates leave out?

Post by erik_novi »

I'd push back on this a bit. 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. 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.
she/her
pierregreen
Posts: 205
Joined: Thu Dec 12, 2024 11:01 am

Re: What's underrated on a resume that most candidates leave out?

Post by pierregreen »

@erik_novi I'd take that specific number with a grain of salt, honestly. 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.
she/her
byang
Posts: 142
Joined: Thu Apr 17, 2025 5:26 am

Re: What's underrated on a resume that most candidates leave out?

Post by byang »

Not sure I fully agree here. 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."
ssantos
Posts: 105
Joined: Wed Sep 03, 2025 12:03 am

Re: What's underrated on a resume that most candidates leave out?

Post by ssantos »

Yeah, this tracks with what I've read as well. 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.
they/them
Post Reply