#2 yoe full stack dev looking into junior backend positions
1 messages · Page 1 of 1 (latest)
that is no one is going to read
a lot of fluff like "engaged in code reviews..." and "attend sprint meetings..."
Typically you should be aiming for
4-6 bullet points, each bullet point being 1-2 lines (mostly 1 line)
@sturdy oriole Thanks for your input. Then with what could I fill up the extra space it's going to have? Do you think I would need some projects for that?
You should (reasonably) increase the font and spacing, increased font will also make it easier to read
Since you have a decent experience, just your best project is fine (I'm assuming you have one or there's no point in putting your github)
I'd also put skills at the bottom
Thanks. I'm curious why putting skills at the bottom would be better (out of pure curiosity). Also would there be anything I could do to make it more backend-focused? Sorry if I'm asking too much!
skills is mostly just for keywords, not useful for measuring your skill with it
that's what job and project descriptions are for
Take out the Intern at your first role, especially since you have 2+ YOE, recruiters will see it as 'lesser' than a full-time engineer position and mark it against you.
Agreed with the other commenter, some of your content can be described as fluff within the lower half of your latest role. I'd consider keeping maybe 2-3 high-impact ones and axe the rest.
Disagree with moving Skills to the bottom as you'll make a recruiters life easier when they scan the section to check-off if you have the majority of what's on their list, then will move to review your XP. They don't spend no more than 10-15 sections, so don't make it hard for them to parse information.
Add x2 tabs to space out your comma separated lists against your actual category titles as they look crammed left-aligned.
e.g. Programming Languages: skillOne,...otherSkills
Market sucks so just keep plugging away and reaching out to those in your network for referrals.