Resume review for swe roles please 👉👈 | cscareers.dev | Page 1

#

aight homie im procrasinating rn

#

so i'll try my best to help you cool

#

cook

#

i personally include relevant course work

#

for the first point of your job

#

i would include a small thing about the study

#

Developed react components for a user study testing reaction speeds for example

#

the last three points are a bit vauge tbh

#

i think if you included more specific goals / achievements, even if mundane it's better

#

because it's a bit...generic

#

if you add some context about the study and process it'ds be much better

#

b/c work is sometimes mundane

#

but it's important to contextualize your responsibilities and achievements

#

~

#

tbh you know it's an uphill battle rn with NG but you got this!

#

~

#

some people like the format of doing

#

Name | tech

#

i personally don't

#

(i'm of the opinion it throws off readability and ATS, but to each their own)

#

~

#

i see the issue

#

i think the issue with your bulletpoints is that you're writing as if someone knows what your project / job is abouyt

#

unfortunately that is not the case

#

your bulletpoints should have enough context

#

i dont have to look up your repo

#

or your company

#

"Designed a discord bot that plays Youtube Music in video calls using Discord.Py, Youtube API, and MongoDB"

#

or something like that

#

has more context than

#

"Developed commands for the bot using ..."

#

i get that you have

#

music recs and trivia

#

but

#

i think it's writing is a bit confusing in my opinion

#

"the bot" is the most pressing issue imo

#

if you know what i mean

#

~

#

"showcased adeptness in external APIs..."

#

this is a very confusing line

#

on one hand it could be describing the bot but idt it is

#

if it's describing you, i'd remove it

#

i dont think it's valuable to include that esp when it's a recrtuier reading it

#

they're basically looking for prospective people

#

it's what they want to see in your lines

#

not you explicitly saying it

#

~

#

for your userscript library, it's a cool project

#

the second and third line aren't very useful

#

while they're important

#

i personally dont like to include those lines

#

in favor of describing partricular

#

features you made

#

APIs you used

#

et cetra

#

i'd also rewrite the first line b/c userscript might not be something

#

a recruiter can understand

#

~

#

for the bog app

#

i wouldn't include the npm line

#

i just wouldnt

#

i'd also try be more

#

magical with the first line

#

give it more

#

zazz

#

and value

#

than

#

just a blog

#

~

#

also why is bait tracker below blog

#

your ordering should always be best to worst imo

#

but you have the

#

dates in

#

so i guess it'd be by time

#

(i personally dont include dates)

#

~

#

i'd rewrite the habit tracker first line to include the fact your writing a habit tracker

#

wait

#

why is the decont line about the fact you did it

#

and the first line saying

#

built a dynamic front end

#

it can't be that way

#

first line gottta include habit tracker

#

and then more details

#

yeah

#

that's all i got

#

you have good experience

#

you need to take this through a few more rewrites

#

you got this

#

❤️

#Resume review for swe roles please 👉👈