#Need Help Improving Resume Readability (NEW GRAD SWE)

1 messages · Page 1 of 1 (latest)

ripe garden
#

@rich vault hey you mentioned earlier in a different thread the importance of readability over technical depth. If you're free, could you give some advice on what I should cut down on and how to make this more readable? any advice is appreciated, ty

glossy dune
#

read these b4 ping

ripe garden
sand river
#

I’d say 1.5 is fine, but yeah the more of the second line you take up the better

#

I swear I saw this before and there was a whole discussion about sdet pigeonholing your job opportunities maybe im bugging

#

But didn’t you have more exp before?

ripe garden
#

i prioritized readability and getting the idea across efficiently over cramming info but yea i might expand a little on some bullets

ripe garden
# sand river But didn’t you have more exp before?

the content is the same, i made the bullets shorter in this version but people told me it is still too technical and not readable so i uploaded it again asking how to cut down jargon and make it more readable because i don’t have a good eye for resumes

sand river
#

For one thing, don’t have bullets re-listing all the tech you used. The tools are a means to an end, the recruiter doesn’t care

#

Especially when you list them next to the company name already

#

Bullet three for first project isn’t much value

#

Make it english so they understand what you did, now what you used

#

Also general content wise, I’d consider open source, it’ll do more for your job chances than low visibility personal projects

#

Unless you want to basically address a problem and try to make a product/service

rich vault
#

like every time uh ave a word in ur resume u should ask does this genuinely contribute to the user's opinion as much as i think it does

#

like

#

project 1 line 2

#

Built a GraphQL API (Aollo/Prisma/Postgres) with codegen types, cursor pagination, and data batching, cutting round-trips 38%

#

a few things i removed

#

"typesafe" cus who cares, u can say this in an interview. is it that important they know its typesafe? dont forget you are trading off how easy it is for them to understadn this linem which is the highest priority imo. changed Apollo/Prisma on Postgres to Apollo/Prisma/Postgres , anyone who understands what youre saying will understand this the same. i reduced dataloader -> data cus it seems like a fine swap but if its not feel free to undo. i removed N + 1 queries because genuinely dont care about that level of detail, also removed speeding feeds 1.6x because it felt like just too manyu metrics shoved in

#

i value formatting and readability way more than getting every inch of detail across

#

the way i see it you convince the human to interview you by having a resuume that appeals to them (readable, looks nice, not filled with technical jargon) and then you can explain further in an interview, where they'll actually give a fuck

ripe garden
ripe garden
#

do these look better?

barren zodiac
#

don’t use gpt 5. the semi colons are overused

#

also too much bolding that doesn’t even matter

barren zodiac
oak crater
#

I would say the tech skills sections needs to be at the top - after education, that way recruiters can see it quickly