#looking for s2024 internships (Canada) please roast
1 messages · Page 1 of 1 (latest)
Honestly, your resume is not bad at all. Great work emphasizing your impact.
I think you may have an issue with some employers due to the dates conflicting in your work between the nonprofit and the record label (overemployment), but given that you're going for internships, I'd say it's safer than for fulltime.
I'd see if you can extend the nonprofit work further than the end of august - honestly, it's fantastic experience that would impress most people due to the purpose and impact it has. I would consider renaming the title to "Software Engineer" if possible to avoid pigeonholing you into android development
I would like to see you mention typescript or javascript in the work with the record label, just because it's not implied for all recruiters that they'll understand (annoying as it is) - and yes, bold technologies for sure. I'd also prefer to name drop Postgres instead of Supabase, just because the latter is a lesser known and relevant technology that might not be communicated to recruiters or even other engineers. I'd probably add a bullet to be more specific about your work on the backend though with Postgres (even if it's on a baas)
I would also consider moving project 2 above project 1, just because of the demonstrated metrics it has, and the fact that it addresses a specific "social good" problem space, which I think is a good look on you
Project 1 could use a little bit of clarification for the first bullet - I don't think people would know what Pomodoro is, and communicating that there would be of more value to you
I'd prefer removing relevant coursework, but it's up to you. I'd also remove (Remote) from your locations just because it might cause bias against you
There are more technical nits, but you landed the core of this resume spot on - great job!
thank you so much!
Yeah the nonprofit is a volunteer position, so I'm not getting paid
That's ok, there are a lot of students who put unpaid positions (even club leadership roles) on their resume for internships/new grad, so you'll be fine
ok thats cool! will try to implement all of your suggestions
have been applying to fall 2023 with a previous iteration but haven't heard back from anywhere haha
Yea honestly it's a really tough market atm, just stay on top on things and keep your head up, and try to connect with recruiters and engineers where you can
ye will do; thanks for the review
do you think my bullets are too wordy? considering maybe shortening some of them
I think some of it is overly technical on more trivial details (see third bullet in project 1) - but in your case, it goes mostly unnoticed because of how well it flows more or less. There's also the case where you're explaining features that might not make sense without context - but this is also a factor that goes into lack of experience, and can be forgivable for internship applications
DB optimization in particular is not really something I'd personally consider noting (using indexes, sharding, bcnf, etc is all part of "basic" db design), especially at the scale of only a few thousand records (this becomes more notable at 100GBs+), but since you're still fresh, I'm ok with it, just put less emphasis on it
are there any specific parts where you see I'm explaining features without context?