jmroberts70
2[H]4U
- Joined
- Oct 15, 2002
- Messages
- 2,953
Yeah, this thread is truly a valuable resource!
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Look for help on formatting and names of tech.
You should take a pass through for grammar. "* System administrator for 175 clients locations in 4 states" should be "for 175 client locations in four states", for example.
Some of the things you list are quantitative, like that one. Most aren't;
It's a matter of style, so you can decide. But I just can't stand numbers less than ten being written out ("4" instead of "four"). And abbreviations ("Jun 08" instead of "June 2008") drive me bonkers. Most style manuals agree with me, but it's your call ...
You have headings with locations and dates. For these, I usually add companies and titles.
I'd suggest getting rid of the paragraphs that explain your duties at each position and instead format your resume to spell out your skills in detail. The "life history" you lay out over 2 pages is a bit much to read just to see if you are experienced with .NET development or working within a Microsoft domain environment. There are examples on this rather long thread as well as a rather old resume on my website (in my sig below).
MrGuvernment suggested that I post my own resume here, and I guess it's a good idea as I was just in the process of updating it. I've done a lot of writing and presentations, so I send out a separate list of speaking engagements and bibliography.
If you find any errors, let me know! I like the format, mostly -- but sometimes wonder if it's too long. The racing stuff at the end is really just a hobby, but it also goes towards my ideal job. Working on the stuff I do is great, but if some automotive manufacturer came along and said they needed firmware for, then I'd be all ears!
MrGuvernment suggested that I post my own resume here, and I guess it's a good idea as I was just in the process of updating it.
Your employment history can be a single line for each position you've held. Any more detail should be left for the interview!
Eh?
One wants to at least write something about key accomplishments at each job. You won't get an interview just by writing that you worked for Microsoft because the crucial piece of information as to whether you cleaned the floor or wrote code is missing. I can't even believe anyone would suggest to not list at least *some* info about performance for each job. Srsly.
If I was interviewing a musician, I'd rather see a list of his songs, their chart positions and awards, tours, and so on -- instead of just "EMI Music, Inc; New York City; Recording Artist".
People who lose interest stop reading; they don't necessarily discard the candidate. If they want to know the details or history, they read the whole thing. Most of the interviews I go to have a question that breaks the ice about either auto racing or "the old days".
I think my resume does both; the first page is at-a-glance skill sets and accomplishments, while the rest gives details about the specifics. The layout lets the reader just turn the page to move around within the resume. I can make the oldest sections shorter, but then I'm left with whitespace. The page is already there -- why not use it?
Hey all, aren't resumes supposed to only be a page long and any longer is detrimental? Just wondering, since I've seen some around 2+ and was wondering what to do with mine as well.
It has more to do with attention spans. I think many resume readers (of which I am one) just lose interest after a dense page of your life story. If you can't summarize your background and skills in one page, maybe you're just saying too much.
I don't think there's a rule. I don't mind reading longer resumes, and mine's more than two pages--and has attachments. I also write prose instead of bullets.
I still need to get my Network+, but they just redid the test and I haven't gotten the new studybook yet >_>