#Need some resume roast and feedbacks ๐ (new grad)
1 messages ยท Page 1 of 1 (latest)
skills at the bottom
remove some less relevant projects to make room for more descriptions
recruiters are expecting more than just what it is
@ruby elk I updated some, feel free to roast me
i'm not going to go into content but
I'd unbolden the dates, they stand out enough as is
and then bolden the technologies+languages you used within descriptions
I at least avoid just dumping all languages+technologies I used in lists (that's what the skills section is for)
I weave them all into my descriptions
@ruby elk thanks, and do you mean that I dumped all the relative tech stacks in the projects section?
yeah, not a huge problem
but I don't think dumping a list of tech stack is that helpful
I think you are right, I can just bolden tech stacks in the description
again thanks for the feedback
I'll prob work on my resume for a bit
Bump!
Need some resume roast and feedbacks ๐ (new grad)
(Sobbing silently) ๐ฅฒ bump for feedbacks !
Dang I thought their logo is not capitalized
Well actually it is, around 912 smth. internal tool at Apple across the globe
Or should I trim it down?
Oof official docs uses capitalized name apart from logo . Gotta fix it. Thanks! @spare estuary
Re: whether to mention the 912 teams metric - depends how attributable the entire tool is to you. If you own the tool (i.e. responsible for design and maintenance), might make sense to say that. Otherwise it is like saying I committed code to Facebook app which has 4 billion MAU
So basically, I had an access to the entire project, and was working on feature implementation, debugging , and PoC test involving multiple meetings with different orgs (iOS, MacOS, WatchOS, global chain, design, marketing and more etc)
Would it be better to just say 'hundreds' instead of 'over 900'?
If you are staff engineer, that figure might not be sus. If you are a new grad or junior, that figure is sus. My opinion