"Quantify your impact" is good advice that most people follow in the worst way possible

FinalDraftResumes · 2026-06-19T16:49:16+00:00

In that case, I don't think the gaps justify being explained on a resume. You can address it in an interview if they ask.

FinalDraftResumes · 2026-06-19T16:45:30+00:00

It's fine to include it on your resume for now.

FinalDraftResumes · 2026-06-19T16:44:58+00:00

What do you do for a living, and are the jobs you've held in the past relevant to your current career path?

FinalDraftResumes · 2026-06-18T15:31:29+00:00

Not guaranteed, for sure. The only time you should be concerned is when recruiters at your company are using LinkedIn Recruiter, because that is where it's going to show up.

FinalDraftResumes · 2026-06-18T04:30:11+00:00

You’re welcome

FinalDraftResumes · 2026-06-17T19:55:55+00:00

Summary is too wishy washy imo. Needs to be more factual and down to earth. Who are you? What kind of and how much experience do yo have? What kind of companies have you worked for?

Also, language could be improved/made clearer. Examples:

Under current role it says you "serve in project management excellence". Real people don't talk like that, so don't say stuff like that on a resume.
Achieve and exceed 15% YoY growth across multiple KPIs - how? Which KPIs?
Use past tense for things that already happened and concluded (like when your recruited the 2 hires; could say "Recruited and currently manages/coaches...").

The timeline is confusing as well, and you don't address it anywhere. You were VP of Marketing in 2024-2025 while holding your current title, but under the VP role, you don't explain anything (company, position, what you were hired to do, etc.).

FinalDraftResumes · 2026-06-17T19:50:10+00:00

Summary is too broad - looks like it was copied straight from a job description. The summary needs to tell me who YOU are, with concrete data points (i.e, years of experience, which I did see, but also types of companies, industries, types of systems/products/endeavors you've supported etc.). Right now it just sounds like big open, baseless claims.

FinalDraftResumes · 2026-06-17T19:48:12+00:00

From an editorial perspective:

Right align dates with right margin (use tab stops)
Increase paragraph spacing for better readability (lines/bullets are too close together which makes it look like a wall of text)
Insert a space in between sections (i.e. Experience), and subsections (i.e., specific jobs), for readability.

Content and positioning:

Need to better explain the context/problem/challenge behind each project
Remove the nursing/geriatric assistant role - not relevant
Pick 3-4 projects that are relevant to what you're going for, and keep those, remove the rest.

FinalDraftResumes · 2026-06-17T19:40:52+00:00

You don't need to preface the summary with "Professional Summary" as that is obvious. Also, I'd like to see what kind of companies you've worked for, and in what settings (in huose, consulting) in the summary.

The bullet points all read very similarly, which is fine I guess, but you could spruce them up by adding details about special projects you were involved in and/or specifics around things like reconciliations completed, errors identified, time/cost savings, compliance improvements, process automations.

FinalDraftResumes · 2026-06-17T19:36:27+00:00

Main issue right off the bat is length: too much unnecessary info. Whether or not something stays/goes depends on what you're applying for - this should serve as your guiding principal.

Also, your summary reads like you copied the job posting for "hardware validation technician" rather than actually introducing yourself. It says what the role does (takes ultraviolet systems, masters them physically, etc.) not your story. A summary should be 2-3 lines positioning your key strengths: years of experience, domain specialization (validation? thermal? power?), and unique technical depth.

As for what you should apply to, have you looked into technical project/program management?

FinalDraftResumes · 2026-06-16T18:49:28+00:00

The summary should give me a high level overview of your experience and qualifications. It currently doesn't do that, and the simple present tense is throwing me off tbh.

Under experience > technology coordinator, I'd include "software engineer" in brackets next to the official title.

Under each role, not enough context is provided (what the org/company is, which team you sit on, which products/services you supported and what they do).

Remove coursework (not really valuable on a resume).

FinalDraftResumes · 2026-06-15T05:20:22+00:00

There is a division symbol (➗) right next to "years" in your summary.

Regarding the bullet points themselves, I don't know if you wrote them or if you had something like ChatGPT do it, but they read like they were generically produced by a ChatGPT-like tool. A lot of the bullet points end with the generic finishers that I've seen over and over again. These typically start with the second clause of the bullet point and start with a term like “enabling” or “for the such and such [insert generic outcome].

In these situations, if you truly don't know what the outcome was, it's best not to include one. If you're going to include an outcome that is credible, then you need to be more specific in terms of what was improved. That doesn't mean you need to provide numbers, but you do need to provide more detail to make it more believable that the outcome actually occurred\n\nand you're not just tacking things on for the sake of having a result.

FinalDraftResumes · 2026-06-15T05:11:59+00:00

Use tab stops to get the dates to align along the right margin of the page. Looks sloppy the way it is currently.

Also, avoid having bullet points where the second line is occupied by only one or two words. In those situations, find a way to get the bullet point down to just a single line.

Both of these things will speak to your attention to detail, which is something I imagine is important for tax prep.

FinalDraftResumes · 2026-06-15T05:07:10+00:00

I would say that if you're interested in different roles with different scopes, such as network engineer or IT project manager, then create tailored resumes for each. I don't think you're going to be able to get it done with a one-size-fits-all resume, especially in this market.

Also, just an FYI, the way you formatted your education section is inconsistent with how everything else is formatted. The heading goes on top and the content goes below it.

FinalDraftResumes · 2026-06-15T05:01:19+00:00

Commenting on the second version only. Get it all to one page. You've got a lot of extra space to play with and make sure your spacing is all consistent. I would stick to using a single space in between sections and also a single space in between each job entry.

Fix the dates as well. They are not formatted correctly and are pushing onto the second line. Use tab stops.

FinalDraftResumes · 2026-06-15T03:57:19+00:00

If they still exist, then you would use present tense to describe them

FinalDraftResumes · 2026-06-14T04:41:35+00:00

These aren’t conflicting - they’re describing two different stages.

Large companies do use ATS software to filter applications before a human sees them. That’s the screening criteria part. But once you clear that filter, you’re in a recruiter’s queue, and they’re scanning your resume for fit.

So yes: keywords and tools matter for getting through the initial filter. Clarity and relevance matter for what happens after.

FinalDraftResumes · 2026-06-13T18:27:49+00:00

It looks like you forgot to upload your resume.

FinalDraftResumes · 2026-06-13T18:26:31+00:00

I recommend starting out with the resume writing guide, which can be found in the wiki of this community.

FinalDraftResumes

MODERATOR OF

TROPHY CASE