desperate freshman seeking guidance

[zenith pike]

I am not the best guy when coming to resume, but it seems like you are missing "result" or "impact" in each bullet points in ur experience section. Because it's recruiters who are initially reviewing ur resume, you gotta write resume in their shoes, which can be done by explaining impacts that u had through ur work. It seems like u know how to use azure. I would also recommend building a project and host on azure, as u put azure on the resume. Its kind of pointless just put azure on skill section if u have no evidence to back up with. Knowing cloud technology is key these day, so that will bring ur chances up. Lastly, there are some formatting that I hate, here and there, but ig its fine

[shut axle]

I think you can always add more impact, but i think your experience bullet points are actually really well written

some formatting advice, though. remove current status, don't round your gpa, remove uni start date, add more coursesand truncate the course names (e.g. Data Structures and Algorthims, Programming concepts), remove italitcs, remove the second header on projects (e.g. logic game known as binary sodoku), swap company name with job title in experience, add leadership/clubs/projects in the additional space

if you haven't had success i'm guessing it's a function of three things: excessive whitespace, Aug 2022 start date, and weak formatting

[shut axle]

not sure what you mean by context

[placid cypress]

I also am curious about that

[zenith pike]

You would put ur role in italics and company name on top. U always want to emphasize company name

The kind of reason i didnt specify formatting is that content is the king when coming to resume. I would work on other stuff.

I actually agree with ur bullet points well written, but its only well written. Not really appealing to recruiter. I can confirm this because i was in same exact situation, and if u didnt get any position well i think this is why by lacking impact. For formatting just follow what coinflipper said

[shut axle]

not really sure how you think these bullet points could be meaningfully improved. on a second glace i think they are really great. every bp is quantifiable, demonstrates technical (and/or 'soft') skills, and business impact.

i'd be interested to see what you think recruiters want to see in a resume

[shut axle]

this isn't standard formatting, for projects definitely don't do it, and for experiences thats where people usually put their job title

if you think it's important, you can include it within bullet points or, for example, for the physics research, say you interned at xxxx college physics dept

though it's not too important because you want to demonstrate that you are a proficient engineer who can work with other people and it doesn't matter much what, specifically, your company did

[zenith pike]

Well im only a freshman too, just doing an internship at mid-size company rn, so take it as grain of salt. What i think or realized with talking hr folks in general was that they do not know much about technical stuff at all. If a recruiter who hires senior position they seemed to be more knowledgeable, but not enough standards in engineers. Like even if u put "i used [tech] to do something" they hardly knows anything or know what it means. Sure it would be good for team matching, but its the recruiter who sees the resume first. U would put "i used [tech] to do something", just to explain recruiter that the person may have matching tech stack that is related with the company or have built similar stuff that company is currently building. So i tend to focus on result or impact such as "i improved service latency/scalability", "improved development of engineer's [something]"

[shut axle]

that's what they do though?

[zenith pike]

Yea it's what they do, but if u wanna stand out u gotta put more heavy emphasis on impact, as tech is really competitive

At least this is what i think cuz i didnt get interviews when i just well written

[shut axle]

sure.

[zenith pike]

@stray raptor if u know any engineers that have built ui components on top of ur ui or u have made reusable ui component, ig u could say "i built ui framework or reusable component for team to base it off, maintaining scalable/consistent design or ease heavy-lifting in development of ui (as u created reusable component)

[boreal tendon]

lack of impact, u need another project

[zenith pike]

These type of thing stands out for as they shows impact than what uve done. Recruiters dont really know if what uve done was good thing or bad thing with just stating what u have done

Exactly they are not knowledgeable as u think they may be

Especially for hiring intern

U need put some tech details for team matching and possible chance that it will match company's tech stack

But it gotta be minimum as u can explain those stuff on interview if hr manager or recruiter ask

General rule of thumb for project is that they either show same or similar tech stack as company or have experience building similar stuff as company. Thats all there it is. I would focus doing projects with web rn as that will match with ur web dev intern position. So project would be making website and hosting on azures