A resume stands out when a recruiter can name your specific outcome within the first six seconds of scanning it — and when the applicant tracking system that reads it first finds the exact title, skills, and dates it was told to match. That dual test, human skim plus machine parsing, is the condition everything below serves. Miss either side and the document fails before anyone judges your experience.
Most resumes fail on one of those two tests, rarely both at once. A beautiful PDF with columns and icons gets mangled by the parser. A clean text file listing duties gets skimmed and forgotten. The seven sections below work through the fixes in the order that matters, from the job posting outward to the final file export.
Decode the Job Posting Before You Write a Single Line
Start with the posting, not your work history. Hiring teams increasingly screen with keyword-matching tools, and according toJobscan's 2024 analysis of over one million resume-to-job-description comparisons, the average match rate among job seekers was around 40 percent against a 75–80 percent target for passing automated screens at large employers. Whether or not that exact figure holds for your industry, the principle does: your resume either mirrors the posting's vocabulary or it doesn't.
Pull the posting into a plain text document and highlight every hard skill, tool name, certification, and job title it mentions. Separate those into must-have and nice-to-have. Job titles and software names go in verbatim — if the posting says "Salesforce Administrator," don't write "SF admin." Paraphrasing is the single most common reason a qualified candidate gets filtered before a human ever looks.
Note what the posting repeats. If "stakeholder management" appears three times in a 400-word description, it's doing structural work in the role and belongs in your summary and at least one bullet. Repetition in a posting signals priority, not sloppy writing.
Finally, check whether the employer names its applicant tracking system. Workday, Greenhouse, Lever, and Taleo each parse documents slightly differently, and Workday in particular is notorious for scrambling text inside tables and multi-column layouts. Knowing the system tells you how conservative to be with formatting later.
Lead With a Title Line That Mirrors the Role
The line under your name is the most-read sentence on the page after your name itself. Use it for the job title from the posting plus your differentiator. "Senior Accountant | CPA | SaaS Revenue Recognition" tells a hiring manager in four seconds what you are and why you're not generic.
This is where most resume advice goes soft. The practical rule: if a recruiter searched their ATS for the exact job title and your resume didn't contain it, you don't appear in the results. A title line containing the posting's exact phrase fixes that at essentially zero cost. The differentiator after the pipe is for the human reader and should name a specialty the employer actually needs.
Skip the objective statement. "Seeking a challenging role where I can grow" says nothing and consumes the highest-value real estate on the page. A professional summary of two to three lines works only if it contains a number, a credential, or a named domain — otherwise replace it with the title line alone and let the experience section speak.
If you're changing industries, the title line carries more weight than anywhere else. Write the target title, then anchor it with the most transferable credential or domain you hold. You're telling the reader which pile you belong in before they've read a single bullet.
Turn Duties Into Outcomes With Numbers and Baselines
Every serious guide says "quantify your achievements." Almost none tells you the hard part: most people don't have metrics sitting in a drawer. The workable method is to build a baseline from what you can actually recall or reconstruct, then attach scale to the bullet even when a precise percentage is unavailable.
Work through these four shapes and pick whichever fits each role:
1: Volume: "Processed 340 invoices monthly" — headcount, ticket counts, accounts, lines of code, clients. 2: Scope: "Managed a $2.4M operating budget across three departments" — money, team size, regions, systems. 3: Time or rate: "Cut month-end close from nine days to six" — cycle time, turnaround, response rate. 4: Outcome with a base: "Raised renewal rate from 81% to 88% across a 200-account book" — always name the base, because percentages without a denominator are noise.
If you genuinely can't reconstruct a number, quantify the environment instead: team size, customer tier, transaction volume, system count. "Supported a 40-person engineering org" is weaker than a percentage but far stronger than "assisted various teams." Never invent a figure. Interviewers probe numbers, and a fabricated metric collapses your credibility in one question.
Rewrite each bullet to lead with the outcome or the scale, then the action. Hiring managers skim the first four to six words of each line; put the number there. "Reduced onboarding time 35% by rebuilding the first-week curriculum for 60+ annual hires" survives a skim. "Responsible for onboarding curriculum" does not.
Keep the ATS From Eating Your Formatting
Applicant tracking systems convert your file to plain text and then search it. Anything that conversion drops is invisible to the filter, regardless of how good it looks on screen. The failure modes are consistent and well documented across vendor help pages: text inside tables and text boxes, content in headers and footers, and multi-column layouts frequently vanish or scramble during parsing.
Build for the parser first. Single column, top to bottom. Standard section headings — "Experience," "Education," "Skills" — because the software looks for those literal words. Contact details in the body of the document, never in the header. Dates formatted consistently as month and year, since inconsistent formats break date-range parsing.
Then there's the file format question. Many large employers' systems handle PDF without trouble, and a PDF preserves your layout exactly. Smaller employers and some older systems handle .docx more reliably. When the posting doesn't specify, submitting .docx is the safer default; when it explicitly asks for PDF, send PDF. Follow the instruction either way — ignoring a stated format preference is a self-inflicted rejection.
Some job boards and company portals accept a resume and then auto-fill an application form from it. That auto-fill is the parser at work, and it's your free test. If the form pulls your employer names into the wrong fields, your layout has a parsing problem. Fix the document before submitting that version anywhere else.
| Formatting choice | ATS parsing risk | Use when |
|---|---|---|
| Single-column .docx | Low | Default for most applications |
| Single-column PDF | Low to moderate | Posting requests PDF; layout matters |
| Two-column or sidebar layout | High — sidebar content often dropped | Portfolio or direct email to a human only |
| Tables for skills or dates | High — cell text frequently scrambled | Never for the submitted version |
| Header/footer contact info | High — frequently stripped entirely | Never; keep contact info in the body |
| Graphics, icons, skill bars | Moderate — read as blank or garbage | Never; replace bars with skill names |
The verdict is simple: design is for the human, structure is for the machine, and the machine reads first. A plain document with strong content beats a stylish one that arrives in the recruiter's system as scattered fragments.
Match Keywords Honestly Instead of Stuffing Them
Keyword matching rewards precision, not density. The target isn't to repeat a term as often as possible; it's to place each required term once, in a context where it's clearly true of your experience. Recruiters and screening software both flag resumes where a skill appears in a list but never in a bullet — the claim looks decorative.
The method: for each must-have keyword from the posting, write one bullet where that skill is the action, not the noun. If the posting wants "SQL," a bullet reading "Built SQL queries against a 2M-row customer database to isolate churn drivers" proves it. A skills-section entry reading "SQL" alone proves nothing. Both contain the keyword; only one survives a skeptical read.
Then handle the skills section as a scannable inventory, grouped by category, with tool names in their official spelling. This section exists for the parser and the six-second skim — it's a lookup table, not prose. Keep it to skills you can defend in an interview, because every line is an invitation to be asked about it.
Watch for the adjacency trap: a keyword you touch once in passing isn't a skill. Listing "Python" because you ran a script someone else wrote will get you a technical screen you can't pass. The posting's vocabulary should describe what you actually do, and the honest match is usually broader than people assume — "data analysis" covers more real experience than "machine learning."
Use the Six-Second Scan to Place What Matters Most
Recruiters reviewing high volumes of applications spend somewhere in the range of six to eight seconds on an initial pass, a figure repeated across recruiting-industry surveys and consistent with eye-tracking research on resume screening. That's enough time to read your name, title line, current employer, current title, and maybe two bullets. Everything else waits for the second pass, which only happens if the first one raised a hand.
Design for that scan. Your most relevant role — not necessarily your most recent one — should be visible without scrolling and should sit first in the experience section when you're targeting a specific job. Reverse-chronological order is the default and what most systems expect, but a "Relevant Experience" grouping above "Additional Experience" is a legitimate structure when you're pivoting fields.
Within each role, the first bullet carries disproportionate weight. Put the achievement that matches the posting's top priority there. The second bullet supports it. Duties that merely describe the job description you were hired under go last, or get cut.
Leave white space. A page packed edge to edge reads as effort to parse, and a skimmed document gets less of a reader's attention, not more. Margins of half an inch to an inch, consistent spacing between sections, and a clear visual hierarchy of name, then title, then headings, then body — that structure is what lets an eye jump to the right line in six seconds.
Write a Summary Only When It Earns Its Space
The professional summary occupies prime real estate and is usually wasted. It earns its place under one condition: it contains something a reader couldn't infer from the rest of the page. That means a number, a credential, a named domain, or a clear positioning statement.
A working example: "Revenue operations lead with 8 years in B2B SaaS; rebuilt forecasting for a 120-person sales org, lifting forecast accuracy from 62% to 84%." Every clause is checkable, specific, and dense. A failing example: "Results-driven professional with excellent communication skills and a passion for excellence." That sentence fits any candidate in any industry and therefore describes none.
If you're a recent graduate or career changer, the summary can do structural work by explaining the through-line the experience section can't show on its own. "Transitioning from classroom teaching to instructional design; built 40+ asynchronous modules for a 900-student district" connects the dots before the reader has to. Keep it to three lines at most.
For most experienced candidates applying through an ATS, the title line alone outperforms a summary. Space saved goes to an extra quantified bullet, which does more screening work than a paragraph of self-description.
Make Contact Details and Dates Bulletproof
Boring failures kill good resumes. A phone number formatted with spaces instead of dashes can break a parser's field extraction. A typo in your email address is invisible after you've read the document forty times. A missing month on an employment date creates a gap the reader has to guess about, and gaps invite suspicion.
Run this checklist before every submission:
Email address is professional, spelled correctly, and checked — confirm it by sending yourself a test message from the exact document. Phone number includes country code if you're applying across borders, formatted consistently. LinkedIn URL is customized and current, not a string of random digits. Every role has a month and year for both start and end; "Present" for current roles. Employment gaps longer than a few months are either explained briefly in a line or covered by something in the experience section — education, contract work, caregiving stated plainly. File name is "Firstname Lastname – Resume" rather than "resume_final_v3."
The email typo deserves its own warning because it's the most common silent killer. A resume with a broken contact line looks identical to a perfect one on screen, and the rejection happens without a trace.
Frequently Asked Questions
How long should a resume be in 2026?
One page for under roughly ten years of experience; two pages once you have a decade of relevant history or a technical CV with publications. The length itself isn't screened — content density is. A two-page resume with filler loses to a one-page resume where every line carries a number or a named skill.
Does a graphic design or two-column resume really get rejected by software?
Frequently, yes, at employers using older parsers. Workday and Taleo are the usual culprits, and text in sidebars, tables, and headers is the first thing dropped during conversion. Keep a designed version for direct email and portfolio use, and submit a single-column plain version through any application portal.
What if I don't have metrics to quantify my achievements?
Quantify the environment instead: team size, customer count, transaction volume, system count, budget responsibility. "Managed scheduling for a 25-person clinical team across three locations" contains no percentage and still proves scale. Interviewers accept environment numbers; they distrust invented outcome percentages.
Should I include a photo, age, or marital status?
No for the United States, Canada, and the United Kingdom, where those details create legal and bias exposure for employers and get resumes discarded. Germany and parts of Asia have different conventions, so check the target country's norm — a photo on a US application reads as a mistake, not a personal touch.
How do I explain a six-month employment gap?
State it plainly in one line if the resume raises the question — "Career break, caregiving, 2024" — or cover it with contract, freelance, or study entries. Unexplained gaps make readers guess, and guesses run negative. A stated reason ends the inquiry in three words.
Is tailoring every resume worth the time?
Yes, and it costs less than people fear: 15–20 minutes per application to adjust the title line, reorder bullets, and swap skills-section entries. Applying to 10 tailored postings typically outperforms 100 generic submissions, because the tailored version clears keyword screens the generic one fails.
What's the single fastest fix for a resume that gets no responses?
Add the posting's exact job title to your title line and first bullet. If your resume never contains the literal title the employer searches for, you don't surface in applicant tracking system queries at all — the fix is one line and it addresses the most common silent filter.