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:
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