Seeking Advice: Career Pathways and Essential Skills for Robotics Engineers

[RinatM]

Hello Fellow Robotics Engineers,

I'm reaching out to gather insights on what the industry currently seeks in a Robotics Engineer, particularly the skills that are most valuable across various sectors such as mobile robotics, automation, industrial robotics, surgical applications, humanoid robots, etc.

A bit about me: I volunteer as a robotics engineer for a small startup focused on Maritime Robotics. I enjoy my work and am keen on continuing with this group. At the same time, I aim to enter the field as a professional. I've been learning ROS, exploring different localization and navigation techniques, and delving into mission planning, simulation, and controls. Once proficient in these areas, what else should I know to stay competitive?

I understand the industry often favors highly specialized, experienced individuals. I'm considering deepening my expertise in areas like SLAM algorithms or enhancing my skills in physical modeling simulations.

I would love to hear about your experiences, what skills have helped you succeed, and any advice you have for a junior engineer looking to make their mark in the robotics field. Any specific guidance related to your area of specialization would be particularly helpful.

Thank you for sharing your wisdom and insights!

 

[DomainRM]

"Robotics" encompasses a wide range of specializations, so could you specify which particular area interests you—like controls, perception/vision, hardware design, or path planning? Many who identify as "robotics engineers" actually come from diverse engineering backgrounds. I often use the term 'robotics engineer' for simplicity, as it's more universally understood compared to 'mechatronics design engineer,' for example. In my company, we have electrical engineers focusing on controls, software engineers handling system architecture, and my role involves a lot of sensor selection and hardware logic processes. We might all label ourselves as robotics engineers, but each of us has a distinct area of expertise.

Ultimately, a robot is a sophisticated system that integrates mechanical, electrical, and control elements, necessitating specialists in each of these domains to create an effective robot.

 

[RinatM]

"Robotics" encompasses a wide range of specializations, so could you specify which particular area interests you—like controls, perception/vision, hardware design, or path planning? Many who identify as "robotics engineers" actually come from diverse engineering backgrounds. I often use the term 'robotics engineer' for simplicity, as it's more universally understood compared to 'mechatronics design engineer,' for example. In my company, we have electrical engineers focusing on controls, software engineers handling system architecture, and my role involves a lot of sensor selection and hardware logic processes. We might all label ourselves as robotics engineers, but each of us has a distinct area of expertise.

Ultimately, a robot is a sophisticated system that integrates mechanical, electrical, and control elements, necessitating specialists in each of these domains to create an effective robot.

I appreciate your point about the broad scope of robotics engineering, which I did try to address in my original post. That's why I framed my question to encourage responses specific to each individual's area of expertise.

To clarify my interests, I'm drawn to mobile robotics across various applications, including maritime, agriculture, and warehouse operations. Specifically, I'm keen on roles related to SLAM engineering, path planning, or other navigation-related areas. Additionally, given my educational background in Mechanical Engineering, I'm also interested in mechanical or electromechanical design.

The main intention behind my post was to understand from other professionals about their journeys in the robotics field, the challenges they faced, and what it took to secure their roles. I'm eager to gather insights that could guide me, and others like me, in starting a career in robotics, whether it's in SLAM, path planning, or design. I hope to learn from experiences across all specializations within this diverse field.

 

[MikeSXS]

I work in industrial automation, where the number of robots involved can vary significantly from project to project—ranging from none to a considerable amount.

Firstly, you'll need a solid foundation in both mechanical and electrical skills. It's essential to be able to troubleshoot various issues, whether it's a grease leak or a communications/power outage, with equal proficiency.

Additionally, strong problem-solving abilities, spatial thinking, and communication/documentation skills are crucial. You should be familiar with a range of programming concepts, from basic 'if-then' statements and 'for-loops' to more complex techniques like indirect addressing and managing parallel tasks.

From there, consider exploring different robotic manufacturers to get acquainted with their programming environments. For instance, Fanuc offers Roboguide for offline programming, and similar tools are available from other companies like Kuka and ABB.

If you're leaning towards R&D rather than industry, the mechanical and electrical foundations remain essential, along with the skills mentioned above, for any role you pursue.