You are awesome, Ricardo! I always love to hear your talks and contributions. I have some comments: 1. You are right that ROS is not a core skill, but it is likely changing as the number of users grows rapidly. 2. ROS is not used by companies that produce robots (I refer here to manipulators) - large companies tend to use ROS interfaces instead. 3. ROS is often used by integrators or equipment producers, who frequently utilize their own products in combination with the manipulator ROS interface. 4. ROS 2 is a powerful and exceptional platform, as you mentioned, for learning, exporting, and contributing. 5. From my point of view, it will be an extremely important feature or skill, especially since NVIDIA Isaac uses ROS 2 to simulate robots and deploy later on Jetson Boards. 6. Most robotics research utilizes ROS. Personally, as a postdoc in underwater robotics, I use ROS 2 every day along with many top researchers here at my Univ. We employ ROS 2 for prototyping, advanced simulators, the various robotics frameworks we use, and during deployment on our vehicles. We have ROS 2 interfaces for everything. You are the most important part of this framework, Ricardo!
Thanks for putting the time into this! For the education level, I do feel like there's some slight bias as recruiters tend to change their educational level to whether filter out more, or to get more application pool. Nevertheless, loves seeing the data.
How do you acquire all that data from LinkedIn? Why not conduct the same analysis for the European market? it's a great video, thx!! On the other hand, from my point of view, robotics is a growing field, yet there are very few companies that implement robots in real-life applications. While it may be somewhat common in Japan, in the rest of the world, it remains uncommon.
Yes you are right it is a growing field. The point that worries me is that ROS is not moving fast and other companies may try to impose their system instead of using ROS...
@@RickTellezL Because ROS is not an industry standard, it requires time to creates its own snowball effect, similar to other technologies. However, there is a lack of documentation for ROS 2 and a poor Python interface, which complicates things for new adopters...
That is a very good question! And the answer is that I searched for "Robotics Software Engineer" jobs. So the search is biased towards software development for robots. That is why the other careers more focused on the hardware are less demanded
You better 25 years old and already 26 years experience including software, hardware, AI , electronics and mechanical by the way also know some biology
![How to Get a Developer Job - Even in This Economy [Full Course]](http://i.ytimg.com/vi/6nz8GXjxiHg/mqdefault.jpg)
![How to Get a Developer Job – Even in This Economy [Full Course]](/img/tr.png)
The ROS Developer Podcast is back! Thanks for sharing valuable info, Ricardo😊
You are awesome, Ricardo! I always love to hear your talks and contributions. I have some comments:
1. You are right that ROS is not a core skill, but it is likely changing as the number of users grows rapidly.
2. ROS is not used by companies that produce robots (I refer here to manipulators) - large companies tend to use ROS interfaces instead.
3. ROS is often used by integrators or equipment producers, who frequently utilize their own products in combination with the manipulator ROS interface.
4. ROS 2 is a powerful and exceptional platform, as you mentioned, for learning, exporting, and contributing.
5. From my point of view, it will be an extremely important feature or skill, especially since NVIDIA Isaac uses ROS 2 to simulate robots and deploy later on Jetson Boards.
6. Most robotics research utilizes ROS. Personally, as a postdoc in underwater robotics, I use ROS 2 every day along with many top researchers here at my Univ. We employ ROS 2 for prototyping, advanced simulators, the various robotics frameworks we use, and during deployment on our vehicles. We have ROS 2 interfaces for everything.
You are the most important part of this framework, Ricardo!
Thank you Markus for your comments and additional data!
Good job Ricardo, its very clear the market in US. Is this same case in Europe?
"Something you won't like, Documentation" You made me roll on the floor on this one Ricardo 😂. Good video as always.
😅
Thanks for the insight. I was frustrated about the jobs availability.
Currently working in startup using ROS2, simulation and controls.
Heyy bro
Can you share me details how you get into startup or how you are learning robotics
Can we get connected in LinkedIn...
Congratulations!
Thanks for putting the time into this! For the education level, I do feel like there's some slight bias as recruiters tend to change their educational level to whether filter out more, or to get more application pool. Nevertheless, loves seeing the data.
Great video thanks Ricardo for doing this!
Thanks for your support Jason!
Thank you for your sharing. That help me form my path to become robotic software engineer.
So happy to see it was useful for you!
How do you acquire all that data from LinkedIn? Why not conduct the same analysis for the European market? it's a great video, thx!!
On the other hand, from my point of view, robotics is a growing field, yet there are very few companies that implement robots in real-life applications. While it may be somewhat common in Japan, in the rest of the world, it remains uncommon.
Yes you are right it is a growing field. The point that worries me is that ROS is not moving fast and other companies may try to impose their system instead of using ROS...
@@RickTellezL Because ROS is not an industry standard, it requires time to creates its own snowball effect, similar to other technologies. However, there is a lack of documentation for ROS 2 and a poor Python interface, which complicates things for new adopters...
Why robotic Engineering have a lowest chance to get a job in robotic developer. That is so weird.
That is a very good question! And the answer is that I searched for "Robotics Software Engineer" jobs. So the search is biased towards software development for robots. That is why the other careers more focused on the hardware are less demanded
@@RickTellezL Ah. That’s why. Thank you so much.
You always have to be young AND experienced 😅
ha ha ha...😅
You better 25 years old and already 26 years experience including software, hardware, AI , electronics and mechanical by the way also know some biology