Resume Optimization Guide

What an ATS actually does with your file.

An applicant tracking system turns your resume into structured fields, stores it against the requisition, and lets a recruiter search and filter the pile. It does not auto-reject on its own. It decides what a human sees first, and how far down the list you sit.

If you applied through a company careers page, or through a form hosted on Workday, Greenhouse, Lever, iCIMS, Ashby, SmartRecruiters, or Taleo, your file went into an applicant tracking system. Three things happen to it, in this order.

1. Extraction. The parser pulls the text out of your PDF or Word file and tries to sort it into fields: name, email, phone, one record per job with an employer, a title, and a date range, then education, then skills.
2. Storage. Those fields become a candidate record attached to the requisition you applied to, alongside everyone else who applied.
3. Retrieval. A recruiter searches and filters that pile. By keyword. By required skill. By location, work authorization, degree, years in a title. Many systems also show a match indicator against the job description.

Retrieval is the part people misunderstand. The software is not sitting in judgment on your career. It is a search box over a few thousand records, and the recruiter is looking at page one. So there are only two ways to lose here, and both are fixable.

• Parse failure. Your data landed in the wrong field, or nowhere. Your last two years show up as an empty work history. No search will find you, because there is nothing to find.
• Search failure. Your data parsed perfectly and you simply did not use the words the recruiter typed into the box. You are in the pile. You are on page nine of it.

The next two sections are one fix each. Formatting solves parse failure. Keywords solve search failure.

Go deeper

Formatting that survives the parser.

One column, real text, standard headings, one date format. Sidebars, tables, text boxes, and images of text are what break extraction. You can check your own file in about a minute by copying the text out of it and reading what comes back.

The one-minute test, before any of the rules

Do this before you change anything. It tells you whether you have a problem at all.

1. Open your resume PDF in any viewer.
2. Select all. Copy.
3. Paste into a plain text editor. Notes on a Mac in plain text mode, Notepad on Windows, or any code editor. Not Word, and not Google Docs, because both will helpfully restore some of the formatting you are trying to see through.
4. Read the result top to bottom.

That is roughly what the parser sees. If your job titles arrive separated from their employers, if a whole sidebar lands in the middle of your work history, if dates are orphaned on their own lines, if your name is missing entirely, then a parser will make the same mistake and you will not know it happened. Fix what the test shows you, then apply the rules below to keep it fixed.

The rules that matter

• One column. A two-column layout is a visual convention, not a structural one. Extraction can run straight across the page and interleave your skills list into your job history, or read one column after the other and put your 2019 role after your 2026 role.
• Real text, never an image of text. If your name or your headline is part of a designed graphic, it extracts as nothing. Same for a screenshot of a skills chart and same for a scanned copy.
• Contact details in the body of page one. Email and phone placed in a Word header or footer can be dropped, because the parser may read only the document body. Put them in the first two lines of the page itself.
• Standard headings, spelled the standard way. Experience. Education. Skills. Projects. Certifications. A parser matches headings against a known list. “Where I’ve Been” is not on it, and everything underneath it goes unlabeled.
• One line per job, in a fixed order. Title, employer, location, dates. Use the same order in every entry so the parser can learn the shape of your file from the first one.
• One date format everywhere. Pick Mar 2023 to Present or 03/2023 to Present and use it in every single entry. Mixing formats is the most common reason a role parses with no end date.
• No tables, no text boxes, no columns of skills. A skills table often flattens into one unreadable run, and a text box can be skipped entirely. A comma-separated line under a Skills heading is boring and it works.
• Ordinary fonts and ordinary bullets. Calibri, Arial, Helvetica, Georgia, Times New Roman. A standard bullet character. Decorative glyphs and emoji can extract as replacement characters in the middle of your sentences.
• PDF unless the form asks for .docx. Follow the form when it tells you. Name the file First-Last-Role.pdf, because that filename is what a recruiter sees in a folder of forty attachments called resume_final_v3.

One thing not to do: never hide keywords in white text or at one point. A parser extracts text, not color, so the hidden words land in the output exactly like the rest of your resume, and they are visible the moment anyone opens the plain-text view. It reads as deception on the one document that is supposed to be your own account of your work.

Go deeper

Pull the keywords out of the job description.

The job description is the search the recruiter is going to run. Strip it to Responsibilities and Requirements, mark the noun phrases you can actually defend, and use the employer's exact wording. Six to ten terms per application is the working number.

Do this the same way every time so it takes ten minutes instead of an hour. Seven steps.

1. Paste the posting into a blank document. Plain text. You are about to cut most of it.
2. Delete the parts nobody filters on. The company boilerplate paragraph, the benefits list, the equal opportunity statement, the sentence about being a fast-paced environment. Keep Responsibilities, Requirements, and Preferred Qualifications. That is usually a third of what you started with.
3. Mark every noun phrase that names a thing. A tool, a system, a process, a regulation, a customer type, a deliverable. Cross-functional stakeholder communication. Incident response. Terraform. SOC 2 evidence collection. Medicare Advantage claims. Series A pipeline.Skip the adjectives. Nobody has ever searched an ATS for “self-starter.”
4. Mark the verbs the role owns. Migrate, forecast, triage, onboard, reconcile, instrument. These tell you what the bullets should start with.
5. Rank by where the term appears, not how often. A term in the job title, in the first responsibility, and again in Requirements is what the recruiter is filtering on. A term that shows up once at the bottom of Preferred Qualifications is decoration. Take the top six to ten.
6. Sort each one honestly.Done it. Touched it. Never done it. Only the first two are allowed onto the resume, and the second group gets the wording it deserves: “supported” is not “owned.” The third group you leave off and go learn.
7. Use the employer’s exact string.If they wrote CI/CD, do not write “continuous integration.” If they wrote RN license, do not write “nursing license.” If both spellings are common in the field, write the posting’s version and put the other in parentheses once. A search box does not know they are the same thing.

Then place them where both audiences hit them: the title line under your name, the first three bullets of your most recent role, and the skills line. Anything below the fold of page one is doing less work than you think.

The limit on all of this is simple and it is not negotiable. Every term you add has to be something you can be asked about for twenty minutes by someone who does it for a living. Keywords get you into the search results. The interview is where a padded one dies.

Rewrite one bullet, before and after.

Most resumes describe duties. Hiring managers are reading for evidence. The shape that works is verb, scope, method, measured change, in one or two lines, and it survives being read in four seconds.

Here is the formula, then three examples. The examples are illustrations of the shape. The numbers in them are made up for the purpose. Yours have to be real.

[Past-tense verb] [what you did], [the scope], [how you did it]. [What measurably changed, and over what period.]

What changed in each one

• The duty became an action.“Responsible for” and “helped with” and “worked on” describe a job description. Cut all three on sight and start with the verb.
• Scope arrived. Four accounts. The only agent on the queue. One team of four. Scope is what tells a reader whether your experience is the size of theirs.
• The method is in there. A shared editorial calendar. Fourteen macros. Terraform. This is where your keywords go, and it is the sentence a hiring manager builds an interview question out of.
• Something moved, and it says over how long. A number with no time window is half a claim.

If you genuinely have no metric

Plenty of real work does not come with a dashboard, and inventing a percentage to fill the gap is the one move that can end an interview. Use scale instead of change. How many, how often, how big, for whom. “Closed the month for three legal entities.” “Carried the on-call pager one week in four.” “Supported 40 accounts, the largest at 900 seats.” Specific and true beats impressive and unverifiable, every time, because the second one has to hold up in a room.

Keep each bullet to one or two lines. Three to five bullets per role, most recent role longest. A bullet that wraps to four lines is a paragraph, and a paragraph on a resume does not get read.

Check the score before you submit.

No applicant tracking vendor publishes a shared 0 to 100 scale, so no tool can tell you an industry-standard number. What a checker is good for is the gap list: paste your resume and the specific job description you are about to apply to, and read what it could not find.

Be careful with resume scores, including ours. There is no common scale across applicant tracking systems, no published threshold, and nothing that converts a number into odds of a callback. Any tool reporting a percentage is reporting its own reading of one resume against one job description, and a different tool will give you a different number on the same file.

Orbyt’s free resume score works like that too. It compares your resume against a job description you paste in and returns a match figure, a short list of fixes, and the keywords from the posting it could not find in your file. Treat the figure as a before-and-after on your own file, not as a standard and not as a prediction. The missing-keyword list is the part worth your time.

How to actually use it

1. Paste the resume version you are about to submit, and the specific posting you are about to submit it to. Scoring a generic resume against a generic description measures nothing.
2. Read the missing-terms list first. Ignore the number on the first pass.
3. Fix only the gaps that are true of you. Every other gap is a note about a job you should think twice about, not a hole to fill with a word.
4. Run it again. The delta between the two runs is the only comparison the number is good for.

One thing a keyword checker cannot do is tell you your file failed to parse, because it reads the text you pasted rather than the PDF you are about to upload. That is what the copy-and-paste test in the formatting section is for. Run both. They catch different failures, and the parse one is the expensive one.

Go deeper

Tailor without starting over.

Keep one master resume with everything in it and never send that file. Per application you copy it and cut it down. Five things change; employers, titles, dates, and numbers never do.

A single generic resume cannot rank well against different job descriptions, because the terms in them are different. But rewriting from a blank page for every application is why people give up on tailoring by the fourth one. The master file is what makes it sustainable: everything you have ever done, in one document, far too long to send.

Your master holds every role, every project, every certification, and every number you have. Ten pages is fine. Nobody sees it. Each application is a copy of it with the irrelevant parts deleted, which is a different and much faster job than writing.

The five things that change, in order

1. The title line under your name.Mirror the posting’s title when it is honest for you. If they are hiring a Solutions Engineer and that is what your last job was, say Solutions Engineer, not “Technical Problem Solver.”
2. The summary, if you keep one. Two sentences, rewritten to this role. If you are not going to rewrite it, delete it. A generic summary is the most skippable inch of a resume.
3. The order of bullets inside your most recent role. Most relevant to this posting goes first. This is the highest-value edit on the page and it costs about thirty seconds.
4. Six to ten keyword swaps. The terms from the previous section, in the wording the posting used.
5. The skills line, reordered.Same list, the posting’s terms at the front.

What never changes: employers, titles, dates, degrees, and the numbers in your bullets. If any of those move between applications, that is not tailoring.

Keep track of which version went where

Save each one as First-Last-Company-Role.pdf and keep the file. Three weeks later a recruiter calls about a role you barely remember applying to, and you need to know which version of your history they are looking at while they talk. Log the company, the date, the posting link, and the file you sent. A spreadsheet does this. Orbyt’s pipeline tracker does it with the follow-up reminders attached. The tool is secondary. Not having a record is the actual failure.

Go deeper

When a cover letter earns its place.

Write one when you have something specific to say: a referral name, a career switch, a gap you would rather frame yourself, or a problem in the posting you have solved before. A generic cover letter is worse than none, because it proves you had nothing specific.

Write one when

• The form requires it. Always, no exceptions, no blank box.
• Someone referred you. Their name goes in the first sentence, where it cannot be missed.
• You are changing industry or function, and your resume alone reads like a mismatch. The letter is where you explain the throughline the bullets cannot.
• You have a gap, a layoff, or a short stint you would rather frame in your own words than leave to someone else’s guess.
• The posting names a specific problem and you have solved that exact problem before.
• It is a small company or an early team, where one person reads everything that comes in.

Skip it when

The field is optional, the posting is generic, and you have nothing to say that would not be equally true of two hundred other applicants. That letter costs you twenty minutes and adds a paragraph of nothing to your file. Put the twenty minutes into the bullets instead.

The shape, four paragraphs, under 200 words

1. One sentence on why this job.Referral name here if you have one. Never “I am writing to express my interest in the position of.”
2. The problem, in your own words. Two sentences restating what the posting says the role is actually for. This is the part that proves you read it.
3. The one time you did that exact thing. With the number. One story, not a summary of your resume. The resume is attached; do not narrate it.
4. What you want and how to reach you. One sentence. Done.

If you draft with an AI, the edit that matters is subtractive: delete every sentence that would be true of any candidate for any job. What survives is the letter. Usually it is shorter than what you started with, and that is the improvement.

Go deeper

The rest of the stack.

The resume is one artifact in a system. What decides your week is how many postings you can tailor for properly, whether you can tell which version went where, and whether follow-ups happen without you remembering them.

A perfect resume submitted into a pile you are not tracking still loses to a good one you followed up on. Three things sit around this document and each one is worth more than another hour of formatting.

• A record. Company, role, date applied, posting link, which resume version, next action, date of next action. Anything that holds those seven fields is enough.
• A tailoring loop you will actually repeat. Master file, keyword pass, score check, submit. If your loop takes an hour you will stop doing it, and untailored volume is how people end up sending hundreds of applications into nothing.
• Follow-ups on a clock, not on memory. A note to yourself for seven days after you apply, and again after each interview round.

If you want the whole search in one place, that is what Orbyt Jobs is for, and the free tier is free with no card. If you would rather run it out of a spreadsheet, run it out of a spreadsheet. Keeping the record is the part that matters.

Go deeper