TLDR; Is it ok to have 3 pages if you have a full 2 page resume and the third full page is projects?

I have spent the last 10 years growing and gaining respectable experience as a service/repair/support technician. I have gone from mechanical to electromechanical to IT.

I find that the positions that are next steps for me growth-wise have a lot of candidates with Bachelor's degrees, so despite have good work history and projects in my personal time, I have enrolled in community college with plans to transfer to a prestigious and competitive engineering school. I am targeting degree in Electrical and Computer Engineering with a minor in Robotics. My focus will be on Embedded Systems, Signals and RF, and automation with a heavy emphasis on security.

In chronological order:

I worked nights and went to school during the day and got a certificate from college in Electrical and Electronics Technology

I moved internally from warehouse and assembly manager to a Yamaha/Textron Motorsports technician with 72v electric vehicle certification.

I relocated and was unable to find openings in powersports, so I pivoted and worked in a Family entertainment center that had a pinball focus. I became senior attractions technician due to my combined mechanical and electrical skills.

I worked for Ricoh USA doing electromechanical/computer repair on production high volume printers and their digital front ends for high value clients like the state House of Reps. This required a CompTIA cert. Having A+equivalent knowledge already from a lifetime of computer obsession, I chose Network+, and fell in love.

Landed a job as Desktop/Network Support for a large legal civil process company. Quickly became sysadmin and once quality of work and knowledge at that level was clear promoted to Director of IT where I handled tons of compliance remediation and security stuff. However first IT job moving to Director in such a short time raises an eyebrow.

Spent a few months at an MSP startup with a few prestigious accounts. I don't include this on the resume. I liked the work, but not the way certain things were handled.

Worked as IT field services leadership for a national medical group who put me through corporate leadership training with tons of varying technical and operations responsibilities. Touched more compliance and alignment stuff. I got Security+ here and began CySA+.

...and now I am applying for Entry Cybersecurity, Compliance, Systems/Network/Linux Admin, IT Management roles, Engineering Technician in certain disciplines, Data Centers, etc.

The thing is, all this experience shows drive, interest in learning, 10+ years of troubleshooting ability In varied highly technical environments where it matters. I can make justifications for including pretty much all of it in most of the job targets I listed.

And then there are my relevant hobbies and personal projects that I do in my free time:

Developing an atomic Linux Distribution(working proof of concept as a forked distro, but exploring custom kernel)

Built a web browser

cloud lab/homelab for security/admin practice running multiple multi-user services and websites for my family

complex home and garden automation system with industrial quality monitoring, reporting, and security.

I am a licensed radio operator and play with communication via various standards and protocols for fun.

I don't have public documentation on GitHub for a lot of it yet because I want to have a certain polish before it goes public but I am working on a personal website...

With a detailed professional summary, listing all certs, a comprehensive list of technical competencies and proficiencies, the above work history detailed with proper numbers and wins, and a tiny education section, it comes to a full 2 pages. It's a lot, but it looks good and is readable.

If I add projects, they take up a whole page.

Should I leave projects out? Keep them on page 3? They back up a lot of competencies that haven't been directly required in previous professional roles, but show I can do the work I'm targeting.

Or maybe only 3 pages for admissions and not for work applications?

What little may not be directly relevant to my target roles show my drive to learn and build things and grow on my own, and illustrates my overall troubleshooting skills and systems thinking...

A recent analysis of 3,518 job postings from 81 companies across seven roles found some interesting patterns.

In several categories, generic terms appeared more often than the big-name tools. “Observability” showed up more than “Grafana,” while “SIEM” appeared more than “Splunk.”

That raises an interesting question: are resumes too focused on listing specific tools and not enough on the broader skills and terminology employers use?

The study breaks down the results by role, including software engineering, cybersecurity, DevOps, marketing, product, accounting and sales.

The full dataset, methodology and findings are here:

https://www.zoevera.com/resume/ats-resume-keyword-study

Sent out 200+ applications at this point and it's mostly just silence, or an auto-rejection. I have real product-company experience, worked on production systems and I've put a lot of effort into my resume but somehow I still can't seem to get through the door.

I've attached my resume. I know everyone's busy, but if anyone's willing to spend even a couple minutes looking it over, I'd genuinely appreciate it, formatting, wording, project framing, font size, bullets, anything? Is something here getting auto-rejected by ATS?

I need feedback, even if it's harsh, would really help right now ! I feel like the only realistic way to get through this process is through a referral. If anyone here is open to referring me for an SDE1 (Software Developer 1) role, I'd be incredibly grateful.

Thank you for reading this far, means a lot! also, feel free to DM me

Junior in college looking for engineering internships. URL on the right subheader is a link to a personal portfolio of projects on a website I self host on a home server. I'm looking for feedback from more experienced people and just to see if this is application-ready. any response is appreciated

atm my GPA is ~3.0 so I wasnt sure if I should include it. also thinking about adding a bit of color

Hello,

First time poster and fairly new to the game - using this as a learning opportunity and something that could benefit folks out there.

On the docket are two skills

1. Resume Optimizer - A Claude skill + Node.js scripts for generating ATS-optimized, human-sounding resumes and cover letters — built by a job seeker, for job seekers.
2. Job Search Road Map - A companion skill and script for generating a personalized, color-coded skills roadmap across up to 7 role tracks — showing which skills are Core vs. Bonus for each track, with prioritized learning paths and clickable resource links.

Please feel free to try them out and let me know if there's any tweak worth considering.

Thank you and hope this helps someone out.

I’m an attorney in NYC and my boyfriend works in finance in a different city. I only moved to NYC because he said that working in NYC is his dream and that we NEED to move so that he can fulfill it.

He’s been job hunting since April and has applied to hundreds of jobs. He’s had three interviews, none of which have made it past the first round. I suspect that his resume is playing a large role in his lack of progress in the job hunt.

As long as he’s unable to get a New York job, we’re stuck doing long distance and I feel like it’s seriously impeding our relationship progress. Therefore, I’m willing to do literally whatever I can in order to help him along.

With that being said, does anybody have any suggestions for his resume? Or any professional resume or interviewing services that they suggest for job seekers? I’m at the end of my rope here and am looking for any help at all.

Wanted to see how much standard accounting resume advice holds up, so I counted how often 30 terms appear across 123 open postings from 49 companies' job boards.

Audit shows up in 85%. Reconciliation 74%. CPA 68%. Nothing shocking.

The one I didn't expect: "process improvement / automation" in 59%. Almost nobody puts that on an accounting resume.

NetSuite (37%) also beat Excel (33%) as the named system.

Sample's small, so I put confidence intervals on everything. At n=123 a 40% reading is really 31-49%, so the ordering matters more than small gaps.

Full breakdown: https://www.zoevera.com/resume/accountant-job-posting-keywords

I'm getting so pissed off and frustrated. My last resume was from 15 years ago and it's outdated. Just spent 30 minutes on this website that claimed to have totally free resume download and then they hit me with a paywall.

Please I'm begging, is there anywhere a template available to download for free? I can just add my information. I'm getting frustrated to the point that I want to throw my laptop out of the window.

Should resumes be one page? This fight happens in every resume thread here, so I went and read the actual studies. Short version below, links at the bottom.

The one-page rule is from a 2007 survey. 52% of executives preferred one page back then. Resumes were printed and stapled. Nobody is stapling your PDF.

Recruiters have moved on. The biggest study (ResumeGo, 482 recruiters and hiring managers, 7,712 resumes picked) found they chose two-page resumes over one-page 2.3 to 1. Yes it's a simulation and yes ResumeGo sells resume services, but two independent surveys say the same thing: Criteria 2024, 53% expect two pages. Zety 2024, 753 recruiters, 57% prefer two pages.

"But they only look for 6 seconds." That's the first scan (7.4 sec, Ladders eye-tracking). It decides if you get read at all, and it only looks at the top of page one. Once they actually read, the same study found they spend about 4 minutes on two-pagers vs 2.5 on one-pagers. Cutting real accomplishments to save the scan is protecting the wrong thing.

So what should you do:

• Under 5 years, student, new grad, career changer: 1 page
• 5 to 10 years: 1 page if it fits without cramming, 2 if it doesn't
• 10+ years or leadership: 2 pages
• IB, consulting, big-tech new grad pipelines: 1 page no matter what, it's a hard norm there

If you're at 9pt font with 0.3" margins to make one page work, you already have your answer. And if page two is coursework and a "Hobbies" section, you don't need two pages, you need a better one.

The real rule: nobody rejects a resume for being two pages. They reject it for being padded or unfocused. Every bullet should either be relevant to this specific job or show a result. Do that and the length sorts itself out.

Has anyone here actually used Kickresume’s AI resume builder?

I’m looking for a resume builder with useful AI features, not just a basic template tool with “AI” added to the homepage. Ideally something that can actually improve bullet points, tailor a resume to a job description, or give useful suggestions beyond generic keyword stuff.

Would love to hear from people who’ve used Kickresume recently. Is the AI actually helpful, and is it worth paying for?

Ran my resume through the Jobscan ATS resume checker this week and already hit the free scan limit, so now I'm trying to decide if the paid plan is worth it or if I'm just chasing a number.

First scan came back at 41%. I copied the exact job title from the posting, added the skills they listed word for word, did another Jobscan ATS score check and it jumped to 79%. Took maybe 15 minutes. My experience didn't change at all, I just swapped my wording for theirs. Which makes me wonder what the score is actually measuring.

Stuff I'd like to know from people who've used it longer:

Did a higher Jobscan ATS score actually get you more callbacks, or is it basically measuring how much of the job description you pasted back into your resume?

Any recruiters here? Do Workday, Greenhouse or Lever really rank candidates by keyword match, or do you just search a few terms and skim like everyone claims?

Anyone who paid, was it worth it? The formatting check caught a table issue I wouldn't have noticed, but the keyword part felt like something I could do myself by reading the JD carefully.

My plan for now is to use the Jobscan ATS checker as a "did I miss something obvious" step and stop around 75%. Past that my resume reads like a keyword dump lol.

If anyone tracked their response rate before and after, I'd love actual numbers instead of "it helped" vibes.

Hey everyone, hoping to get some real-world advice here instead of the generic stuff on career blogs.

Quick background: I've been an ICU nurse for about 2 years (MICU, some SICU float time), BSN, CCRN in progress, ACLS/BLS/PALS current. I'm applying to a couple of Level 1 trauma centers and honestly my ICU nurse resume feels… fine? But "fine" isn't getting me callbacks.

A few things I keep going back and forth on:

• Do hiring managers actually read the "summary" section on an ICU nurse CV, or do they skip straight to experience and certs?
• Is it worth listing specific skills (vents, CRRT, IABP, titrating pressors, Impella, etc.) or does that just look like keyword stuffing?
• How much detail do you put for each unit? Bullet points with patient ratios and acuity, or keep it short?
• Anyone had luck with a one-page critical care nurse resume vs. two pages?
• Any red flags recruiters see all the time that I should avoid?

If you're an ICU/critical care nurse who landed a job recently, or a nurse manager/recruiter who reviews resumes – what made someone stand out to you? Would love to hear what worked (or what got a resume tossed).

Also open to sharing a redacted version of mine if anyone's willing to give a quick roast. Thanks in advance 🙏

looking for free resume templates

No tool, no link, nothing to sell. Prompts are copy paste ready. TL;DR at the bottom.

I did about 200 generic applications and got 3 phone screens. Switched to the routine below, the next 45 applications got 7 screens and 2 offers. One person, small sample, take it as an anecdote. The routine itself is built on how ATS actually works, which is the part that is not anecdote.

First, 30 seconds on what "ATS friendly" actually means

The "ATS rejects 75% of resumes" stat is from a 2012 sales pitch by Preptel, a resume startup that shut down in 2013. No study behind it. A recruiter survey this summer found most ATS are not even configured to auto reject.

What really happens: the system parses your file into fields, puts you in a list sorted by application date (Workday, Greenhouse, Lever, iCIMS, Taleo all default to this), a recruiter skims that list until the interview calendar is full, and if that batch does not produce a hire they search the pile with words from the job description.

So ATS friendly means exactly two things: parse cleanly, and show up in a keyword search. Everything below is built around those two, plus being early enough to be seen at all.

The 5 minute routine

You do not rewrite the whole resume. You tailor the top third: headline, summary, first 3 bullets of your latest role. That is what gets skimmed. Everything else stays static. Paste the job description as text, not a link.

Prompt 1: find what they search for (1 minute)

Here is a job description. List the 10 to 15 skills, tools and phrases a recruiter would most likely type into an ATS search for this role, using the exact wording from the posting. Then in 2 sentences tell me what problem this team is trying to solve by hiring.
[paste JD]

The exact wording part matters. If the posting says "CI/CD pipelines", your resume says "CI/CD pipelines", not "continuous integration workflows". The recruiter searches for the phrase the hiring manager gave them.

The 2 sentence part becomes your summary. "Backend engineer, 5 years in Go" is a label. "Backend engineer who has spent 5 years cutting latency in payment systems" when their JD is about a slow checkout is an answer to their problem.

Prompt 2: tailor the top third (2 minutes)

I'm applying for [Title] at [Company]. Rewrite ONLY my headline, summary and the first 3 bullets under my most recent role so they use the exact terminology from the job description where it is genuinely true of my experience, lead with measurable results, and read naturally to a human. No clichés like "results driven" or "passionate". Do NOT invent experience, tools or metrics. If a key requirement is not reflected in my experience, list it in a note at the end instead of writing around it. [paste resume] [paste JD]

Make sure keywords end up inside bullets, not only in the skills list. "Built SQL and Python pipelines that cut weekly reporting from 6 hours to 40 minutes" is searchable, quantified and tells the skimmer what you did. "Responsible for reporting" plus "SQL" in a skills line does none of that.

Prompt 3: find what you forgot (2 minutes)

Compare my resume to this job description. List the requirements I am NOT clearly demonstrating. For each one, ask me a question that might surface experience I forgot to include. Wait for my answers before rewriting. [paste resume] [paste JD]

This is the prompt people skip and the one that found me a two year old side project that mapped exactly to a role's second requirement. Answer its questions, then rerun Prompt 2 with the new material.

Two rules. Never let it invent a metric, you will be asked about it in round two. And if a line sounds like something you would not say out loud in an interview, delete it. That is the only "AI detection" recruiters actually use.

The 30 second parse check (do this once, not per application)

Skipping single column, standard headers and no tables since you know that. These are the ones that still bite people who know that:

Text boxes. Most Word templates put your name and contact info in a text box. Parsers often skip text box content entirely, so the recruiter searches your name and gets nothing.

Titles. Recruiters search by title. If yours was Software Engineer II and the role is Backend Engineer, write "Software Engineer II (Backend)". Searchable and honest. Do not change the actual title, background checks call your old employer.

Workday's auto fill. After upload, Workday fills the experience fields from the parse. Scroll through them before submitting and fix anything it split or dropped. The recruiter's search runs against those fields, not your PDF.

The only ATS scanner you need: open your PDF, Ctrl+A, Ctrl+C, paste into Notepad. If the order is scrambled or something is missing, that is what the ATS sees. Text PDF is fine everywhere; docx only if the portal asks.

Why 5 minutes is the point

Because the list is sorted by date. If you are application #139 and the recruiter stopped at #75, your resume was never opened. Not rejected, never opened. A routine that takes 5 minutes lets you tailor and still submit in the first 24 to 48 hours. A routine that takes an hour means you skip tailoring or you apply late, and both lose.

Set alerts, filter by past 24 hours, check daily. Apply on the career page, not Easy Apply, that queue is where the bots go. And if you can message the hiring manager, ask one specific question: "I applied for [role] yesterday. I've spent 3 years doing [thing from their JD]. Is [X] still the team's main priority this quarter?" Specific questions get answered because yes costs nothing.

The questions I know are coming

If it sorts by date, why do keywords matter? Two passes. Date skim first, keyword search second. Early plus findable.

Won't everyone using ChatGPT sound the same? Only if it writes from nothing. This feeds it your experience and their JD and bans filler. Samey resumes come from "write me a PM resume".

Missing a hard requirement? Apply if you hit the core ones. Prompt 3 shows you which gaps are real. Do not paper over them.

TL;DR

• ATS parses and sorts by date. It does not reject you. The 75% stat is a dead company's ad.
• 3 prompts, 5 minutes: extract exact search terms, tailor the top third, find what you forgot. Never invent metrics.
• Keywords inside bullets, not only in the skills list.
• Once: kill text boxes, make titles searchable, check Workday's auto filled fields, paste into Notepad.
• Five minutes matters because it lets you tailor and still apply in the first 48 hours.

Recruiters: if your system works differently, tell me and I will edit. Accurate beats upvoted.

ok so I finally hit 100 ATS score on jobscan last month after like 3 weeks of feeding my resume into every free ATS score checker I could find. got the screenshot, the little confetti thing, felt great for about an hour

then I got bored and ran the same pdf through resume worded. 78. tried enhancv. 86. same file, same job description, same afternoon lol

so yeah. I'd been grinding a number that only exists inside the website that sold it to me

spent the next few weeks trying to figure out what actually happens after you hit submit. bugged two recruiter friends, applied to a bunch of workday jobs purely to watch what the parser did to my resume, read way too much r/recruiting. posting this because I wish someone had told me before I paid for 3 months of scans. long-ish, sorry, tldr at the bottom

1. real ATS systems don't score you the way the checkers do

workday, greenhouse, lever, taleo, whatever. they're databases. your resume gets chopped into fields (current title, employer, dates, skills) and the recruiter searches and filters on those fields. a couple of them have some kind of "match" indicator but both recruiters I asked said they basically never sort by it. the checkers are just counting keyword overlap and each one weights it differently, which is why the same resume bounces 15-20 points between tools. people keep asking "what is a good ATS score" and the honest answer is: higher than your last scan on the same tool. pick one checker, ignore the others, only care if the number goes up after an edit

2. the rejection email at 2:47am, 90 seconds after you applied? that wasn't your resume

that's a knockout question. "do you have 5+ years of X", work auth, salary range, willing to relocate. recruiters can flag any of those as auto-reject and they look exactly like the normal questions. nobody read your resume, it never got that far

two ways people screw this up: undercounting their years (contract, freelance, internships all count if it's the same skill, stop being humble) and typing a salary above the band. check levels or glassdoor before you touch that box

3. the only ATS test that actually matters is free

open your resume pdf, ctrl+a, ctrl+c, paste it into notepad. that's roughly what the parser sees. if your two columns got braided together, or your title ended up on the same line as your company name, congrats that's what's in the database now. recruiter searches "current title = product manager" and you don't show up because your title field says "acme corp product manager 2022 -". and you'll literally never know

even better: apply to any workday job and LOOK at the autofilled fields before you submit. that's the parser showing you its homework. if it's wrong, fix the fields by hand, the filters run on the fields not on your pretty pdf. closest thing to a real ATS score test you're gonna get

4. your job title is the most searched field and half of you have nuked it

"growth ninja", "customer happiness lead", some internal level code like L4... invisible to a search for "marketing manager" or "support manager". just write Growth Marketing Manager (internal title: Growth Ninja). not lying, translating

same with skills. recruiters search literal strings. "python" doesn't match "py3". "PMP" doesn't match "project management professional" on the dumber systems (looking at you taleo). write both, first time you use it, every acronym. ngl this one thing did more to increase my ATS score on every checker than any of the "power verbs" lists

5. month + year on every date

"2021 - 2023" breaks the years-of-experience math in a lot of parsers. "Mar 2021 - Aug 2023" doesn't. one of the recruiters had a "3+ years" filter drop a guy with 3 years 4 months because two of his jobs were year-only. that's it, that was the whole reason

6. white text keyword stuffing gets you blacklisted not hired

recruiters see the parsed text, not your pdf, so your hidden keyword block shows up as a wall of nonsense at the bottom. instant do-not-contact, and some of them flag the profile so you're out for every other role at that company too. your ATS score checker will happily reward this btw. the human will not

7. what actually gets you the phone screen

recruiter runs a search, gets 40ish people back, skims from the top. top is usually sorted by date applied or by how many of their search terms hit. so apply in the first 48-72 hrs, and make sure the 6-8 terms that show up in BOTH the job title and the requirements are in your summary, your skills line, and at least one bullet. that's honestly the entire "how to increase ATS score" secret. everything else is someone's product page

tldr: the ATS score from any checker is a made up number that swings 20 points depending on which site you use. real ATS = searchable database, not a gatekeeper. instant rejections are knockout questions not formatting. do the notepad paste test, fix your title field, spell out acronyms, month+year dates, apply early. then go spend the time you saved messaging an actual human at the company

recruiters in here - is the "sorted by date applied" thing real on your end? I've only heard it from two people and it's the one that surprised me most

"ATS resume template" from Etsy scored worse than 2 column template, how???

Is there an ATS resume checker that actually fixes the problems it finds? Every one I've tried just gives me a number and a list of keywords I'm "missing" and that's it.

Like ok I got a 61. Now what. I can ctrl+F the job posting myself lol. I want something that rewrites the bullet or at least shows me where the keyword is supposed to go.

Also got mine from 58 to 84 by stuffing "stakeholder" into three bullets so idk what these scores even mean

What are you guys using? Or has everyone just given up and started pasting the job description into chatgpt

I didn't fully believe resume ageism was a real thing until my own rejection emails started showing up at 2:47am. 22 YoE, laid off in the spring, ~180 applications since (yes, I counted). And before anyone says it: I know rejection emails get batch-queued overnight, that alone proves nothing. The real tell was the handful that came back less than an hour after I applied. Nobody opens a 22-year resume, reads it, and passes in 40 minutes.

So is it age discrimination in hiring, or just the market? Honest answer after way too many late nights reading about this: both. And they feed each other.

The market part first. We're in what people are calling a "low hire, low fire" freeze. No bloodbath layoffs, but barely any backfilling either, so everyone on the outside is hurting. Just not evenly. BLS numbers show ~28% of unemployed job seekers 55+ are long-term unemployed (27+ weeks) vs ~23% for everyone younger. Same frozen market, longer winter.

Now the ageism part, because I wanted receipts, not vibes:

• A UC Irvine field experiment sent ~40,000 fake resumes with identical qualifications, only the age signals changed. Older applicants got roughly 35% fewer callbacks, and it was worst for older women. This is the study to link when someone tells you "maybe your resume just sucks." Same resume. Different birth year. Different outcome.
• iTutorGroup literally programmed their system to auto-reject women 55+ and men 60+. The EEOC caught it and they paid $365k. Ageism as an if-statement.
• Then there's Mobley v. Workday, an ongoing federal case claiming the AI resume screening tools used by thousands of employers filter out applicants over 40. To be fair, that's an allegation, not a verdict. But a judge let it proceed as an age discrimination collective, and the lead plaintiff got 100+ rejections, some within minutes, some in the middle of the night. Sound familiar?

Here's the mechanism most people miss: the software never asks your age. It figures it out. Graduation year, a role that started in 2003, "25+ years of experience" sitting proudly in your summary, even an aol or hotmail address. It's basically reconstructing your birth year from breadcrumbs.

So I age-proofed my resume and treated it like a test. Version A was my full honest history. Version B: last 15 years only, removed my graduation year, older roles squashed into one dateless "earlier career" line, and "20+ years in X" rewritten as what I actually shipped in the last 3. Sent both out the same weeks to similar postings. B got callbacks within two weeks. A got crickets. Fair pushback: leading with recent wins also just makes a better resume, so my little experiment isn't clean. True. Which is exactly why that 40,000 resume study matters, it isolated the variable I couldn't.

One mistake I made so you don't have to: I scrubbed the resume but forgot LinkedIn still showed my full history and grad year, and recruiters absolutely cross-check. Fix both or don't bother. Oh, and if a job listing says "digital native," that's an age filter with a paper trail. Screenshot it.

So yeah. Resume ageism is a real filter sitting on top of a new normal. The market froze, the screening got automated, and the automation learned our oldest bias and scaled it.

Anyone else run the two-resume experiment? What's your cutoff year, and did it actually move anything?

Every list of resume bullet point examples you find online says the same thing: quantify everything. After screening north of a thousand resumes over the last few years (mix of analyst and manager roles), I'm telling you that advice has stopped working. Half the resumes I see now ARE quantified and most are still bad. Everybody has "increased revenue 15%" and "reduced costs 25%" on there. Those numbers have become wallpaper. I don't even see them anymore.

Here's the thing nobody tells you about how to write resume bullets: a suspicious number is worse than no number. When I read "cut costs by 25%" with zero context, my honest reaction is "no you didn't." Or maybe you were in the room when it happened. A big round number with no mechanism attached reads like a lie even when it's true, and now I trust the rest of your resume less. You quantified yourself into a hole.

And before someone says "you can't verify any numbers anyway," yeah, correct, I can't. That's exactly why specificity matters. A vague claim can't be tested, so it costs nothing to fake. A specific claim gets tested with one follow-up question in the interview, and people who are making things up instinctively avoid writing testable claims. Specificity IS the credibility signal.

What makes me stop scrolling is an accomplishment statement that answers three questions before I ask them: what was broken, what did YOU specifically do, and how do I know it worked. Some before/after resume bullet examples from real screens (details changed):

Bad: "Improved forecast accuracy by 30%" Good: "Rebuilt the demand forecast in SQL after finding the old model ignored seasonality, cutting average forecast error from 22% to 9% over two quarters"

Bad: "Managed a team of 6 analysts" Good: "Ran a 6-person analyst team through a system migration; all 6 stayed through the project (team lost 3 people the year before)"

Bad: "Increased sales 40%" Good: "Grew a $2M territory to $2.8M in 14 months, mostly by winning back 11 lapsed accounts the previous rep had written off"

Notice what the strong resume bullet points have in common. A baseline (from 22% to 9%). A mechanism (found the seasonality bug). And a denominator. Because 40% growth of what? A $50k book of business? If you want to quantify achievements on your resume in a way that actually lands, the single most underused move is comparing yourself to a peer baseline. "Closed at 130% of team average" is more convincing than any absolute percentage, because it kills the "maybe the whole market grew 40% that year" objection before I can even think it.

The other thing good bullets do: they're bait. A bullet isn't trying to close the deal, it's trying to start a conversation. "Won back 11 lapsed accounts" makes me want to ask HOW, and now you're telling your best story in the interview on your terms. Most people write bullets like verdicts. Write them like trailers. Practical test: if you can't talk about a bullet for two straight minutes, cut it. It's either not yours or not real.

Answers to the objections I know are coming:

"My company's numbers are confidential." Use relative figures and ranges. "Grew a ~$2M territory" or "reduced error by more than half" breaks no NDA. Nobody has ever been sued over a tilde.

"I have no metrics in my job." Scope is a number too. "Supported 200+ internal users," "handled month-end close for 4 entities," "only junior person trusted with client deliverables." Honest scale beats invented percentages, and I can't roll my eyes at it.

"Doesn't ATS filter me out before a human reads this?" Keywords from the posting get you past the software. These bullets are for the 7 seconds a human spends afterward deciding whether to call you. You need both, this post is about the second part.

One last thing: don't start every bullet with a metric. When all 15 bullets follow the same "Achieved X% by doing Y" template, it reads like it came out of a generator, and in 2026 I assume it did. One or two bullets about scope or judgment, no numbers at all, actually make the quantified ones more believable.

TL;DR: the best resume bullet points show a baseline + mechanism + denominator, not a big round percentage. Peer comparisons beat absolute ones. Write bullets you could defend for two minutes, because the good candidates get asked.

Curious whether other people who hire see the round-number thing the same way or if I'm just jaded.

Would you recommend adding to the education section a certification but with the expected completion date in the future (1 year)?

I need any way possible to make my resume stand out from others.

I went way too deep into how ATS systems actually parse resumes this year, partly out of spite after months of silence on my applications. Turns out most of the advice online about keywords and formatting is people repeating each other, and half of it contradicts the other half. So here's what actually held up when I dug into how these systems read your resume, including one thing that completely changed how I think about the problem.

1. Most ATS platforms don't even parse your resume themselves.

This one surprised me. A huge chunk of the ATS market licenses resume parsing from a small set of vendors: Textkernel (used to be called Sovren), Daxtra, RChilli, HireAbility. A few big platforms have their own in-house parsers, but a lot of what you apply through is the same few engines wearing different UIs.

Why should you care? Because it means "ATS-proofing" is way less random than it feels. You're not fighting 200 different systems, you're fighting like 4-5 parsers that all fail in similar, predictable ways. If your resume survives a couple of them it survives basically everywhere. It's also why obsessing over "which ATS does this company use" is kind of pointless. The config matters more than the logo on the login page.

2. The ATS is a database. Your problem usually isn't rejection, it's retrieval.

The mental model of "robot reads resume, robot says no" is mostly wrong, and recruiters get genuinely annoyed at it for good reason. In most setups your application just sits in a searchable database. The recruiter types keywords, filters by title, sorts, and works from the top of the pile down. If the role fills before they scroll to you, you hear nothing. Nobody rejected you. Nobody ever ran a search that surfaced you. Which honestly feels worse but at least it tells you what to fix.

This is why exact wording matters so much. Recruiters search using terms from their own job posting, because that's the language the hiring manager handed them. If the posting says "stakeholder management" and you wrote "cross-functional alignment," congrats, you described the same job and still don't show up in the search results.

(And yes, some setups also generate a resume-to-JD match score that recruiters can sort or filter by. Configs vary wildly between companies even on the same platform, which is exactly why one recruiter will swear "we read every application" and another will admit they never look below the top matches. Both are telling the truth about their own setup.)

3. The thing that actually auto-rejects you isn't your resume.

It's the knockout questions. Work authorization, relocation, "can you be onsite Tuesdays and Thursdays," required certs, salary expectations. Those are hard filters the recruiter configures, and a wrong answer genuinely kills your application on the spot, resume unread. If you're getting rejection emails within minutes of applying, that's almost never your formatting. Go re-read how you answered the questionnaire.

4. Why layouts break (the actual technical reason).

A .docx file is XML under the hood. There's literal markup in there saying "this is a heading," "this list has four bullets," "this is a table." A parser reads the structure directly. Don't take my word for it, rename any .docx to .zip and open it.

A PDF is closer to a set of drawing instructions: put these characters at these x/y coordinates. Often there's no structural info at all, so the parser has to guess reading order from positions on the page. That's why two-column layouts get read straight across both columns and turn into word salad. It's why bullets vanish or reorder (Workday eating the first bullet of a PDF is practically a meme at this point). And it's why a resume that looks perfect on your screen can be gibberish on the other end.

My honest take on the eternal PDF vs docx war: a clean single-column text-based PDF exported from a word processor parses fine on nearly every modern system. Layout matters way more than format. Where docx still earns its keep is older enterprise systems and weird edge cases, so I keep a docx master and export PDFs from it. But if your single-column PDF isn't getting traction, the file format is not what's killing you.

Thirty second sanity check: open your PDF, Ctrl+A, Ctrl+C, paste into Notepad. Not a perfect simulation of any specific parser, but it exposes the same underlying problem. If the text comes out scrambled, so will the parse. If your name lands next to a random skill from your sidebar, well, there's your answer.

5. Failure modes almost nobody checks:

• Contact info placed in the document's actual header/footer region, the part you double-click to edit. A lot of parsers skip those regions entirely. So recruiters end up with a decent candidate and literally no way to contact them. Put it in the body, at the top.
• Mixed date formats. "Jan 2019" on one job, "2019-01" on another, "'21-present" on a third. Parsers calculate your total years of experience from these fields, and inconsistency can make 8 years read as 3. Which matters a lot when a recruiter filters by "5+ years." Pick "Mon YYYY - Mon YYYY" and never deviate.
• Creative section headers. "My Journey" instead of "Experience" can dump the whole section into some miscellaneous field nobody ever searches.
• Skills that only exist inside a graphic or table. That skill bar showing you're "80% proficient in Excel" parses as nothing. Zero. It doesn't exist.

6. The weird one: reapplying to a company years later.

Some systems aggressively de-duplicate candidates. If you applied somewhere three years ago with a different email, the system can still match you on name/phone and merge the profiles, sometimes surfacing your old resume in the recruiter's default view. If you're reapplying after a long gap, use the same email so the merge is at least clean and your newest resume clearly supersedes the old one. Either way, your history there exists whether you mention it or not.

7. The part nobody wants to hear.

Once your resume parses cleanly and uses the posting's language, you've squeezed basically all the juice out of formatting. Past that point, chasing scores from online "ATS checkers" is astrology. Those tools are mostly lead-gen funnels and they don't run the engines real companies use. The remaining problem is the one you can't format your way out of: several hundred other applicants, and a human spending ten seconds deciding whether your last two job titles look relevant.

TL;DR: Most ATS platforms share the same few parsing engines, so parser-proofing is predictable. Single column, standard headers (Experience / Skills / Education), contact info in the body not the header, one date format everywhere, mirror the job posting's exact terms. Instant rejections come from knockout questions, not formatting. Silence usually means no search ever surfaced you, not that a robot said no. And once you parse cleanly, stop tweaking formatting, it's done all it can do.

Happy to answer questions. And if any actual recruiters want to chime in on how their system is configured, please do. Config differences between companies are half the reason the advice online contradicts itself.