DEV Community

Discussion on: What are your tips for an effective developer resumé?

Collapse
 
missamarakay profile image
Amara Graham

I'm a hiring manager, so I have a slightly different angle on this.

I think most of my advice is centered around "don't make me think". You want your resume to be so easy to read and parse that an HR system or a person can easily skim and find what they need.

List your technology, products, operating systems, frameworks, programming languages, etc. clearly. This should evolve overtime since you may write C in a university program and then never again, just like you may eventually decide you want to specialize in a particular JS framework.

Similarly, for projects and experience you may want to bold the items above if written in sentences.

Also for projects or experience, write exactly what you did on the team, not what the team did as a whole. It's more impactful if you write "led release automation" than "executed the full project lifecycle" or something cumulative. In the interview you can tell me a quick summary of what the whole team did if it necessary.