Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Two Mistakes in Dev Resumes (and How to Avoid Them)

DZone's Guide to

Two Mistakes in Dev Resumes (and How to Avoid Them)

Looking for a new development job? Learn how to knock the dust off of your resume and get the attention of more companies.

· Agile Zone ·
Free Resource

Employers and recruiters spend on average 7 seconds reading a resume so if you don’t immediately capture and retain their attention; your resume is going straight in the reject pile. As a Resume Writer, I have noticed these two common mistakes made in my Software Developer clients’ resumes. Take note of my advice and watch the interview invites come rolling in.

Your Resume Isn’t Tailored to Every Job You Apply To  

A common mistake made by my clients is that they use the same resume to apply to multiple jobs. You should have a different resume for every job you apply to. Job adverts posted by employers and recruiters differ so why would you use the same resume to apply for each job? Your resume needs to closely match employers’ requirements.

For each of the jobs, you are interested in, you should read the job adverts and identify the areas of experience the advert focuses on and tailor your resume accordingly.

For each position you’ve held, you should do the following:

  • Give an overview of your role (who do you report to and how many direct reports do you have, if any).

  • Explain your key duties that are required and desired by employers.

  • Give details of the projects you have been a part of including your own contribution (be selective of the projects you mention, only mention the ones which most effectively convey the value you added).

  • Detail the key technologies you have used in each role.

From reading your resume employers should be able to tell the following:

  • What types of projects you have been involved in.

  • What your technical strengths are.

  • How you have added value to projects, teams, and organizations.

  • How you have developed your skills (both technical and soft skills) throughout your career.

Your Resume Is Too Task-Orientated and Doesn’t Highlight Your Achievements

Employers like candidates who go the extra mile rather than those who just stick to doing what is expected of them. Mentioning achievements on your resume is a good way to stand out from the competition. Think about what quantifiable achievements you have achieved over the course of your career.

If you are struggling to think of any, below are some good achievements for developers:

  • Meeting or exceeding targets.

  • Significantly improving the performance of the existing software.

  • Developing and implementing a new software program.

  • Reducing costs.

  • Improving a process, operation, or a system.

  • Meeting or exceeding role or project specific outcomes/milestones.

  • Facing and effectively resolving challenges.

  • Contributing to reputable publications or websites (e.g. GitHub).

It is important to explain in detail how you achieved each accomplishment so employers can see what your contribution was. You should also use engaging language, figures, and metrics to sell your achievements.

If you follow my advice you will have a tailored achievement focused resume that sets you apart from the competition. If you take the time to re-write your experience, your technical and soft skills so they effectively express how you add value to teams and organizations, you will start getting interview invites.

Engineers build business. See why software teams at Atlassian, PayPal, TripAdvisor, Adobe, and more use GitPrime to be more data-driven. Request a demo today.

Topics:
dev career ,developer career ,devlife ,developer career path ,agile

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}