#Feedback - Looking for new grad starting may 2024

1 messages · Page 1 of 1 (latest)

wary plover
#

Feedback - Looking for new grad starting may 2024

echo pagoda
#

i'm tired i will look tomorrow

wary plover
#

ok thank you!

fading monolith
#

Also post a screenshot of the resume instead of the actual pdf w/ [redactions] as well if youd like

wary plover
winter schooner
#

NGL, it's really visually appealing, maybe because of all the Jake's resume variations on here, but its eye catching for a resume readers standpoint at least. I know it's not a visual-oriented profession, but it goes a long way to marry a professional looking resume that's also eye catching, not many people do that and if all the resumes start to look alike, then most will start getting scrutinized for similarity

  • I'd strip the icons from the header and probably just make that whole header section one column instead of two, a little easier for resume parsers to grab.

  • Extra 'n' in Canada on your Additional Experience, just double check your whole document with a spell checker

Other than that, it's pretty solid!

wary plover
fading monolith
#

Pls share prayge (w/ redactions ofc)

echo pagoda
#

Some general advice for now:

  1. Use the STAR framework
    • Situation – the situation you had to deal with
    • Task – the task you were given to do
    • Action – the action you took
    • Results – what happened as a result of your action and what you learned from the experience. It can be helpful to include some metrics if applicable, but don't take too much sole credit for things you did as part of a team. Remember, highlighting your ability to work in a team is a benefit not a drawback.
  2. Personally I think it's helpful to include a 'Personal Profile' section right at the top of your CV. This should be a sentence which states where you are in your career, and what you are looking for. The idea is to save time for the recruiters.
  3. Make sure that everything you put on your CV has a purpose. Every single word should be there for a reason. Really sit there and think about why you are writing certain things. Are you just finishing the sentence on auto-pilot, or are you writing with purpose? Remove the fluff/waffle.
  4. Make sure that everything you put on your CV is maximising its potential. If you list a job that is not related to CS, you can still get value out of it e.g., by demonstrating your people skills, ability to work as part of a team or ability to follow instructions. Were you a TA? Great - make use of it!
  5. Try and actually make your CV interesting. This can be a somewhat difficult one to get right. But just imagine yourself in the recruiter's position, reading mindnumbingly boring descriptions of React.js calculator projects. You don't necessarily need exceedingly impressive projects, you just need to be able to convey them well. This is strongly related to the STAR framework.
  6. It's key to achieve and maintain flow throughout your CV. Make sure your bullet points are cohesive, and aren't just written in isolation from each other.
#
  1. Don't bloat your technical skills section. You don't need to write 'MySQL, MariaDB, Postgres, SQL'. Also remove skills you are not competent with. If you aren't comfortable being quizzed by an engineer on the skill, then remove it. If you divide it into subsections, ensure they actually make sense and are visually distinguishable.
  2. Don't just list all the courses you took under your Education section. We know you probably did 'Software Engineering' and 'Object-Oriented Programming'. You can include courses that are unique and/or very interesting to you, but ideally add some extra detail (particularly if they are relevant to the role). This can be a good place to briefly describe some coursework you did, particularly in order to highlight your ability to work as part of a group.
  3. It's helpful to include dates wherever possible (e.g., for experience, projects, etc.,)
  4. If English isn't your first language and/or you struggle with grammar, have a friend look through your CV for you.
  5. You probably don't need it to be any longer than a single page.
  6. If your CV looks empty, your margins are probably too big and/or your sentences are consistently not reaching the end of the line.
  7. Include links to the GitHub repo (and live site if applicable). Many recruiters won't pay attention to these, but it's far better than just providing a generic GitHub link at the top of your CV.
  8. Ensure your terminology is consistent, e.g., React vs react.js.
  9. If you are using acronyms, it's a good idea to write out the full version 'Point of Sale (PoS)' and then just refer to it by the acronym 'PoS' thereafter.
#

Ping me once you have updated it using this generic advice and I can give specific advice

wary plover
echo pagoda
#

then no it doesn't follow many of the bullets

echo pagoda
wary plover
#

1 ✅ - used xyz format
2 ✅ - included personal profile
3✅ - everything has a purpose -education, internships, projecct with legit metrics + impact
4✅ I literally was a ta and i included this
5 - I dont know how I couuld make this more "interesting"
6 ✅ - i believe this is fine
7 ✅ - technical skills isnt bloated
8 Keeping the courses to emphasize that I didnt do only math ✅
9 ✅ - Everythingg has dates
10 ✅ - english is correct
11 ✅ - is a single page
12 ✅ - no format issues
13 ✅ - project has link to github
14 ✅ - yeah terminology is consistent
15 ✅ - Dont use acronyms

#

@echo pagoda what are you seeing that doesn't follow ur list?

echo pagoda
#
  1. xyz is fine. however, i still think the z component should be the result for the company (which you included) and the result on you / your education/growth
wary plover
#

ok thats a great point

echo pagoda
#
  1. i would label this as such
#
  1. ok
echo pagoda
#
  1. i think you are good here
wary plover
#

ok thanks I have room for mroe about the app great idea!

echo pagoda
#
  1. i think you're fine here. i personally don't like bold but that is probably just me
wary plover
echo pagoda
#
  1. this is fine. maybe re-think 'Probability, Statistics' but up to you. also i'd put ML before those
wary plover
echo pagoda
#
  1. if you now have good knowledge of web development, i would remove the 'intro' from the course name
#
  1. ok. maybe add years on both sides (June 2020 - August 2020). easier to digest
#
  1. think the personal profile is a little informal. otherwise seems ok
#
  1. ok
#
  1. name is a little big and i also don't love the icons. but not a big deal
#
  1. ok
#
  1. seems fine
#
  1. ok
wary plover
#

Great thank you so much for the feedback!

echo pagoda
#

no worries, but pls be patient next time. i have a lot of ppl asking for feedback

wary plover
#

sorry!

wary plover
#

@modern glade Cold I possibly have some feedback too please? Thank you!

echo pagoda
#

boi are you really asking for feedback without editing it first

modern glade
#

Ur skills section has general stuff in it