#New grad resume, update after low response rate

1 messages · Page 1 of 1 (latest)

teal spruce
#

looks ok now

bleak kernel
#

New grad resume, update after low response rate

mental wadi
#

oh here it is

#

I'll look through it in an hour I'm running some errands

#

Wdym by implemented ann instead of lstm. lstm is ann. why does reduced training time matter. that's cool that you at the very least compared some models. if you want a stronger point, do hyperparameter optimization. did you try against any classical models, how does naive bayes perform

#

ok i gotta run though I'll read more later

mental wadi
#

Yea I mean generally deep learning models are expensive, and if you can get away with something less complicated that does the deed theres no reason not to

mental wadi
#

It's not that big of a deal. Anyway overall it looks alright. generally i believe in single line bullet points whenever possible

#

If a line loops over by a small amount like the ci/cd point, rewrite it to fit in one row

#

Similarly in Bosch, make that three bullet points total. idc how

#

Well i do care, theres a general guideline of "achieved X using Y resulting in Z" which is kinda hard to do sometimes but it's a guiding model

#

with this guide in mind, we can sort of assess how strongly your points come across

#

Nvidia 3rd point: 3.5/5. X is the pipelines being built, docker and Jenkins is Y, and Z is the time saved

#

Y is fine, Z is great, but X could sound better if you rewrote "... that go hand in hand with trunk-based development"

#

if the grammar doesnt fit nice for what you wanna express, remember that english is flexible and as long as you convey the same meaning in a not too contrived way you're free to permute XYZ

#

let's check another bullet point to see how it performs

#

2nd nvidia point: X is "designed and implemented.... to categorize/troubleshoot"

#

Moreso the latter part

#

Y is i guess nlp models using pandas and spacy

#

Z is the metrics, the numbers

#

Observe that X doesnt sound like an achievement

#

You can go through each bullet point with this rubric and make the decision whether to modify the wording

#

Again it's just like minor stuff. But a lot of small things can add up. im just being super critical, up to you whether many of these are worth implementing

#

one of my profs in undergrad, he would give unreal amounts of feedback on assignments. fully scrutinize every little detail. we would say they were covered in blood, with how many red markings were on top. Even if you got 100% he always had something to say. i guess some of that has rubbed off on me

#

the first nvidia point is good

#

The second point in virtual pager is secretly two bullet points

#

ok I'll stop

mental wadi
#

ill look at it later if i have time, quite busy

dim lantern
#

Did u not get a return offer from Nvidia?

mental wadi
#

I'll be home in 10 mins

#

then I'll be free for 30 mins or so

#

@bleak kernel i am at home

#

you should add a line to each of your experiences/projects for the tech stack

#

basically just list off every bolded keyword (that isnt a result)

#

nvidia
software engineer intern
technologies: python, pandas, spacy, docker, jenkins

  • created...
  • designed...
  • built...

instagram clone
technologies: python, flask, mysql, css, javascript, react, bash
-...
-...
-...

#

no

#

you should keep your bullet points as is

#

and add an additional line for the tech stack

#

the bullet points on your resume are a tldr of what you did

#

the tech stack line is a tldr of your tldr

#

i mean you should literally do nothing to your bullet points

#

the bolding in them is fine and good

#

just that in the new line, you dont need to bold them again

#

if it is, remove your least impressive project

#

you worked at nvidia and bosch

#

its fine

#

of course you should

#

its work experience

#

each work experience is worth more than a project

#

for sure you should remove projects before work experience

#

if you need the space

#

that works too

#

thats what i do on my resume

#

well i just do instgram clone | python, flask, ...

#

since the word technologies takes too much space

#

the one with the least keywords

#

well. i have no idea anything about c++

#

it might be cool

#

as far as stuff i know about, the fake news classifier is the weakest

#

but who knows maybe the person looking at your resume is clueless

#

and only knows how to look at bolded words

#

the tech stack line i think is reasonably important though cuz it basically doubles the number of keywords in your resume for free

#

idk i mean it sounds cool to me. but i wouldnt know

#

i may sound like an expert but idk what im doing either, my expertise is in sounding good on resumes

#

i have a math degree and like 3 months of coding experience

#

you can put your resume into various job sites that let you attach one

#

and see how well it picks up your stuff

#

ATS parsing, etc