Full Stack Developer with 3YOE

[sinful marsh]

Any thoughts on my resume? Are 3 lines too long for some of the bulletpoints? Do the projects sound too trivial (you can be completely honest)? Are there not enough business metrics/numbers?

[chrome lava]

can drop the udacity nano degree, those dont really hold much weight and you have experience anyways with a CS degree

the main thing i have is that the resume is very wall-of-text esque. I would consider trying to add some vertical whitespace in between bullet points so it doesnt just look like a wall of text

can reduce size of ur header to help with the above

looks like some of your bullet points end in a period, while others dont. would make it consistent

“contributed to UI features…” ehhhh kind of vague, i think it could be improved by maybe emphasizing 1-2 contributions u made and making them their own bullet that outlines their own impact

i think maybe doing “1.5 minutes to 2 seconds” could MAYBE be read better by adding the percent instead ? “reducing response times by 99%” or something but not a big deal either way, up to you ultimately

[sinful marsh]

For the UI features they were kind of trivial, like adding CRUD webpages and features, realigning some elements, and fixing some minor bugs, but I completed numerous of them and created like 70% of my team's total PR's. i was also really proactive at finding bugs and fixing them, even when there was no backlogs. was looking for any improvements possible to the codebase, and testing the webpages and query performance constantly

not sure how to phrase it to sound more complex/impressive

[sinful marsh]

Here is my updated resume, hopefully it is more readable now. Still kind of undecided on how to split up that UI features bulletpoint. The UI work i did was pretty trivial impact wise, just making bug fixes, enhancements, and creating CRUD webpages so not sure to include those specifics or not

[radiant socket]

IMO your Technologies/Tools/Frameworks is too big. Are you really an expert at "Open AI", "Postman", and "Crontab"? Maybe you are! Idk! But I don't think anyone will look at your resume and say "oh wow this person knows crontab? THAT is what we want." You want every part of your resume to be very clear about what you bring to the table. You bring React, Flask/python libs, and databases. That's a very useful set of skills and I think you need to make it really clear at first glance that's what you bring.

You have so many bullet points. This is just a brainstorm but can you combine some of them into a more cohesive story? For example, I see 2 bullet points about improving DB queries (point 1) and refactor for maintainability (point 8). Can you combine this into a story about improving the product as a whole? Did you use monitoring to determine what to optimize? Did you talk to customers to get a feel for what the pain points were? Can you rewrite this portion of your resume to show that you did a whollistic approach to performance improvements and in order to achieve that goal you dove into a bunch of parts of the stack (including the DB queries and the angular modules) to make sure the product was rock solid?

[sinful marsh]

Thanks for the valuable feedback. Point 1 and point 8 were from different projects actually. For the DB queries (point 1), that was for the search feature in the monitoring tool itself, not the apps that are being monitored by the tool. Point 8 was for a completely separate project. Points 1-7 are about a monitoring tool

The monitoring tool was used for the clients/customers, and its purpose is to reduce manual inspection of the logs and check for any chokepoints or which part of the application's code was causing performance issues.

I believe the client wanted to see any areas of the application that were causing performance issues, thats why we displayed stack traces along with how long each stack trace was running, so that we can see how each line of code is performing in an app .

Maybe points 2-5 can be combined since they're all somewhat related. I was also looking at other people's resumes and they have a bunch of different features in their bulletpoints as well, and they all seem to not have a cohesive story. Is there a concern if i consolidate my resume too much that I might be missing some keywords, experience, or it wont be enough content to fit into 1 page?

[radiant socket]

in order of importance, it is more important that people glance at your resume and see why you're good. it is less important to explain everything you did.

For reference, no one asked me one single question about any bullet point on my resume during my entire amazon and meta loop.

These bullet points get your foot in the door

[sinful marsh]

Do you think small to mid sized companies will ask about your bulletpoints? From the few I've had with them they asked about my resume bulletpoints in detail.

Is it worth having 2 separate reusmes? 1 for big tech companies (with consolidated bulletpoints), and the other (explaining everything I did) for startups and small/mid sized companies?

Or should I just use the consolidated resume for all companies?

Also not too sure how to consolidate/reduce my bulletpoints without taking out too many keywords from ATS or making the consolidated bulletpoint too long, but I guess thats something I'll play around with

[radiant socket]

I'm telling you I think you should cut the bullet points.