What a robotics engineer actually does

A lot of people hear "robotics engineer" and imagine someone designing a humanoid from scratch

In reality the job splits into specialisms, and you pick one and stay literate in the rest:

• perception and computer vision
• controls and state estimation
• motion planning and manipulation
• robot learning
• embedded and firmware
• simulation
• systems and integration
• deployment and operations

I read live job listings from Figure and Skild, and the same four requirements appear in every single one:

• C++ and Python, both, not one or the other
• experience on real hardware, since simulation-only does not qualify you as senior
• depth in one specialism and literacy across the rest
• debugging named as a skill in its own right

Notice what is not on that list: a specific degree

That is why this roadmap is built around making things work rather than studying theory, and why every section below ends with something you have to build

Keep whatever is paying you while you do it, treat this as two or three hours a day, and the six months are designed to be run that way