Quote:
Originally Posted by gblake
I'm going to insert one more piece of general purpose advice here.
Because I know what it means to be a strong contributor to a student-robotics team, I was able to translate an short phrase like "FRC drive team captain" or "award-winning VRC notebook" into the sorts of candidate attributes employers look for.
But, not everyone reviewing job applications (the vast majority in fact) knows how to translate those short phrases. In applications, you/we/I need to convey what those mean, both in terms of talents we possess and in terms of accomplishments we achieved.
So, take a look at your resumes, your LinkedIn profiles, and anywhere else you want to make an impression on a potential employer; and make sure that you are telling your story well enough for folks *outside* this community to know how valuable your can be to them.
Blake
|
Seconding this. One of the biggest issues I have at work is explaining to higher ups why something is important. I can talk to the folks I work with directly about how I created a new d3 visualization for the provider view. Means pretty much nothing to someone who is in upper management. So my supervisor has started stressing the need to answer the question, "What was the impact to the sponsor?".
So, for folks putting FRC Drive Team Captain... what is the impact to your team? Why is that experience relevant? Perhaps talk about decision making under pressure, thinking on your feet, analyzing a problem. Give it to them in terms they understand and can apply to their problem. When I'm hiring an intern "Award Winning VRC Notebook" isn't applicable. But "Award winning technical documentation" sure is.