Equal parts higher-ed IT, web dev and support; with a dash of freelance consulting thrown in for good measure. (Oct/19: Seeking change of pace. Not afraid to take a step back in order to move ahead!)
For my own resume (assorted dev roles since 1999), I aim for:
two pages: one physical page when printed duplex
font size of 10/11pt: it needs to be readable without a magnifying glass
line-spacing of at least 115%: ditto above...legibility!
no-frills font face: I'm partial to the PT Serif/Sans families
highlight one or two recent projects in a section of their own: not necessarily wrapped up with employment history
limit employment history to the last 10 years: got an irrelevant job in the middle of that spread, list it to show you were employed, but don't bother elaborating on the particulars.
skip the "Objective" statement: it's a waste of space; besides, that's what your cover letter is for... You did write a cover letter, right?!
I also prepare a second document which may or may not accompany the resume depending on the nature of the job I'm interested in. That second document is an exclusive Project Summary. Again, it's limited to two pages and follows the same formatting rules as my resume; however, its purpose is to expand on specific projects--dates, role, tech stack, etc.--that I've been involved with recently (or in the past if a particularly proud accomplishment).
Now that's the way I do things as a "seasoned" developer (I hate the "junior", "intermediate", "senior" pigeon holes!)...
In my time, however, I've seen great resumes and crap resumes from potential hires. The great resumes are (1) legible and (2) concise. The crap resumes usually (1) look/read like they came from a MS Word 2000 resume template, (2) require a microscope to read and/or (3) cover the applicant's entire life history...I'm talking a dozen+ pages!
In a nutshell:
Be clear
Be concise
Be legible
Skip the buzzwords
Be yourself!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
For my own resume (assorted dev roles since 1999), I aim for:
I also prepare a second document which may or may not accompany the resume depending on the nature of the job I'm interested in. That second document is an exclusive Project Summary. Again, it's limited to two pages and follows the same formatting rules as my resume; however, its purpose is to expand on specific projects--dates, role, tech stack, etc.--that I've been involved with recently (or in the past if a particularly proud accomplishment).
Now that's the way I do things as a "seasoned" developer (I hate the "junior", "intermediate", "senior" pigeon holes!)...
In my time, however, I've seen great resumes and crap resumes from potential hires. The great resumes are (1) legible and (2) concise. The crap resumes usually (1) look/read like they came from a MS Word 2000 resume template, (2) require a microscope to read and/or (3) cover the applicant's entire life history...I'm talking a dozen+ pages!
In a nutshell: