Hmm, looks alright to me. If I'm being nitpicky, maybe more metrics and formality in your bullet points?
#My resume must be shit lol
rich belfry
for example, "making things like Amazon's ..."
"Wrote software responsible..." is kinda vague. You should specify the type of software (pipeline script, executable, cron job, etc.) that you implemented.
fossil needle
yeah, you gotta specify what you did, and not necessarily what your team did
recruiters will be able to tell the difference, and right now it looks like you did nothing but write tests
fossil needle
give background on my team (bullet 2) -> explain project (bullet 3)
^ I wouldn't even bother dedicating an entire bullet point to these two
like I would just fit those into the 2nd half of this bullet:
add things I did during project
and I think that like... you want to really say to the recruiter "hey, I did a lot", so it's better to break your single bullet point that explains your project (that is really a combination of many smaller tasks) into multiple bullets that each describe a unique task that you worked on to improve your team's overall objective
like make 1 project sound like multiple
kindred spindle
A lot of people are working at Amazon now so prob not as impactful as you're competing with more and more people who also worked at amazon
Your projects overall are okay but they don't have too much focus, I would try to focus on which area of the stack you want to work in for example backend
or full stack
overall your projects are pretty simple and they don't stand out to me
I would incorporate more enterprise tools
valid hazel