- Overall comments
- I like the format and organization, it’s easy to follow and looks nice
- Honestly you have a pretty strong resume, just a few things that I think can be improved. And I think the stronger parts of your resume come after the ____ experience, but ____ is at the top so you need to focus on making that one as strong as possible.
- Technical skills section
- Move “exposure” items to “proficient” - The resume is a place to grab a recruiter’s attention, you are basically shooting yourself in the foot by flagging yourself as not that strong with typescript. “Fake it til you make it”, they don’t need to know you only have minor exposure to typescript.
- Once you are in the interviews you can be honest about your experience, but you need to get back that first gate
- Professional experience section
- Just looking at your ____ experience for now - I see a lot of filler words, and have a hard time understanding what unique value you added to the team.
- You can keep this information as I think it provides a general outline of what you did, but I would strive to come up with one or two unique things that YOU did. Maybe you presented a new idea or way of thinking, identified a gap or performance issue, etc. Recruiters love that kind of stuff that jumps out and paints a more colorful picture of YOU
- Can you try to come up with a few things that you and only you could say that you did on that team? Then we can work that in and reword the current bullets
- Select projects section
- These are really good, but I would love to see links to the projects that I could check out. You shared with me one project that looked really nice, that goes a long long way if recruiters can just click on a link directly in your resume and see a working product that you built.