LATEST CHATTY HEADER
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
New to Shacknews? Signup for a Free Account
Already have an account? Login Now
Subscribe to Shacknews Mercury starting at $1/month!
Chrome Shack Community Guidelines Chatty Search
Scroll down to join the conversation.
I'm reviewing resumes for a co-op position in a engineering role and I want to give a few tips for those of you preparing resumes. In reply because I'm irritated at stupid resumes.
Thread Truncated. Click to see all 28 replies.
I do like the way you write the bullet points. I agree with kramweil. The action verbs are good. You could shorten many of them up. e.g. "Developed tools for automation log retrieval, parsing and summary reporting" instead of the paragraph you have. You also list the tools used after each bullet and again at the end of the job. Listing them at the end of the job probably makes sense for your industry, but you could save space and redundancy by only listing them there.
Other examples I'd shorten:
"Developed a summary dashboard with daily polling"
"Developed a replacement time sheet system (incl. vacation, project labor distribution, summary reporting)"
I don't like the "2.5 years of accumulated experience" as a bullet. You already say Summers 2002-2006.
The profile section isn't bad, but you need to shed lines, and this would be a good place. The first two bullets kind of make me roll my eyes when I see something like that on a resume. I'd rather see something like "A passion for building tools that lower barriers for others" or something that tells me what you like.
Another thing that would be very good to include is a few words in one of these projects about requirements gathering. E.g. that you built a system based on a design document that you co-authored with engineers, or that you had an iterative development with interim review by customers. If you worked with the end users of your code on the project that's a huge plus for me. I don't know if it's true though :)
There are definitely people that don't mind longer resumes. This one got you hired obviously. I'm just giving you my perspective on it as if it came across my desk.
FYI my wife was looking for someone just like you recently and thinks your experience is awesome. You'd have gotten an interview with her for sure. I thought the skills section was too long, but she thinks it's informative. Other people don't have that section, so it stood out to her. One warning, when you list the skills and your proficiency she called that "brave." Whatever people put on their proficiency level (e.g. advanced) we assume is one level lower :). And be very aware that anything you put "advanced" on you WILL get grilled in an interview. It's a challenge to a technical interview, so you better be sure. Also, she suggests not putting advanced for any skill you haven't used in a job (learning it in a class would never fly as advanced proficiency). So, she's been looking at resumes to hire someone like you and thinks your skills are great (to hire someone to do exactly this kind of engineering support, automation data handling and reporting).
The post has been reported. Thank you!
You must be logged in to post.
You must be logged in to post.