just unlucky for those three companies - separate extracurriculars and projects into two different sections, projects above extracurriculars
#2025 Grad, looking for Summer 2024 Internships
wary edge
past anvil
unless its amazon, no.
wary edge
besides more luck, reaching out for referrals, and a leadership position in an interesting extracurricular, not exactly
that's a big plus
you should date your extracurricular and projects as well
yeah it does matter - outdated unless you're still actively doing those
get rid of those and replace w something better if you aiming for faang
personal projects that are recent - a project(s) that is relevant to the type of swe you're aiming for
but it's not like you're locking yourself into say, mobile if you do a mobile project. but don't try developing a "general" project if you're thinking you want any type of swe. that's more counterproductive than picking a more defined project then applying for a position that's not the same field as that project
hope that makes sense
you don't need a revolutionary product - you're developing a project. i'm also aiming backend so i just made a project utilizing a relevant tech stack to backend
majority of recruiters (for swe intern) do not have a tech background - so a project would be more eye catching to them
only an engineering manager or lead of some sort (if they even are included in the recruiting process which 40% they are ) would even care about your github contributions.
but even so the same would go for an engineering manager anyway - projects > open source contributions
yeah that could def be one
things to keep in mind is robustness and readability for interviewers that may sometimes ask for you to walk thru a project you’ve done.
another is how well you frame the project on your resume
if you could possibly publicize the bot for use and then snatch those metrics (how many users and all that) big big big big big plus
not a downside if you don’t plan on publishing tho it’s jus an idea of the potential for it -
wary edge
imo do it alone so you can claim it as your own - otherwise you better be clear about what you did vs what your friend did during interviews
wary edge
well even though that's like...the least productive way to go about a project if you're pair coding the whole time, the one concern is git commit history which will include the words "pair coding" inside the git commit message. assumig you're going to use vscode's pair coding feature
even so i'd be against pair coding majority of the proj
wary edge
i mean, it’s only 5 companies chances are always low