#Summer 2025 Internships
1 messages · Page 1 of 1 (latest)
Resume needs more breathing room imo, it looks a bit hard to read
I got that advice from a friend as well. I am stuck as to what exactly I should do to have more breathing room. I have now removed the summary lines and can try to shorten the bullet points but is there anything that you can suggest in particular that I can do to achieve that?
I have made some changes to it. I haven't cut the content in the bullets for now.
Can you please tell me if this is better and what more to do to further improve it?
Better but as other said u should make it one line. U can make it 2 line max if its noteworthy/important. bullets u have which are two lines seem verbose and not much important/noteworthy
Like first one u said it improved processing time but later adding extra sentence to show more result without number seem verbose to me
Also under ur skill section u have like CI/CD and rest apis under the category that doesnt make sense. Im assuming it is done to pass ats scan
But u gotta know they actually look at resume after they ats scan the resume
Sometimes it also reaches hiring manager beyond just recruiter so if they look at it they probably going to question ur knowledge in these terms
Leading to no interview
Also summer 2025 is too late. Start looking for fall internship and beyond
You can save a couple lines by cleaning up the coursework sections under both your universities. Only keep 2-3 of the most relevant courses or just remove them entirely if u want
I would also remove your gpa to clean up space
Your project titles can also be shorter
I would also switch your position and company name
Position should be the one in bigger font and bolded, with company name below
Could include more metrics in ur personal projects as well, especially with the distributed one
I feel kind of iffy about bolding each tech, id maybe only bold metrics
wow. that is a lot of advice. I'll work on my resume and come back here.
Thanks a bunch! @frigid wedge and @grim raft
I am not sure about REST APIs but isn't CI/CD a good fit under DevOps?
Devops are people who build CI/CD. and CI/CD isnt really skill. Its a practice created in software space. If u mention tech for building cicd or tool related to devops, then those are fine
Same goes for api. Its a architecture. U build api and cicd not list them as skills
Ex: openapi is technology that u actually utilize to build api
from that to this. I am trying to incorporate all the changes that you have been giving me. thank you for your suggestions.
how do you guys feel about this? please feel free to tell me your honest reviews about how this one feels
Some of your bolding is odd imo, i wouldnt bold stuff like recreation and front-end
I also think your bulletpoints under the norton internship are kind of vague
Is 100% compatability with future updates an absolutely certain metric?
I would personally feel iffy about defending it during an interview
they were using an Objective-C codebase for the ui. I worked on reimplementing the same ui using swiftui. I'll see how I can frame it in a different way
to address this, I have changed the 'DevOps' title to 'DevOps Practices'
does it make more sense now?
Some of the things you have listed under there aren't entirely devops related
Rest apis, unit/e2e/integration testing, logging are all things a SWE could do instead of a devops person