#New grad cooked

1 messages · Page 1 of 1 (latest)

void prairie
#

Are you applying early? That's been the biggest factor in callbacks this year. Given your professional experiences I would also be indexing more on any extracurriculars/leadership you have as they seem to improve callback rates. Your resume isn't awful at a brief glance.

Looking into it, your experience reads generic and all over the place without any significant business metrics across all of your experiences + projects. There are also several points where, from a hiring manager's perspective, your experience seems questionable. Because of your lack of metrics, your bolding also emphasizes a lot of weak areas of your resume, so it'd probably be better to bold your tech instead of metrics. Your coursework and concepts also add little to no value, and I would prefer to remove it in favor of whitespace.

#

Digging deeper into more in-depth nits and critiques:

Role 1

  • Why is Redis/Docker/Kubernetes relevant for your first point? If you're talking about cache and deployment infra then make that clear and on a separate point (because you have 0 devops exp otherwise). As-is it just reads like you're trying to cram as many different technologies into your resume as possible (which is not a good strategy)
  • Your second bullet about the Mission Control panel gives me no information, and you don't need to include mantine for companies that don't use it. I'd prefer you expand on what this was for (because again, it's not clear)

Role 2

  • Did you use AngularJS or Angular? You also don't need to include Apollo, and I don't know how QA testers are involved here
  • Third point reads like you're trying to cram technologies, doesn't really tell me anything
  • LOC count is completely unnecessary, and your metric isn't particularly impressive either

Role 4

  • What exactly is this startup for? "Serving users globally" doesn't tell me anything pertinent
  • Improving mobile load time by 5 seconds honestly speaks worse to both yourself and the startup (if these are pages you wrote yourself, you're telling me you wrote shitty enough Next.js code that it would take 5 seconds to load)
#

Just to summarize: overall, your resume is lacking major highlights to impress a recruiter/hiring manager and I would be applying early if you want to see any callbacks.

trim scroll
#

im mostly targeting backend/fullstack roles which is why i put a bunch of tech emphasizing that experience but not sure what i should replace that stuff with

void prairie
#

It seems you’re focusing more on the tech and not actual work done - I would look at other resumes and see how people are structuring relevant experience there

trim scroll
#

alright ty i will try to focus more on impact. Is the coursework section irrelevant once i graduate?

#

I have gotten it mentioned in 2 interviews i had (interviewer asked me to briefly talk about some classes i took)

void prairie
#

From what I’ve seen coursework doesn’t help you for most firms, and if you’re getting asked about it, it speaks more to either the depth of your experiences or the company’s weaker standards on tech hiring (e.g., local banks)

#

And other than the high perf computing thing, you don’t particularly have any standout courses either

#

@normal pike if you have anything to add on a public review, at least be helpful instead of trying to solicit for your bs services smh

trim scroll
void prairie
#

I think the way to make your projects stand out is by making your intrinsic motivation clearer. One of my friends has an anime tracker for one of the projects - but because it solved a clear problem and was well emphasized in both metrics and work, it’s the one thing they get asked most about in interviews

#

Does that make sense?

trim scroll
void prairie
#

One way to look at is would be to answer: can you take your project beyond a tutorial? E.g., for techhub, how many sales can you generate? Number of visitors? Web vitals metrics?