12 Mistakes Developers make on their resume
Planning to get a new job in 2016? Before you do that, update your resumé! There’s already a big competition on the market, so it’s important to make sure you avoid those common mistakes before handing submitting your application. I’ve gathered a list with 10 useful tips that will help get you your dream job!
Let’s get started!
- 1 Let’s get started!
- 2 Making Grammatical Errors and Typos
- 3 Submitting Incorrect Information
- 4 Giving everyone the same resume
- 5 No action verbs
- 6 Squeezing in as many words as possible
- 7 Omitting exact dates
- 8 Highlights
- 9 Make your resume ATS friendly
- 10 It’s tasteless
- 11 Career summary, instead of objective
- 12 Don’t forget your skills
- 13 Github, Stack Overflow, LinkedIn, Blog
Making Grammatical Errors and Typos
There’s no room for laziness. Your resume has to be grammatically correct and perfect. Otherwise, employers will take conclusions like “This person can’t write”, or “This person obviously doesn’t care.
Always try to get another pair of eyes to look at the file before submitting your resume. Reach out to a trusted mentor or a colleague in a similar industry, or if you’re a student, use the resources at your college career center or local library.
Submitting Incorrect Information
For some people, this might be obvious, but getting simple details wrong will get your resume tossed right into the bin. If you put an incorrect phone number or mess up the dates of your job titles, your resume will look disorganized. For example, if you’ll say you’re detail-oriented, and the employer catches incorrect information in your resume, this mistake is a big red flag.
Another thing you need to keep in mind is to not lie. The incorrect information can eventually leak out during the interview.
Giving everyone the same resume
It might come up as a surprise for some job seekers, but your resume is not supposed to be one-size-fits-all-jobs. Whenever you try to create this kind of resume it’ll quickly get ignored and thrown away. Employers want you to write a resume specifically created for their position. They expect you to be very clear about how and why you would fit in the position in a specific organization. Use the job description itself to make the position relevant for the specific position.
No action verbs
Avoid using phrases like “responsible for.” Instead, use action verbs: “Resolved user questions as part of an IT help desk serving 4,000 students and staff.”
Squeezing in as many words as possible
Stick to one page, don’t make it longer than that. In general, you should make sure that you’re answering the requirements within the job listing while also telling your most relevant employment story, including specific achievements that reflect what the employer is looking for.
Omitting exact dates
To leave out clear dates of employment often raises suspicion, which could make it look like you’re trying to cover up something. If you’ve got a big gap in your resume, try to address that issue and gap in a cover letter.
Don’t make too many highlights. Try to only highlight the most important parts of your resume so it doesn’t get too blurry and messy. It should be easy for the reader to scroll through and find your important parts.
Make your resume ATS friendly
Don’t use an image file such as JPEG or PNG. Most preferable is to create the document in the program Word since companies nowadays use ATS (applicant tracking system), which is a software application that allows the electronic handling of the recruitment needed. Since the system now can read your document, there are a few guidelines you have to follow:
Send a doc or docx file. ATS can’t read PNG, JEPG or any image file, write titles and subtitles.
Your resume should be a reflection of your professional life. You want to grab the reader’s attention in a few seconds so you don’t sound boring. Avoid clichés such as: committed, hard worker, dedicated, good communicator and works well with a team. Instead, you should highlight accomplishments that actually prove you’ve been accomplishing these abilities and qualities. Use a lot of action words and keywords that grabs the reader’s attention quickly.
Career summary, instead of objective
Skip the objective statement at the top of your resume. Instead, you should call it career summary and include a short description with 3-4 lines what you’ve achieved in your working career and what’s your passion and goals in your career.
Don’t forget your skills
Since you’re a developer you need to mention all the programming languages you know and your level of knowledge in each one of them.
Github, Stack Overflow, LinkedIn, Blog
Social platforms and blogs is always a good way to showcase your knowledge and what you’ve accomplished. You can build a good social media profile to make it worth showing for a potential employer. Put a link on your resume where it’s relevant. I’ve made a short summary of what you can do on these different platforms:
- Github – network for open source projects, work together with colleagues, informative profiles and a showcase of what you’ve been creating.
- Stack Overflow – network for asking and answering questions regarding technical questions, possibility to rank everything that’s being published, rewards with different badges and mastering of levels.
- LinkedIn – as you probably know is the biggest social media platform for business-oriented social networking service. So you can use it for networking and showing your career path.
- Blog – a perfect way to showcase everything you’ve been doing by documenting that in a blog.