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.
People really put course numbers on their resumes? Wow. I can't even remember what material I learned based on the course number, and I was in those classes day-in day-out. Heh. I had a version which touted course material, but all the jobs in the area were looking for experience over education. I'll certainly keep your tips in mind in the future though.
This must have been a slightly older draft, as I know I fixed the "discrete" thing in the final version, and changed the wording to make it sound less like I'd used assembly language in the prototyping phase. Or at least I hope I did. : /
Also, the motions were totally discreet. The hand could cop a feel without anyone noticing, and wouldn't tell anyone about it.
Kramweil was right, I have a standard header with my name in large font with my contact information immediately below on a single line, all centered, only on the first page, with the font faces matching the body (heading/text), a la:
SwiftyPants
Address, City, Prov., Postal Code * AC.Phone.Number * email@address.com
I neglected to mention that this version would be paired down based on where I was applying, so I would be able to fit it in on two pages with the header and also throw in a few job-post buzzwords. I would have also tuned certain points based on the job. Regardless, by the time I'd got to this version, I was sick of re-writing the bullets. I agree that many points could be shorter.
The tool lists in both the bullet and at the end was a toss up. I ended up leaving them in since they didn't add to the overall length of the document. Mostly I wanted to emphasize where I was using what, but in hindsight I probably don't need them.
Originally I didn't have the "accumulated experience" stuff. That was specifically requested by the recruiter who got me my recent job. I thought it was odd too, but I got the job, so *shrug*
It's funny you should mention the first two lines. The very first draft of this resume was taking a buddy's and changing his name to mine as a starting point. I think those are the only two hold-over's from the original. That being said, I couldn't really come up with anything better without sounding equally as eye-rolly.
It's also amusing you should mention requirments gathering. In my very first job, I didn't know WTF about software development. My boss told me to make an app that did a few things, and I did. He'd use it, comment, and I'd fix it. By the time I was done at that job, that's all I'd done. So when he invited me to ATi to continue working for him, the requirements ended up being: "Do what you did for me at Quake here at ATi." And when AMD bought them out, and I continued working there, it was essentially the same. At the end of my current contract, I'll finally be able to have a good bullet point about requirements gathering. :)
I completely agree about the "Advanced" thing being risky. I only put that on skills where I know I had used very advanced topics proficiently, and could (at the time of writing) recite complicated processes and methods off the top of my head. Like how to go about building a Google-docs type application in JS/CSS, or configuring Apache with multiple domains, using re-writing to get a nice URL for complex/deep PHP page structure, or tuning MySQL performance issues with replication for large databases.
You do bring up a good point that I completely missed, in that I never mentioned how I used OO design/analysis in any of my jobs (even though I did break out mad UML and abstraction skills). I'll have to keep that in mind for the future.
Anything that I'd only ever used in a class would never be advanced. I had a section under "Concepts" called "Education Material" that got cut. All the Engineering education/skills I had there specifically stated specifically stated it was in a class environment, and (depending on the topic) was only Beginner/Intermediate. Stuff like DSP, Control System Design, Electronic Circuit Design and Construction, etc.
The post has been reported. Thank you!
You must be logged in to post.
You must be logged in to post.