DEV Community

Cover image for How to Improve Your (Junior) Developer Resume Bullets
Andrew Stetsenko
Andrew Stetsenko

Posted on • Originally published at

How to Improve Your (Junior) Developer Resume Bullets

How to make your tech resume attractive to employers and recruiters if you don’t have a lot of professional experience? Strengthening experience descriptions is one of the ways you can achieve this goal.

Jointly with the team of CV Compiler, an ML-powered app for resume improvement, we’ve run through dozens of junior developer resumes to pick up “weak” bullet points and show by example how it is possible to make them sound more impressive. Take a look at the difference:

I was responsible for designing and implementing X feature for the XYZ CRM.

Designed and implemented X, a new built-in CRM feature enabling its 20k users to easily keep track of their business expenses.

Implemented social login and profile autofill functionality using OAuth with JavaScript.

Achieved a 20% uplift in conversion rates by implementing social login and profile autofill functionality using OAuth with JavaScript.

Reduced page load time using Ajax.

✓ Reduced 30% of the page load time using Ajax.

Rebuilt the home page on the website.

✓ Rebuilt the home page, improving page load time by 3 seconds with updated code.

Worked with senior developers to develop, deploy, and troubleshoot some web applications.

Collaborated with cross-functional agile team of software engineers on the development, deployment, and troubleshooting 7+ web applications.

Responsible for prototyping UI animations, improving performance and stability of UI and JavaScript runtime.

Prototyped new UI animations, significantly improved performance and stability of UI and JavaScript runtime.

Used Bootstrap, HTML, CSS, JavaScript, and jQuery to build a mobile-friendly website for Khan Academy.

Built a fully functional mobile-friendly website for Khan Academy using HTML, CSS, and JavaScript.

Helped convert front-end from ERB files to React framework.

Converted front end from ERB files to React framework in joint collaboration with X.

Building a mobile version of the sales reporting application using X, Y, and Z.

Independently built/developed a mobile version of the sales reporting app using X, Y, and Z.

Created a new client CSS branding file using Less.

Coded a new client CSS branding file using Less, resulting in a 70% reduction in file size and 2x less time to brand a site.

Now, try to improve yours! Here’s a quick how-to guide for you:

  • If you haven’t already, describe your experiences in bullet-point form.
  • Start out all your bullet points with strong action verbs. Make sure to vary these verbs so you don’t sound repetitive.
  • When describing the roles/projects that have already ended, use action verbs in the past tense.
  • Quantify your accomplishments, as much as possible.

If you’re an IT student, be sure to share this link with your bootcamp/career coaches to get access to CV Compiler’s resume and job search toolkit for young professionals in tech. Over 500 bootcamp students and recent graduates have already benefited from using it.

Top comments (11)

zsoltime profile image
Zsolt Meszaros

Some solid advice, Andrew 😉 What do you think, would exact numbers work better than round ones? I mean, instead of "Reduced 30% of the page load time" we could use "Reduced 31.6% of the page load time".

On sales pages, these numbers perform better as they appear more credible. Not sure if it's the same on CVs though 🤓

stetsenko_me profile image
Andrew Stetsenko

Thanks a lot for the question! I'd use round ones on a resume, since they are easier to read.

thatonejakeb profile image
Jacob Baker

Seems that quantifying the value and showing the added benefit is the way to go. Completely agree!

stetsenko_me profile image
Andrew Stetsenko


weeb profile image
Patrik Kiss • Edited

So basically, not:

I am a good programmer


I am an extremely talented person, who uses his rare and well developed skills, to design and build fully functional websites with outstanding performance using XYZ technologies.

stetsenko_me profile image
Andrew Stetsenko • Edited

1) A good rule of thumb is to avoid using personal pronouns (especially "I") in a resume. Everything on your resume pertains to you...

2) Using adjectives like "talented," "outstanding," "rare," etc. also makes little sense. Any of us can add them to the resume, none of us would write: “I’m NOT talented...”

Strengthening experience descriptions is not about adding beautiful words and phrases. It's about showing potential employers that you can deliver results.

justinemmanuelmercado profile image
Justin Emmanuel Mercado

Is it normal to get the quantitative result of work you've done? It has never happened to me or the people who know have never told me about it. Maybe I'm working at the wrong jobs?

For people like me without any number to base our accomplishments on would you suggest just guessing or don't include numbers at all? Great advice overall 👍

boywithsilverwings profile image
Agney Menon

This is true, average companies and startups don't necessarily measure many of these figures. The only place I have used these mathematical terms is making a site faster.

notsag profile image
Maxime Gaston

Some good advice there, thanks.

I'm working on a project for developers who want to make resumes.
The idea is to create a yaml file which would be the content of your resume and can convert it to pdf using a desired template:

It's in a beta state for now, but feel free to have a look and contribute, give ideas or feedback, it's always appreciated.

anduser96 profile image
Andrei Gatej

Thanks for sharing!

Do you think contributing to the community can be on par with showing what you’ve had to deal with real-life situations(i.e the bullet points you’ve listed)?

By contributing I meant:

  • contributing to an open source project
  • being active on Stack Overflow
  • exploring the source code of a technology(framework) and sharing the findings in an article

Thank you!

loujaybee profile image
Lou (🚀 Open Up The Cloud ☁️)

Great article Andrew. It's always important to showcase those tangible outcomes!