#New Grad 2024, getting 0 callbacks, OA's. Is my resume that Bad

1 messages · Page 1 of 1 (latest)

violet viper
#

Looks like there’s lots of fluff and that you may not know what you’re talking about to me

dire raft
#

^ your description doesnt really say anything about what the project does and impact it has - probably need to rephrase most bullets

tall viper
#

Noted should i keep my server assembler job in resume or remove it?

#

a or any advice on what i can do to get better chance in this market?🙏

sand granite
#

Resume has stuff like "quantifiable metrics" and "Testing and training dataset", stuff only a novice would write in an ML resume. Stalk MLEs on linkedin and copy their resume style

tall viper
#

Looks like my bullet points are way too wrongly set up.

vestal drum
#

Also i think your a bit too wordy imo

#

lots of adjectives and qualifying statements that makes your bulletpoints kind of hard to scan

#

But i think hopefully my guide helps b/c i think u fall into one the categories that i point out as "common mistakes"

#

Feel free to reping me if u want me to take a look, but i think everyone else is already accurate enough on its too fluff

tall viper
#

Thanks alot, do you recommend me to make more projects or these are enough for entry level. i mean market is 🫣

vestal drum
#

@tall viper I think what you have is enough. The recruiters / interviewers will not care too much if u go any further / I do think there is only so much you can cram rn.

I do recommend to keep learning for the sake of learning, and always expand expertise, cause u'll just sound better if ever asked

#

but the resume is just a foot in the door, to do leetcode tbh

#

with only a smaller subset of companies really drilling down into any practical experience

#

(which is why can be helpful to keep learning on the side) but tbh, there just tons of ppl who only know leetcode at first.

#

the way i tell my mentees is:

  1. Learn leetcode to get the job
  2. Learn practical skills to keep the job