Just going to throw everything out as word vomit, remember that this is a work of iteration. There's tons of advice out there about how to write a resume, but at the end it's a very personal document to write.
Some of my per section recommendations:
Technical Experience
Remove side projects from the header, it's not necessary
Remove KLOCS, instead opt to add descriptions of your experience. Built something you're proud of? talk about it!
Your experience should speak at your capabilities, saying you know linux and git adds nothing but something like "Built a linux console application that utilizes git to achieve *" has more value.
Education:
Trim trim trim, anything before college doesn't matter, unless you have something super awesome to put in. At your level of experience, maybe list some relevant courses or a current GPA if it's really high
Languages: not relevant to your professional experience, so it doesn't belong in your resume
Professional skills: I'm mostly against giving a laundry list as these are mostly shallow. "Responsible"? "Analytic ability" what do they actually mean to the person reading your resume? You have about 1 paragraph worth of space to put something more personal in your resume and those words can be part of that: "A Passionate team-worker with great attention to detail with X amount of experience" Note that even that sounds kind of impersonal.
Other:
Doesn't belong on your resume
References:
Ditto, it's obvious that you have references upon request, why waste space on your resume?
Some general recommendations:
The text on your resume should speak about your RELEVANT professional experience and nothing else. The rest can be represented in a cover letter/interview
Anything more than 1 page is tiresome to read and messy to handle. Don't forget that this is going to pass several hands (hopefully)
Your resume is usually the only thing representing you between a stack of dozens more, it should be informative and interesting enough to get noticed.
Always tailor your resume to the job - Are you applying to a position that requires Java and Linux experience? Show that off and remove your prolog/lisp/asm experience.
Some of my per section recommendations: Technical Experience Remove side projects from the header, it's not necessary Remove KLOCS, instead opt to add descriptions of your experience. Built something you're proud of? talk about it!
Your experience should speak at your capabilities, saying you know linux and git adds nothing but something like "Built a linux console application that utilizes git to achieve *" has more value.
Education: Trim trim trim, anything before college doesn't matter, unless you have something super awesome to put in. At your level of experience, maybe list some relevant courses or a current GPA if it's really high
Languages: not relevant to your professional experience, so it doesn't belong in your resume
Professional skills: I'm mostly against giving a laundry list as these are mostly shallow. "Responsible"? "Analytic ability" what do they actually mean to the person reading your resume? You have about 1 paragraph worth of space to put something more personal in your resume and those words can be part of that: "A Passionate team-worker with great attention to detail with X amount of experience" Note that even that sounds kind of impersonal.
Other: Doesn't belong on your resume
References: Ditto, it's obvious that you have references upon request, why waste space on your resume?
Some general recommendations: The text on your resume should speak about your RELEVANT professional experience and nothing else. The rest can be represented in a cover letter/interview
Anything more than 1 page is tiresome to read and messy to handle. Don't forget that this is going to pass several hands (hopefully)
Your resume is usually the only thing representing you between a stack of dozens more, it should be informative and interesting enough to get noticed.
Always tailor your resume to the job - Are you applying to a position that requires Java and Linux experience? Show that off and remove your prolog/lisp/asm experience.
Feel free to re-draft for more specifics
reply