#Resume Review 2+ YoE - Got 3 interviews, 2 rejections from them. close to 350+ applications

6 messages · Page 1 of 1 (latest)

hollow aurora
#

2 +YoE currently doing grad studies, working on 2 research papers in AI/ML, good uni in Canada, looking for co-op.

resume.png
#

Resume Review 2+ YoE - Got 3 interviews, 2 rejections from them. close to 350+ applications

strong surge
#

I'll check this in the morning, but some quick stuff first:

  • Remove your technical lead and hackathon because it was so long ago, you have actual work experience now, and it's literally only one bullet point
  • Don't bold keywords, it's honestly a pain to read and you don't want to make your recruiter / HM feel like you're spoon feeding them like children
  • Technical skills should go way at the bottom, also remove the nonsense "Troubleshooting" - also keep in mind that anything you put there is fair game for interview questions, so don't stuff it with stuff you barely know.
  • You don't need metrics for absolutely everything, honestly I think the R=Results could also mean impact, i.e. what is the fundamental impact of your work on the overall project / team / company?
  • Building on above, you have some nonsense metrics which should be removed - for instance, "5 teams" shouldn't be bolded as a metric (and imo it should be "five"), and I don't think reliability necessarily needs percentages either.
  • You don't need to cram your entire resume with keywords, seriously. It doesn't matter that much. You don't need to put Git on one of your projects because it's assumed you're using a SCM anyway, and "REST API" should be obvious as well.
hollow aurora
#

Thanks for the suggestions!

hollow aurora
#

can I highlight the quantifying numbers? or will it be too much as well?

strong surge
#

I wouldn't