#Requesting for Resume Review

22 messages · Page 1 of 1 (latest)

shell swift
#

I'm graduating next month and I'm applying for a Frontend or WordPress position.

example_page_1.png
burnt raft
#

You’re doing a lot well. I see that your resume was built in LaTeX, presumably using Jake’s Resume or something similar as a template. Your ordering of education then experience then projects then skills is perfect for a fresh graduate, you’ve got three bullets per project or experience which is great, and your skills section doesn’t drag on.

The biggest thing I feel you could improve on is the content of your bullets. You put tools and frameworks front and center in each, rather than achievements and accomplishments. Rather than saying something like “Used Selenium…” you might want to phrase things like “automated validation for 17 web forms using Selenium, improving test efficiency and data integrity”, putting your accomplishments front and centre while also noting the tools you used. Dozens of applicants know these languages, frameworks, and tools, but what you’re trying to showcase is that you bring value to a dev team and an employer and that you know how to use these tools to do so.

Other big thing is the summary section. I’m not sure you need one at all, since your degree and prior experience communicates your intended path well enough and it doesn’t say anything the rest of the resume doesn’t already say. Summaries bring the most value to career switchers, where that context is helpful for resumes full of unrelated work experience. For you, it might be taking up space you could use to expand on your work experience

#

And the last major thing I’ll note is that both your summary and skills sections claim React proficiency, but you mention the framework in a single bullet that essentially just says you’ve used it before. React and TypeScript are foundational frontend development skills nowadays, and this might be the thing killing your resume for a lot of traditional frontend web dev roles. I’d strongly recommend going into more detail on your React related accomplishments in your work experience and project sections

Nitpicks:
Using “Web Development Intern” and “QA Testing Intern” might be more natural than putting intern in parentheses
jQuery isn’t a language, it’s a framework
If any of those projects are deployed and/or are open sourced on GitHub, I’d include links to them (on the non anonymized version of course, maybe you already did and just redacted them for this anon post)

#

I assume you’re already familiar with STAR based on these bullets, of course if not I’d go read up on that as well as other approaches like CARL and XYZ - the more successful resumes I’ve seen tend to be very STAR flavored, but dont always rigidly adhere to the structure if it doesn’t feel natural and can draw from other approaches depending on what the bullet is intended to communicate

lone mortar
#

No need to pester people in other threads please

undone wolf
last elbow
#

if folks have time they will engage

undone wolf
#

Ok

#

My apologies

lone mortar
#

This thread is not yours. This thread is for the OP. Please help us help others by keeping threads on topic.

thick jackalBOT
undone wolf
shell swift
#

Okay, I revised my resume according to your advice, removed the summary, and added the certificates section. Please review again because I'll apply to 5-10 more companies soon (so far, all of the companies I applied to ghosted me and idk why).

example_page_3_1.png
burnt raft
#

It’s looking pretty good. You do a pretty good job of communicating what you did and what impact your work had for the most part.
The current weakest bullet point on your resume is the second bullet in your last project, “Managed sample student account data within Firebase […] demonstrating strong data handling.”
What did ‘managing student data’ entail? You mention the type of data you worked with, but not what you actually did and what the outcomes were. Even just noting that you gave structure to this data adds useful context. ‘Demonstrating strong data handling’ is also very subjective and not very tangible as an outcome.
The other weaker bullets all are under your projects section as well: ‘core Kotlin functionalities’ is rather vague, ‘core website functionalities’ makes me want to ask what said functionalities were, and ‘organized information access’ is too general.

Overall, work on being less vague. You want to clearly state what problem you solved, what methods/approach you used, and what the concrete, measurable outcome of your work was. You don’t need metrics for every bullet and it’s especially understandable that your projects would lack them, but you want to stay away from things as subjective as claiming that you demonstrated strong data handling. You want to show that you have this skill by describing things you did to data and the positive outcomes of your work, rather than tell.

#

This is mostly picking at your projects section, as your work experience section is looking pretty nice. You don’t always get to name drop specific features and improvements you were responsible for as a developer working on proprietary products, but for personal/hobby projects like the ones in your project section you should be able to be more specific

shell swift
#

Update: I revised the resume again according to your instructions and I'm still not getting interviews and they all ended up ghosting me. I applied to them when they posted it in less than 24 hours.

I guess they want someone who's the "master of all trades" at this point as frontend developer position is just saturated and some junior/entry-level roles require 1-2 years of work experience.

lone mortar
#

The job market is bad right now. I'd expect it to take months of searching

burnt raft
#

Your university may have one or even several resume review services, for example my university offered resume reviews from the career services center and separately from engineering career services, then some recruiting events included resume reviews that reflect what the host company looked for in potential interns/new grads from the school
Reddit has a general resumes sub and an engineering resumes sub
LinkedIn connections and irl peers may offer resume review services formally or informally

#

People tend to disagree on what makes for a strong resume, even (and especially) the people responsible for reading them
I think the input I provided here is solid and broadly applicable, but having more input can help you fine tune and better understand what signals people are getting or missing from your resume

#

With two internships and three several month long projects, I don’t think you lack the experience to land something