#Incoming third year, Canadian, w24 and s24 internships

1 messages · Page 1 of 1 (latest)

quaint grove
#

very strong resume

#

one thing is to use some metrics that show the impact u did at ur coops

quaint grove
#

just makeup a realistic number as ur impact

fierce schooner
#

I think you have really strong parts in your resume, and you have a solid chance in getting your foot in the door of where you want to go. Just apply early, network, and grind

As for comments:

fierce schooner
#

General

  • I understand the overall strength of skills-first resumes comes from when applying to roles where it's your specialty, and matching skills get highlighted first. I just don't think it adds as much value here when you're a student - with FAANG-level+ companies, you wanna present as more of a generalist, and I think your experience speaks for itself. I'd personally move the skills section to the bottom, but it's up to you
  • I'm also not a big fan of the bullets, as they're nonstandard (why does your university have a bullet?) - would recommend removing it (you can change the styling on \labelitemi in case you're not sure how)
  • Put your expected graduation date on your resume, don't use present. This is what companies look for
  • Don't say "candidate for ...", just keep it standard:

Bachelor of Computer Science (Honours)

  • I'd prefer you remove coursework, as it adds little value compared to your awards/competitions + experience, but if you do decide to keep it, please do not be adding (Adv) or your final score (e.g., 100%) -- it's odd at best, and at worst, it makes you stand out in a seriously unusual manner. Grades are subjective by the prof and school, your 100% doesn't hold value to anyone. Be realistic and humble
  • Scholarships - you should remove the dollar amount. It's also unusual that "scholarship" isn't capitalized for the first one
  • Given that you're primarily doing remote work or are otherwise located in Waterloo, you should consider removing location entirely, replacing it with date due to the lack of value (University of Waterloo is obviously in Waterloo). It's taking up unnecessary real estate, and goes into this next point:
  • The subheading used for your experiences is highly unusual ("Designing and engineering software for..."). Just make them regular bullets, there's no reason for it to not have been.
  • I think overall, the wording of things can be made more straightforward, and highlighting impact. I'll give examples later
#

Awards/Competitions

  • Should be more consistent here (you use "placed" for 2, but not google code jam?). You can probably make things shorter as well:

ICPC ECNA RPC: Represented Waterloo in 2021 and 2022, placing 4th and 6th against 90+ teams, respectively

  • Google Code Jam doesn't need to be clarified as a "major algorithms competition", would also recommend bumping up the participant count up to match the others

Projects

  • Certain areas for improvement overall, including metrics and more straightforward wording where possible
  • Have you released your competitive programming tools? This is a solid area of opportunity to get real world users and iterate on software, especially one that has relevance to you
  • Compiler: just say it's a "Scala-based MIPS compiler", don't drown me in words

Huawei

  • Can you shorten the title on this to "Network Engineering Intern"? Having "Data Center" isn't saying anything of value to me
  • Current iteration is good, though again, I don't particularly like the way the subheadings are formatted - but it's up to you to change it

AMD

  • This is an area where the impact is not necessarily clear, would recommend revisiting and rewriting
  • Reducing development time and increasing accuracy by how much? speak with metrics (also random period here)
  • Last bullet is especially not clear, would recommend rethinking entirely. What's the extension? Where did the UI library come from? What's the issue with formatting? Is it something like:

Automated XXXXXX formatting produced by YYYYYYY

#

WePlate

  • Might be worth tagging (Early Startup) in WePlate, for the people that aren't clear on why you're not an intern here, and why your tenure was so short
  • This is also a case where making that subheading a bullet will improve the impact this conveys especially. I don't want to see your first bullet being some algorithm implementation
  • You also did not "create" an algorithm" - there's also lacking context on what optimized portion sizes are for
  • "mass amounts" is not necessary, just use the number. When talking mass amounts, we're looking at millions, if not billions+

Overall, not bad, the experiences + competitions + projects will carry you far enough on their own, but just the general takeaway is to improve your communication on the business context and impact