1+ year non internship experience. 2 internships.

[hot vessel]

if reviewers would kindly put their attention to the bullets i wrote rather than the format. Though do point out if the formatting is glaringly bad.

@nimble stream please forgive this direct ping but i noticed you leave thorough reviews. so if you don't mind 😉🙏

[dim silo]

maybe add a section for leadership experience or involvement

recruiters love to see stuff outside of technical career stuff as well

for example i have esports coach on my resume and its one of the first things i get asked about by HR

if you have something you did outside of school like piano teacher, you started a band, played in an esport etc, it looks cool when hr is doing there quick 1 minute scan

i would also add a concepts section under skills as well and just list a bunch of shit from the posting

it doesnt show you know the skill, but you are aware of the skill and how its applied, it alsol helps get past ATS

for example

i would also just put graduation date, and not when you started

you should also quantify your impact in bullets

for example:

i'm also not a fan of multi line bullets

i would shorten them with chatGPT

[dim silo]

for example all my bullets stick to one line

maybe keep bullets to 4 bullets per experience, 2-3 bullets per project and all one liners

and then i would add some involement/leadership experience section of some sort, like sign up for a free hackathon or something, you dont even need to compete, you just need proof you participated

in you skills section, list the skills that you are most comfortable with to least comfortable, if you are applying for front/backend, please list those skills first (e.g., typescript, javascript, etc.)

[nimble stream]

This isn't applicable for a full-time role. OP is a 2023 grad, and they will be expected to be a professional for roles they're applying to. They're not competing against students, but instead of the tens of thousands of laid of engineers in industry.

I would also recommend against concepts - it doesn't help for student resumes, and it definitely doesn't help for professionals. At this level, hiring managers and recruiters prefer to see the application of work and tech.

Multi-line bullets are also fine.

This biggest issue with the bullets in this resume is the lack of focus on the business. It's usually best to lead with your strongest impact unless you're targeting a specific need in a role (e.g., OAuth).

I think I would like to see you do a deeper dive on your work in your most recent role. My takeaways from what you wrote are:

• built a Helm unit testing framework (yes, it comes off like that)
• set up Grafana dashboards
• set up uptime monitoring

A non-technical recruiter won't even try to understand much here (so a suggestion would be to bold your tech used - which is generally most helpful).

The issue is similar for your remaining roles, I don't understand 1) what the business need for your work was or 2) the business outcomes of your work. I keep having to ask "for what?" to myself as I read your bullets.

Your projects also read a bit too detail-heavy - at this level, you should aim to talk more about what problems you're solving with your project, or what your major contribution is, or what the most interesting tech is.

Lmk if you have any questions about this here

[hot vessel]

that essentially is what I did. and here's what the impact of that is. I think you're suggesting i lead impact first?

without the helm-unit-test stuff people are merging in bad code left and right and catching it in production.

without the Grafana Dashboards leadership had to really on manual spreadsheet work and repeating that long workflow anytime they wanted to see AWS costs. The dashboards I worked on allow a live-ish (updates daily) view of our AWS spend with historical spend data. This also allows people to know where the spend is coming from and to what resources it's going to.

Prior to the uptime monitoring work we had nothing outside of the platform itself that monitored the platform. A year ago there was a huge outage (not immediately detected which led us to doing this work)