#Would appreciate any feedback? Looking for new-grad roles - SWE

1 messages · Page 1 of 1 (latest)

fast robin
quasi mason
#

no need to blur out education i know what school you go to from that first project

#

having full time positions before youve graduated is a bit susipicious, seems falsified

#

technical skills at bottom

#

this seems a bit gptd

#

like why are you spearheading development instead of just developing

fast robin
quasi mason
#

eh

#

maybe you just put intern

#

sorry for not conitnuning im just kinda having a hard time reading this

#

i usually like to skim first but i needa read line by line for urs

fast robin
quasi mason
#

haha

fast robin
#

tytyt

quasi mason
#

🥺 sry

#

like maybe im just stupid

#

but like idont know what telemtry is

#

or rf based digital twins

#

like the first bullet is prob fine

#

yeah ur first bullet is fine im just not familiar with this work

fast robin
#

Makes sense, yeah the project is like using data from Wifi APIs (Cisco Meraki, Aruba, etc.) to gauge location based topography and visualize it in 3d, something along these lines. I will simplify it a bit.

quasi mason
#

yeah simplifying it would be nice, when i skim it i kinda just skip over that stuff

#

maybe someone else would disagree but i think you should just stick to x y z format, made x using y resulting in z

#

like thats just how im used to reading things so its easy for me

#

but you have it as like z x y

#

or like x z y

#

but i feel it is much clearer if you just stick to

#

i made this using this, for this reason / resulting in this

fast robin
#

xyz, got it that makes sense

quasi mason
#

that way if they ahve no clue what youre talking about when you say how you made it, they at least know that x feature correlated to z result

#

and can just skim over the y

fast robin
quasi mason
#

it is but

#

like dont use spearheaded

#

cause you want to be clear

#

its not really relevant or not if you spearheaded it

#

again for the ta

#

like it does not exactly matter that you were selected

#

the work you did was jsut evaluating projects

#

just focus on your work and let it speak for itself

#

you dont need to fluff up things

#

also youre mixing around your order of xyz

fast robin
#

makes sense, yeah but I was like recommended to be a grader by my old prof, and it's not really common at my uni to be undergrad reader, but I get what you're saying, need to convey it better.

quasi mason
#

like for the third one its z y x, then second bullet is x y z

quasi mason
#

like its obviosuly a good thing

#

but im not sure if it means anything to recruiters

#

it may but thats up to you

#

but focusing on like a selection process rather than the work youve done often shows to me that what you did is not signifigant enough so you have to add on to it

#

ive seen some other people put selected for fellowships or programs alot

fast robin
#

makes sense I will try to convey it better and focus more on MY WORK, thoughts on projects? I am planning on starting my next project, so would love to get feedback.

quasi mason
#

dont call your first project fablix

#

like if you are a recruiter looking at apps from the same school

#

and you see 2 guys have the same project its a bad look

fast robin
#

yea ez dox

quasi mason
#

not really dox

#

but more just like once you realize its a class project it takes alot of the merit away i feel

fast robin
#

fair

quasi mason
#

plus less unique

#

makes your resume stand out less

fast robin
#

Got it

quasi mason
#

bullets for fabflix are fine

#

for projects i like to do first bullet general overview

#

into rest bullets are descriptions of technical stuff

fast robin
#

makes sense, I will try that.

quasi mason
#

hmm

#

streamlined backend logic

#

through jsut parsing data?

#

like usually

#

your first bullet is just made x project for y reason supporting z users

#

then next you would talk about how you implemented website functionality using serverlets and whatnot

#

then talk about cloud hosting and scalability in the next one

#

then talk about db scaling in another bullet

#

you see what im saying

#

seperate so its clear

fast robin
#

YEAH, I DO, I feel like I just put a lot of information on a paper and let the recruiter decode it

quasi mason
#

this is a good example i liekd this one

fast robin
#

ugh

quasi mason
#

you see hwo their projects are very simple

#

ver clear what it was for, what they did technicall and what the impact was

quasi mason
#

cause if they have to look through hundreds

#

they will just skim

fast robin
#

yeah, for sure

quasi mason
#

so impress them quick

fast robin
quasi mason
#

wdym

fast robin
#

like this resume review post, cause I just applied for 20-30 positions in the last 2 days

#

lool

quasi mason
#

its ok 20-30 not alot

#

once you fix up and apply to a few hundred you should be fine

fast robin
#

I will make it better and get back here! Manifesting amazon for you!

quasi mason
#

haha ty

fast robin
#

TY!

quasi mason
#

last note

#

projects usually whatever

#

only real way they stand out is like if it has real world signifigance / lots of people use it

#

so focus more on making your experience as good as possible

#

like i would not try to start a new project to make yours more impressive, pretty sure recruiters only care about exp

#

so just sell your exp as well as you can

fast robin
#

Makes sense, IMPACT. Got it, I will revise this and post again. Thank you sm!

quasi mason
#

well impact but also just making it clear what you worked on

#

but yeah np

fast robin
#

tyty

fast robin
quasi mason
#

Just put cumulative

#

I think if they background check you that’s what’ll show up on your transcript

#

3.5 good enough anyway

fast robin
#

cool

paper bronze