#Statistically impressive fail rate, please help (600 Apps, 3 OAs, 0 Interviews)

1 messages · Page 1 of 1 (latest)

jolly snow
#

Statistically impressive fail rate, please help (600 Apps, 3 OAs, 0 Interviews)

lone juniper
#

very vague statements, why does update speed matter(also start with moved from polling to to timer driven then explain how it improved)

#

Feel like you dont hit enough key words either

#

this is just words, tells me nothing useful

image.png
#

just my 2 cent ¯_(ツ)_/¯

jolly snow
jolly snow
#

I'm not sure how to add more keywords, I did my best to just accurately reflect what I've done so far but evidently it hasn't been passing ATS

lone juniper
#

Make projects with more diverse languages and libraries

jolly snow
#

Or something generally speaking more meaningful with more technologies

lone juniper
#

I will change resume depending on role I apply to

#

If the role asks for full stack, then yeah replace shell with full stack, if it is low level include shell

jolly snow
#

Makes sense. Like for firmware roles that's probably good to keep on there, full stack probably not so much

#

Yeah I get it

#

Thank you so much again bro

#

ur a real one

long gazelle
#

bullet points look good

#

but like Scratch said try to apply for roles or tailor your resume to roles that fit the type of SWE

#

it looks like you did a lot of scripting work in python, what was the framework for the internship? UI or just a backend service? was there cloud?

#

for the first one just put software engineer unless you are targeting systems roles as well

quiet abyss
#

i think your document margins are too small. 0.4 is the lowest you should go

jolly snow
jolly snow
#

I'll take all the help I can get, I appreciate everyone helping me

onyx ravine
#

agreed. too many words, not enough substance. Honestly, for OP, the less, the better

jolly snow
#

from what I understand the bullet points for the unpaid internship and the “team of engineers” on under my robotics club need work for sure