Job Description:
Must have ROS / robotics experience!
In looking at the resumes - a lot of what he is seeing is firmware candidates - want to look for robotics candidates
Seeing embedded C, working with micro controllers, lots of HP/Micron people have that background - most of the staff has that background but it takes 3-6 months to get into the robotics side
Trying to move fast - don t want a ton of ramp up time
Key robotics tech - software stack called ROS - everything Bastian has done is built on top of ROS - started in schools/universities or who has done it professionally
Need exp working with hardware / sensors - PID control algorithms, moving motors - making something spin, driving something around - a lot of firmware candidates are just working with chips/circuits
CAN / CANopen isnt always in robotics - sensor data, cameras, LIDAR
Have a lot of code written, but theres a lot of places where its not reliable/fast - this is a very hands on role - needs people that can sit with the robot, run it, observe where its slow, shaky, why its crashing, why its not reliable - use their experience so brainstorm through things like code changes
Looking for someone who has been hands on with a robot or vehicle in some way - not just writing code and handing it off to someone else - should be familiar with writing code and testing on something real
Would love to find someone from Amazon Robotics, someone that has actually been doing robotics and working as a robotics engineer - wouldn t be calling themselves an embedded engineer
Amazon engineers don t use ROS - they use something custom - doesn t have to say ROS but that s typically what to target - 6 access robot arms, AGVs, AMRs, self driving forklifts - can look for those key terms
Locust robotics, fox robotics (self driving forklifts), amazon robotics - robotics engineers - would love to find someone with an actual robotics background
Need to make sure they don t have a non disclosure / non compete clause
Here are a few ideas for screening questions. We really need people to have experience with:
- Modern C++ (C++11 and onward)
- Should have experience w/ Smart Pointers, Templated Classes, Abstract Classes
- Should have experience designing new system in C++, not just experience debugging or working on existing code.
- We highly value experience with hardware communication protocols, specifically:
- CAN and CANOpen (often used in Robotics and Automotive)