#Can't get a single interview || More than 500 Apps
1 messages · Page 1 of 1 (latest)
bruh U had an amazon internship and can't get interviews? no wonder I can't get interviews either. My resume is nowhere near as good as yours, and if you're not having any luck I'm screwed đ
It's a full time role worked for a year, No one is giving shit because am trying to move to software or data engineer and it was a support role
the resume looks solid to me
unless u r international, u prob get some callbacks when the market swings back
I'm an international unfortunately
oh maybe thatâs why then
tough market for domestics, even harder for internationals :/
and about the resume, just my opinion, u can place the skills section below the education
I did migrated some of my projects to get cloud to get experience and tinkered with AWS S3 storage and ec2 just to get some experience and add some keywords
Ohh gotcha, but I was like everyone goes for the experience
maybe rephrase some of wordings with buzz words
its like half and half
some recruiters I met said, they look for the skills first to see if the candidate is qualified or not
since they just skim through the resume
ohh gotcha
also, u can place name of the company above the role since itâs the highlight u know
the word Amazon comes before the role would give better exposure
I mean role is just a role
So what exactly is a "data support engineer"??
I donât think you donât have to blur the role
instead blur the big names
lowkey recruiters r superficial mofos so they donât really read what role u had rather where u worked ig
u remember that fake resume?
Basically same work as data engineer but instead of multiple point of contact and huge responsibilities we tend to work on only single process and work with Business intelligence engineers
but yeah these r just my small feedbacks , I hope u find a good position soon!
gl mate
Ohh cool, never though like that
Yea but in that it was role was highlighted
I was under the impression that role matters a lot (more than the work place)
I think recruiters r just hr they canât tell the difference between the roles u have on your resume ngl
ohh than they go by whatever they see
Some bullet points are nice, some bullet points are weak, and the sentence structure is not consistent, and you have some silly mistakes... makes the thing hard to read
can you please help me out by pointing out some ? or should I rewrite again all the things ?
First of all your titles:
Change it to:
- Graduate Research Assistant
- Data Scientist or Data Engineer
Change "academic exp" to "Projects"
- Sentimental analysis should be "sentiment analysis ML model", needs to be a bit more descriptive
- Cloud web interface? What did the app do exactly?
- Remove the ":" from those titles
Skills are fine but HTML and Javascript are languages not web technologies
oh you weren't a graduate TA, you were a research assistant
LOL
Yeah just call it Data Engineer
ohh that cloud web part was a automotive car inventory management one
tried to implement end to end application for the automobile inventory
yeah then the title should be "cloud inventory app" or somrthing
OK so your bullet points are so weak lol... read this outloud:
"analyzed hadoop and increased user threshold by 30% so more people can use it"
It sounds like you just went in the menu and flipped it to 30% more
But I think you should highlight the analysis that led you to that conclusion?
And then, a bullet point that you installed software? Literally anyone can install software... that bullet point is such a mess... what part of it are you trying to highlight?
Basically what I did is that analyzed the mapreduce and yarn distribution of resources on the hadoop cluster, changed the resource allocation which helped in that
Ok I just realized what I wanted to say and the sounding is totally different
OK I recommend you rewrite your bullet points... focus on the idea your trying to communicate, and use Google's bullet point format
âAccomplished [X] as measured by [Y], by doing [Z].â
for example
I like to flip the format around personally
so I would say:
Migrated refund functionality to Stripe API using Ruby on Rails, reducing refund processing times by 21%
you say your technical achievement, what tech/language you used, and the metric if there's one
very straight to the point
make sense, let me flip the points
@agile knoll changed the part GRA part, please help me review it
Also let me know what other changes I need to make, is the other's are also bad? and rewrite it?
there's so much stuff I have to write but can't decide on which i need to focus on
The experience looks much better
I still don't know what "analyzed and traced down this and that" really means... maybe it's enough to say analyzed
and implement my recommendations for the project section as well