Please evaluate my resume

Hello everyone!

I just finished updating my resume and would be nice to have some reviews.
I have some experience as a manual tester but I’m currently looking for my first job as a front end developer while I’m still learning. Any suggestions or any job offers?

Thanks in advance,

1 Like

Hello @gabriel.n.acevedo, welcome to the freeCodeCamp forums!

Your resume has some rough edges that should be cleaned up:

  • Your Summary section has a typo with an extra , on the first line after the word “JavaScript”.
  • There seems to be an extra space after the word “Client”.
  • I’d also keep words such as “smoke testing”, “client” and “back-end systems” all lower case. Unless it’s an acronym (like “UAT”) uppercase it’s not needed.
  • Your start and end dates for the 2 jobs listed as experience are the same dates.

Your summary also might be too reserved, in regards to things like “learning how to think like a programmer”. A business would like to hire someone who can do the job, its understandable to always require some on-boarding/training/learning, but your resume is essentially cutting yourself off at the legs and saying your just “learning how to think” on how to do the job. This might kill your chances regardless of what else is on the resume.

I think one of the big things with your current resume is lack of projects or portfolio. If you’re aiming for a front-end engineering position, having some front-end things is essential to standing out. This could be replacing some of your experience section with specific projects and metrics/impact-numbers to help “sell” your current skills.

For example, how much impact/testing/analysis did you do in your testing engineer job? Providing hard numbers can help sell your impact in your old job.

For any resume the main goal is to lead to an interview, but alternatively for front-end devs you want your resume to lead to more “investigative work” into your other links provided, namely:

  • Github
  • LinkedIn

Unless you have significant experience listed on the resume, most resumes by themselves are not enough to get a job interview. So you’ll have to stick with “feeding” into the 2nd option, which is to focus on recruiters/hiring managers who are curious and end up looking into those 2 links.

Github usually is the area where you can stand out the most, as LinkedIn usually is more “fabricated”. Github also is very flexible, and doesn’t have the same limitations as a resume. If you want to get an interview without a strong resume you should have a strong Github.

Your github currently seems rather sparse, and generic. I’d suggest investing some time in “spicing it up” with specific projects you’re proud of, along with adding a profile README, and other bells and whistles. Having fancier well documented projects (add screenshots!) can help show off your skills, in place of raw experience listed on your resume.

There’s limited space on a resume to put hard solid reasons to get an interview, but your github has essentially limitless possibilities of what you can and do. So do invest into it.

As a front-end developer you should have a portfolio that can be added to your resume. This provides an “end user” perspective on the work you do, rather than the “engineer” perspective github usually offers. The goal being those 2 together can provide a full picture of what you can do and how you do it.

Without a portfolio a recruiter (who isn’t usually technical) wont know what you can produce, and thus ignore your resume and github even if they are curious as there isn’t a clear accessible path from resume → work.

Finally, the whole “name of the game” is to sell yourself. Job hunting is a skill in itself, you could be the greatest engineer in the world, and still struggle to get a job simply due to not being good at job hunting.

Understanding what you have “to sell” to employers to have them invest into you is the goal of your resume/github/linkedIn.

Your previous test engineer experience can be leveraged, along with any experience you’ve gained so far doing front-end work. Its harder to show off soft skills, like people skills, but that could also be leveraged and help “sell” yourself.

Good luck, keep learning keep building :+1:


You should try learning C and C++ to put make your resume better. C++ is in huge demand and freeCodeCamp does have a C++ course too!

If you learn C first (which freeCodeCamp also has a course for), you can learn C++ easier. The resume is generic, not the best nor the worst.

There are many, many, many developer careers that don’t use either of those. Almost all web dev jobs (what this guy does) do not use C or C++. If this guy is pursuing a degree in web dev, there are much, much, much more fruitful things to study. He was also asking for a resume review, not random suggestions for things to study.

There’s nothing wrong with C or C++, it just wasn’t the question he asked and wouldn’t be much use on his current career path.


Brad gave a good review.

I would just like to reiterate about the summary.

I think this is one of the most important things on your resume, especially since you don’t have your job title as a subtitle. The summary is what they are going to look at first and in the 5 seconds the HR drone will have to decide into which pile to put your resume, it will have the most weight. They don’t care about what you aspire to. They care what are. What can you do and what type of position are you looking for. The HR drone wants to see that so they can decide.

They don’t care about your bartending experience. It wasn’t some major career and it has nothing to do with dev work, so just leave it off. They don’t care. I would much rather you have a section talking about things you’ve built.

Which brings us to portfolio. Definitely portfolio.

Don’t list “VisualStudio” as a skill. That would be like carpenter listing “Black and Decker Hammer” as a skill. Everyone uses a code editor and they don’t care which one you use. Even if they do, they know it will take you 15 minutes to make the switch.

1 Like

Get rid of the bartender bit entirely, it’s not the relevant to the job and you could fill that space with more job relevant information/projects

You don’t need to worry about explaining a ‘job gap’ on your cv, I’ve never been questioned about anything I did outside development in an interview

How do you think, guys, how much attention does an HR-specialist pay to the visual part of a CV?

It’s the first thing they see. It’s not the only thing they care about, but it does affect them, even on a subconcious level. There is a reason why chefs spend so much time making food look good - they know it affects how people perceive it.

This post was flagged by the community and is temporarily hidden.

1 Like

This reply probably comes too late, but just in case you haven’t seen it by now: there’s also a typo in your languages section (English).