#3+ YOE Targeting Mid-Level Full-Stack/Backend Roles

1 messages · Page 1 of 1 (latest)

ripe badge
#

Been casually applying looking to job hop. Sent out 250+ cold apps since mid 2024 with 1 callback. I'm worried my experience isn't strong enough for mid-level positions. Also should I include more bullet points to showcase soft skills (ex: mentoring interns)? I'd appreciate any other feedback.

dense jungle
#
  1. Experience section sounds really clear and it's easy to understand but to make it ATS friendly, I would end each bullet point with a period
#
  1. Recruiters mainly prefer education on the top and skills on the bottom, but if your education is weak, keep it that way
#
  1. Way too much blank space on the resume. I could probably fit 2-3 projects on your resume
ripe badge
#

I based it off of the recommended one from r/EngeeringResumes (https://docs.google.com/document/d/1MBvhATv8y-ESORopRoLSZ3f3HjkM_Qa_f8fIHAEqgnI/edit?tab=t.0) , but I'll play around with that template

#

i heard education should be at the bottom for people who already have some years of professional work experience, so I'm leaning towards keeping it at the bottom

#

any tips for the work experience bullet points?

ripe badge
#

New version based off Jake's template. I'm worried my section for Company 2 has too many bullet points and may be hard for recruiters to read. What do you think?

deep monolith
#

It does make sense that Company 2 would have many bullet points though. I think most recruiters would understand that.

wintry jacinth
#

Have you leveled up in title at company 2? One thing some teams look for in mid experienced hires is career progression - it’d also help break up your points if you worked on various teams/projects

#

Honestly, your initial formatting is fine - the main concern is you don’t make it easy to parse relevant pieces of your resume (e.g., how and what tech did you use when) so I would consider bolding relevant keywords that fit the jd stack in your experience so we can know better what you did and how you’d fit in an opening

ripe badge
#

They haven't promoted me yet, that's part of the reason why I'm looking.

#

I've received conflicting advice about bolding the keywords. I heard it can make the resume too busy. How should I balance that?

wintry jacinth
#

Two ways I find this works well is if you only bold relevant tech for teams that are looking for specific stack experience (e.g., React, Django), or if the business domain is relevant highlighting that there (e.g., POS systems)

In your case because the content is so dense I would look to vary it up to make these parts stand out more or you will get skipped over more often esp if your last company isn’t strong

ripe badge
#

When you say if my last company isn't strong do you mean whether or not it's reputable, like FAANG?