#would appreciate any advice. Intern/new grad
1 messages · Page 1 of 1 (latest)
@lavish merlin any advice or criticism will be much appreciated looking to start applying soon.
I mean, this looks like a pretty solid resume.
Maybe put your email at the top, a website would also be a plus (can be linkedin, personal, blog).
Your leadership experience should be it's own thing. it's currently under your software engineer intern position
You have a lot of bullet points in your intern position, do you think they are all needed
Your projects look good, do you have links to them on github or live
You can bold more stuff in your projects, like your second project uses AWS EC2
Otherwise, skills look good
I just thought maybe because it’ll take to much space plus that was the only leadership experience I have and it was privately for the internship and not present. So I thought I’ll put it under the internship to show what I did during the three months
Got confused because there's a tech company called "Hey" but you are just redacting your work exp, correct?
Here's some thoughts in no particular order. Overall it's actually a great resume and you have a good shot. These are just some things I noticed that could be improved. Almost every resume has some things a person thinks can be improved. Doesn't mean it's bad or that you have to make all these changes
- I personally wouldn't list starting an ERG under work experience, but that's just me. Some people might look fondly on it. Maybe get a second opinion from someone at your school's career center
- You bold too many things in your work exp
2.5 I don't think bolding every technology and numeric value in your job exp is a good idea. I've started seeing this a lot in resumes and I don't know where it's coming from. You should bold achievements, or things that can summarize the larger point. So if I had a bullet point like: "Improved user engagement 40% leading to an extra $2M in MRR for our flagship app by overhauling the React frontend with smoother transitions, less clicks to perform actions, and lower application bundle load times", I would bold the first part: "Improved user engagement 40% leading to an extra $2M in MRR for our flagship app by overhauling the React frontend with smoother transitions, less clicks to perform actions, and lower application bundle load times"
When I look at that, the bold part tells me the main point
- When summarizing job experiences, I would not focus on what you built, what team you worked with, what technologies you used, etc. I would focus on the impact you had as a developer. How did you make the company money. How did you improve things for the company in a way that was well worth your salary. How did you set them up for long-term success. Focus on these things first, the technologies, the role you had on each team (leader vs IC etc.) is all second to this
- Last thing, I would not include projects from your coursework in the Projects section of a resume. It's typically not a good thing to do that, and since recruiters read through 100s of resumes a day, they can tell instantly if a project is coursework or not no matter how you change the description. I don't know if any of your projects are from coursework, just some advice
Best of luck. Overall a v good resume, you have good exp and projects, and you should be able to land a good internship!
@lavish merlin @tepid moon @gaunt briar @edgy carbon do you think i should keep the leadership experience there under experience just because that’s my only leadership experience and I don’t think I should create a whole leadership experience for that section since a company specific leadership experience from a internship ?
Changed up what I could @zenith osprey @clear leaf @soft cloud would love to hear anything else or if you think it’s fine to start applying now. Thanks for your previous review!
Leadership section looks better
Still too many things bolded, still the work exp doesn't focus on your impact it focuses on what was built with whom with which technology
I tried to think of my impact but I would be lying if I wrote a random number down, it’s not anything we calculated as a team while interning there
It doesn't have to be a number, that's just an example, but you should be aware of the impact your work has in the org.
What about the percentages like reducing the time to preform crud operation by 75% isn’t that impact?
Or could u give me an example of what you mean
This is metric
Impact is like what was your business impact
Impact can be quantified as metric
But instead of listing tools/tech keywords you can add more on how you contributed business value
random example would be
Created a backend testing framework to speed up development cycles for 200 developers
Or smth along those lines
Like right now you list a lot of tooling. Great, you have a wide tool kit. But how did this improve the company, or customers/stakeholders
Yeah that's the point. Like reducing time to perform CRUD operation is great, but what is that operation, how does it help users? For example, if it's a bank, then saying "Cut the time to load, send, receive Secure Messages by 50% leading to more Secure Messages sent by users"
Idk something like that, Pork Chop said it better than I could
Point is, tie your work to the business value, the company, the goal of your org