#Seeking SWE Internships, 2026 grad, ~100 applications, 0 interviews, any feedback helps!

1 messages · Page 1 of 1 (latest)

winged totem
light valve
#

the first line of each of your projects should be a description of what it is. what cool/unique idea you came up with is important too, not just the relevant technologies and implementation details

winged totem
#

on my resume i didnt really have a unique name for the projects, but just left them as they are in what i sent, so i think that might be enough context for what the idea is right>?

light valve
#

the idea sure but for some of them i cant tell what you accomplished. like for your personal finance app i can assume its an app that helps manage your finance but i dont know what it does specifically to accomplishes that. even tho the titles may seem descriptive enough for you, to someone reading your resume for the first time i dont think the titles are enough to get a good idea of what you accomplished

#

especially since recruiters are going to be skimming through

winged totem
#

i see, thanks for your help!

random rose
#

Yep, srireazy is on the dot here - the biggest thing missing from this resume is any big picture highlights. You need to talk about 1) what exactly you worked on, not just what tech you used, 2) what it was for (i.e., the why), 3) and what you impacted if it applies. This is the primary reason experience is usually king over projects, but you can apply this principle to all your stuff to bring it up

If your first bullet on your first experience is "used a firestore emulator", I'm already dropping your resume

In skills, I suggest removing on concepts as it adds virtually nothing but noise (you're literally just covering everything). I also recommend splitting out frameworks and libraries from dev tools

It would be nice if you had any notable extracurriculars/involvement - you seem very one-dimensional and in this market, you need to stand out.

winged totem
#

Most of my experience section comes from extracurriculars and I’m applying to more this year to fill that up a bit more

#

But I’ll definitely make those changes about my skills and I’ll reorder my bullet points to highlight more impressive contributions

winged totem
#

@random rose @light valve I made the changes you guys recommended and wanted to know if you had any further advice

light valve
#

looks better. i would reword the first bullet point of the last project. clarify what you mean by "their input"

winged totem
#

Yeah that part was a little rushed. It just takes in an input when the program is ran, so how would you suggest phrasing that

#

I’m trying to reduce the white space too so nothing too long so it won’t go into the next line

light valve
#

what input? just try to describe the use case in one line

winged totem
#

Alright I’ll fix that up

#

Anything else you would suggest before I use this for applications?

light valve
#

thats all i had in mind. good luck!