Targeting entry level roles. Please help review my resume.

[languid sluice]

Double check your consistency in bolding key words and metrics. Some points have bolding but others don't.

Also, I'd be interested to know what others think about putting the points of normalizing and the number of tables and views created. I've designed a database as well but I didn't mention those things, so if it's considered a good and impactful point, then you can definitely keep it in

Otherwise it looks good to me

[thorny canyon]

Thanks!
Was on the fence about the Database thing.. Will look into it again.

[lofty lava]

i would reduce the amount in which ur bolding

u dont need to bold aggregate and analyze, “website using …”

“ultra low latency”

etc

[languid sluice]

You should ideally bold metrics and keywords related to your skills

Take a look at the way you did it with your second experience. Other than the first and third points which should be revised with where the bolding was applied, you did bold the right words and skills with the other points.

[fading flame]

This is really solid overall, good job. Seriously.

Tiny notes:

• Did your C++ work ever utilize Boost? If so, definitely mention it.
• "driving weekly developer time savings"... using the word "drive" to describe a discrete time savings is odd; drive usually refers to guiding some project through time (decision making, leading others, etc.). 'resulting in' would be sufficient here
• You list 'AWS' in the tools - particular services may be worth noting as well (similar to your breakdown of SQL)
• Someone in this thread brought up the database architecture point... the schema normalization detail is worth it only if you want to do more of that work in the future. If not, you could include more technical details of the fullstack internal web tool.

[languid sluice]

Yes. I mentioned the database architecture point.
Part of the reason is because I've done database work as well and it was a pretty significant chunk of what I did.
Since I am targeting backend positions (java mainly), do you think it's worth mentioning extra details about the database? I already have some stuff about migrations, but does adding normalization and the number of tables add value to the point?

@thorny canyon , what kind of positions are you targeting?

[thorny canyon]

Thanks for the detailed feedback.
Yeah, Ive used Boost quite a bit. Will add it to my resume.
I'll change the wordings for the driving part and add AWS details.
Will look into adding more details about the fullstack part.

[thorny canyon]

Hey, I'm mostly targeting backend SDE positions or some positions involving C++ since I've worked on it a bit

[fading flame]

If you specifically want to do database work, sure, mention that. If you want to highlight optimization of database tables, I'd describe the before and after in a way that illuminates the change. No one will really grasp what "30 tables" means at a singular point in time. Or maybe some might, but I'd imagine those are IT places or DBAs etc.