#PLS HELP, no callbacks! T5 @ Amazon, incoming AMD

1 messages · Page 1 of 1 (latest)

old bough
#

T5 @ Amazon, incoming AMD, no callbacks

old bough
#

PLS HELP, no callbacks! T5 @ Amazon, incoming AMD

silver bane
#

Right off the bat, my critique is that its way too wordy. too many words on the page. I don't understand the skills concepts section remove that

we know you have actual ability bc you already have several experiences we don't need a breakdown of things you know. also its assumed you can pick up anything when you have the experience you have and even just a good school

you descriptions need to be plain english with the specific technology removed. If a general person is reading it, they don't need to know the specific service to understand it. for example on capital one, dynamodb, say database. Then what i personally recommend is doing a bold technologies at the end of the experience and listing off everything. The readers shouldn't need to know which is what.

also when you think of descriptions, think of bigger code commits you made and what they did. some of you bullets feel way too general for me. the metric stuff is good

#

also 5 projects feels way too many, you already have good names and experience. i would include the top most impactful like limit to 2

#

take the last two bullets listed for the last lis experience,

the first one, too much mention of technologies that i can't read it right off the bat and decipher what you did.

the second one, you talk about testing, the wording is too wordy just say you improved testing or made it more robust by including mock testing, integration (idk what the other testing are hitting, but if it actually acceses one of the dev, prod ) or something

mint merlin
#

theres no such thing as "Too many" projects

#

why would there be?

#

if youre looking for research positions, theres definitely an argument to expand on them

#

but projects will never be as valuable as experience just bc of credibility differences?

#

to make the changes youre suggesting youd have to take away from exp and shift the space allocation to projects

#

i will sya this advice is not blanket statement

#

u should take away from projects as necessary to give space to experience

#

you shouldnt be AIMING for 1 line projects, its just the way you fit in more projects if your experience section leaves little room

#

not sure how you went about making the res so i just wanted to give that context

#

👍

#

one thing i will say is concepts section seems a bit hefty / zoomed in

#

i know what its for, im the person who introduced it to the cscd

silver bane
mint merlin
#

you can make the argument that you should have BETTER projects because you dont have enough that are worth talking about and sure, i agree a dbms is probably one of the most basic projects ever

silver bane
#

the goal is to showcase you can be successful at job and pick up a variety of technologies and some jobs want to see you have worked with a technology they are looking for and have mastery of it, why do they care about interest or curiosity

mint merlin
#

they dont just care about your skills , and why would a project show mastery?

#

you think that devs who work with a lang on prod level code for 8 hours a day have the same mastery as someone who built a dbms in java?

#

projects were never to show mastery

#

no company is going to look at a project in an area that a candidate has little to no experience and say "well they dont have experience in the language we need but they did say they built this project in an afternoon in java, lgtm!"

#

obv hyperbole but just to make the point

#

let me look

silver bane
# mint merlin they dont just care about your skills , and why would a project show mastery?

if you showcase something super involved, like for example a project i built for a class is mini facebook and you have to implement all parts. that would show you can fully develop a full stack app back to front and figure out configuring a cloud services, include security etc. You would be hired if they are looking for potential backend engineer and you are working on webapp that does the same stuff

mint merlin
#

that will always be the case

#

building facebook in class to be used by no one will never >> or even == someone who worked in backend in their experiences

#

and the reailty is there will always be a candidate with a better skillset than you for the job

silver bane
#

i feel like we are back to my point that if you have experinces, you don't need projects that don't display some other skill

mint merlin
#

not really

#

im arguing that projects dont display skill at all

#

thats not your point?

#

your point is display a different skill with projects, mine is that yours is moot because it doesnt express any production level skill at all

silver bane
#

so they are just there for show???

mint merlin
#

they are there to display curiosity and interest

And to fill the resume ! because new grads and students need some way to show technical involvement (not skill ! ) outside of experience they do not have

#

now we're back to my point 😄

mint merlin
#

anyways , i wont go in circles with you on this because there is no point, and the person who's resume this is will decide based on what makes more sense to them

#

i guess when i read the first line of amazon

silver bane
#

ok, i just assume if you are in the field you have interest lol. regardless, good to have anotehr perspective and critique to my feedback is good for athena

mint merlin
#

yah

#

better than one pov i agree asw

#

amazon is alright but it reads kind of awk on the first line concluding with through Full-stack development @old bough

#

my first question to that is like

#

okay but what exactly did you do to improve experience

#

yah i understand

#

but i think there are ways to be more descriptive

#

ill show u an example from my resume

#

where you dont get too technical but still explain well

#

heres my go to example

#

the first line still gives an accurate + informative description of what i did, but a non technical person can easily read it

#

even if they dont understand "microservice architecture" they still understand the line

#

i think its avoiadble by removing such detailed specifics (like team names, which wont be super important to ppl who are outside of amazon)

#

yeah i agree with that framework, but i still think its not detailed enough

#

first thing they read should be general overview of project

#

i think that overlaps with your definition

#

but i feel yours goes too quickly into qualifying it (200+ teams and the team names are your evidence, not your information) before you've fully explained what you did

#

you'll notice that my only statistic in my bullet is on the last line

#

after i spent 2 lines giving an accurate overview of what i actually did

#

yes exactly

#

and that canb e kind of hard so feel free to send me dms for thoughts n stuff

pine rampart
#

congrats on mit

bitter river
# mint merlin

"Engineered a service utilizing microservice architecture..." - why not just say you built a microservice lol

#

Wait this isn't part of your resume hold on

bitter river
#

My biggest advice stands - you need to apply early in this market, within the first 2-3 days if you can. The highest callback rates I've seen this year are those that just jump at the opportunity. I would not take your rejections as a sign that you're underqualified - if anything, you're prob in the top 0.5% of students searching rn

First things that stand out to me:

  • It's way too dense - yes, you want to seem involved and have impact but you want to communicate that succinctly and effectively bc nobody's really going to try to parse through all that
  • You have 5 lines of concepts despite having 4 prior internships - I think you can (imo should) cut this out entirely. You have keywords via your experiences/projects, and it adds no value at best
  • You can similarly cut coursework for the same reason
  • Putting a future internship is often advised against, so I would keep this to one line at most if you want to keep it
  • Your project titles can be more apparent, and your project bullets should be improved overall (e.g., wym by "Orchestrated a complex automated data pipeline, reducing data proprocessing time"?) - mostly, projects bullets should communicate 1) what the project is about and for, 2) the impact of the project (if it exists), and optionally 3) any technical considerations that someone would find interesting

My focus here would be making your impact more apparent - meaning give your resume breathing room, cut down on the BS and fat. You have a good number of bullets that span much longer than necessary (e.g., your last bullet in role 5 is literally just "Improved test coverage by 15% with Pytest"). I've seen people in this market who've gotten offers with citadel, roblox, databricks with resumes that half the size of yours, and with less/weaker experience.

Again, it doesn't mean you're less or less competent - rather, my point is more that this market is the toughest it's been. You can be confident with your experience and let it show for itself

#

Your bullets overall are otherwise good for the most part (save for the few fatty ones and the first one for the co-op), but I would try to revise your resume to cut the bigger things and iterate on the feedback you have from the people here. I'll try to go through the content more thoroughly if you can ping me then!

#

Btw a lot of these companies are also swamped with the sheer volume of resumes and having cut down some of their recruiting teams. Don't sweat it too much if you don't hear back - the microsoft university pipeline for ex got back to people after over a month+

#

I haven't heard/seen any evidence that referrals are super helpful in this market atm btw

#

My friend sent me a pic of her spreadsheet for c1 applicants, and almost every other applicant has a referral lol

#

Doesn't impact the resume scoring

#

No they're considered normally, it's just marked as a field

#

It's different company to company

#

Would people be interested? Yes. Would you be pushed through the pipeline? Idk - recruiting is very swamped rn

#

Why don't you go for startups/unicorns? Out of curiosity

#

The way I see it at least big tech has a lot worse predictability/growth in this market, but imo it's easier to able to land interviews if you tailor to strong unicorns (think Ramp, Loop) which are stable and good growth opportunities

#

Codesignal only gets you to the resume screen, and a lot of people have 600 gca's (it's easy to cheat it lol)

#

Ramp specifically is looking for someone who fits their tech profile so you need to tailor your resume to them if you want an interview

#

Ramp does manual resume reviews

#

I think your concepts section might've thrown off people