3 ms·
Would you have time to review my resume and help set an achievable get-in-the-field project goal?
by singlepaynews 2y ago
Would you have time to review my resume and help set an achievable get-in-the-field project goal?
- jvanderbot 2y agoI've hired a few roboticists and my advice is always the same - if you're a new grad, knowing ROS and having strong C++, ROS, and OpenCV experience will give you a leg up. After that, the most common things new grads want to work on are path planning or computer vision. These are high-ish demand but usually go to grad students or senior folks. But you can be an excellent candidate by knowing about them and how to integrate and test them. Path planning has several open source libraries and implementations. Do a comparison on several maps. Pull game maps and try em out. Anything. For AI/CV, there's similarly many applications. The key for non-PhDs is to know the existing stuff well. Even if you're a PhD, you'll spend less than 1% of your time doing anything interesting / researchy, and will mostly be using existing codebases for everything. Very few research-primary positions exist.
- singlepaynews 2y agoSo, the advice for companies is "avoid ROS", but the advice for entrant engineers is "have ROS experience"? What about, e.g., Drake? (https://drake.mit.edu https://drake.mit.edu) How is experience meant to be demonstrated? Do you do a home project and put it at the top of your resume? Edit: I don't mean to be pedantic; I'm just ~6 years out of touch here. I did a SLAM-in-quadcopter and force-controlled-6dof-arm in undergrad, and those projects are being correctly ignored by hiring managers as "he's since forgotten this stuff" today.