Recently we broke the internet with a Resume Review dev.to post and tweet. OK - we didn't break the internet, but my notifications were definitely fried. Overall it was an amazing thing to watch the community help each other out. I reviewed as many as I could bear before holiday, and will be continuing to go through and try to catch any that fell through the cracks.
Out of the many I reviewed and comments I've seen from other reviewers and more, I've compiled the list of the most common mistakes collectively caught.
Recruiters and managers pass your resume around via email and printed paper. Run it through a printer, make sure it looks good in black and white and that it's not cut off anywhere.
A resume is designed to be a quick review of your skills, experience, and education. It should not be an extensive dive into the last 20 years of your life. Here's a few quick tips to cutting down on the number of pages:
- list only relevant experience/projects
- use bullet points and not complete sentences.. remember easy to skim
- position your resume for the job you want not the job you have
- try different layouts, helps to think of your resume as a website. How would you optimize a blank page to fit everything without scrolling?
It's hard to know what to put down if you're new to the field. But, this also gives you so much room to boast about what cool things you've built. What classes did you take? What group projects have you built? What languages did you use, or are currently learning? What technologies are you familiar with? Git? SVN? npm? All the acronyms?! This is your chance to highlight your accomplishments, what you're learning, and what you're interested in. In technology, you're greatest skill is being able to learn new things. Show it off!