How Applicant Tracking Systems Read Your CV or Resume
A Practical Guide to Parsing, Keywords, Formatting and Human Review
By Oravanto
Applicant tracking systems are often described as invisible gatekeepers that reject resumes before a person can read them. That explanation is simple, memorable — and frequently misleading.
An ATS is not one universal piece of software, and “beating the ATS” is not a reliable resume strategy. Employers use different platforms, configurations and recruitment workflows. One system may parse a resume into structured fields. Another may let recruiters search the full text for exact keywords. A third may apply screening rules to application questions. Some platforms now also offer AI-assisted matching, keyword suggestions or broader recommendation tools. Human review still sits inside that process, but it may occur at different points.
The practical goal is not to manipulate a machine. It is to produce a resume that can be processed cleanly, searched accurately and understood quickly by a recruiter or hiring manager.
Important: “ATS-friendly” is a useful search term, but it is not a certification. No format can be guaranteed to perform identically across every employer, parser and recruitment platform.
What Is an Applicant Tracking System?
An applicant tracking system is recruitment software used to collect applications, create candidate records, organize hiring pipelines and support recruiters, hiring managers and administrators. Depending on the product and the employer’s configuration, it may also support career-site applications, resume parsing into structured fields, custom screening questions, automated application rules, full-text and Boolean candidate search, filters by location or skill, candidate tagging, interview scorecards, and AI-assisted matching or keyword suggestions.
Oracle’s recruiting documentation describes candidate searches using keywords, Boolean expressions and fields including job title, employer, skill, education and resume text. Greenhouse documents full-text resume search, keyword filtering, application rules and candidate-review workflows. SAP SuccessFactors similarly supports candidate searches across profile and resume data. The differences between these products are exactly why universal ATS claims should be treated cautiously.
What an ATS Does — and Does Not Do
The term ATS is often used as though parsing, screening, ranking and rejection are the same function. They are not.
Function What it means What the candidate should do
Application capture The system stores the application, attachments and responses. Complete every required field accurately and follow the employer’s instructions.
Resume parsing Software extracts text and attempts to place it into structured fields. Use clear labels and a layout that doesn’t hide essential information.
Screening rules Answers to application questions may trigger tags, advancement or rejection. Answer truthfully; resume keywords cannot override a disqualifying response.
Search and filtering Recruiters may search resume text, fields or application data. Use recognized role terminology and relevant keywords in natural context.
Matching or ranking Some systems prioritize or recommend candidates using configured criteria or AI. Build clear evidence of fit rather than trying to maximize an unknown score.
Human review Recruiters and hiring managers assess the application and decide what happens next. Write for a person: relevance, credibility and achievements still matter.
A parser can misread a resume without rejecting the application. A recruiter can find a candidate through a keyword search without the system “scoring” them. A screening question can reject an applicant even when the resume is excellent. Keeping these functions separate leads to better decisions.
Phase 1: How an Application Moves Through an ATS
The sequence varies, but most online applications involve four broad stages: record creation, parsing, screening and review.
Step 1: The Application Record Is Created
When you apply through an employer’s career site, the ATS creates or updates a candidate profile and associates it with the vacancy. The record may hold more than the resume: application answers, source information, work authorization, salary expectations and other employer-defined fields — so inconsistency between the uploaded document and the online fields can create doubt or require manual correction. Before submitting, check that your name, employment dates, job titles, education and any linked profiles match across the entire application.
Step 2: The Resume May Be Parsed into Structured Fields
Resume parsing is the extraction of information from an uploaded file into structured data — name, employers, titles, dates, qualifications and skills — used to populate a profile or form. It is designed to save time, not to render a final judgment on your suitability, and it can be partial or inaccurate. Greenhouse advises recruiters to verify parsed information and documents several causes of unsuccessful parsing, including image-only resumes, graphics, word art, complex tables, headers and footers, text boxes and columned layouts. SAP’s documentation expressly states that resume parsing isn’t always 100% accurate.
See Greenhouse Support on unsuccessful resume parsing and
SAP SuccessFactors guidance on resume parsing.
A failed parse doesn’t necessarily mean the application disappears. In some systems the file stays attached and a recruiter can still view it — the risk is that searchable fields are incomplete or the recruiter has to work harder to understand the document.
Step 3: Screening Questions May Trigger Rules
Many candidates assume rejection comes from the resume. In practice, an application question may be the decisive factor. Employers can ask whether you hold a required license, are authorized to work in a location, can meet a schedule, or are willing to travel — and some platforms let configured responses trigger automatic rejection, tagging or advancement. Greenhouse, for example, documents auto-reject rules based on answers to yes/no, single-select or multi-select questions.
See Greenhouse’s application-rules overview.
Practical implication: A resume cannot compensate for an inaccurate or disqualifying application answer. Read each question carefully, answer truthfully, and distinguish “required” criteria from preferences.
Step 4: Recruiters Search, Filter and Review
Once applications are available, recruiters may review them in sequence, filter into subsets, search full text or structured fields, or prioritize candidates using configured tools. The search logic isn’t uniform: Greenhouse documents exact keyword matching in its talent-filtering workflow, with required terms acting as AND conditions and preferred terms as OR conditions. Oracle supports keyword and Boolean searches across fields such as job title, employer, degree, skill and resume text. Some platforms also suggest search terms or provide broader matching and recommendation tools, but the exact behavior depends on the product and the employer’s configuration.
See Greenhouse Talent Filtering and
Oracle Candidate Search.
The conclusion isn’t that you must predict a secret algorithm. It’s that widely recognized role terminology should appear clearly in the document, supported by evidence a person can evaluate.
Phase 2: Write for Searchability and Human Evidence
Good ATS-conscious writing is not a list of keywords. It’s accurate professional language placed where both a search function and a recruiter can make sense of it.
Step 5: Read the Job Description as a Requirements Document
Before tailoring, separate the job description into four categories: core outcomes (what the person is expected to improve or own), required capabilities (technical knowledge, systems, qualifications), operating context (team size, geography, reporting line) and screening criteria (work authorization, licenses, mandatory credentials).
Don’t treat every phrase as equally important — a capability repeated in the title, summary and responsibilities usually matters more than a generic line in the employer-brand section. Mark each requirement as one of the following:
Priority Meaning Resume response
Essential Presented as mandatory or central to the role. Make the evidence prominent; use the employer’s recognized terminology.
Important Appears repeatedly or supports a major responsibility. Include where it genuinely applies, within an achievement or scope statement.
Supporting Strengthens fit but isn’t central. Include only if it adds value without crowding out stronger evidence.
Not evidenced You don’t possess or can’t defend it. Do not add it. Address the gap through transferable evidence instead.
Step 6: Use the Keyword–Context–Evidence Framework
The strongest keyword strategy has three parts: the recognized term, the context in which you used it, and evidence of your level or result.
Vacancy requirement Keyword or phrase Evidence in context
Budget ownership Budgeting and Forecasting Led annual budgeting and quarterly forecasting across seven departments
Systems / reporting tools Power BI Built Power BI dashboards for monthly performance and variance reporting
Team leadership Team Leadership Managed and developed an eight-member finance team
A keyword alone tells a search function you might be relevant. Evidence next to it tells a recruiter you actually are. The objective isn’t to “game” an ATS — it’s to make genuine fit easier to identify and evaluate.
If translating your job description into the right keywords and evidence is the part that stalls you, Oravanto’s professional CV and Resume Writing Services build this framework into every document rather than leaving you to reverse-engineer it alone.
Step 7: Handle Synonyms, Acronyms and Job Titles
Recruiters may search for an abbreviation, a full term, or a common synonym. Where space permits, include both forms the first time a term appears — Financial Planning and Analysis (FP&A), Search Engine Optimization (SEO), Profit and Loss (P&L) Management, Accounts Payable (AP) and Accounts Receivable (AR).
Don’t manufacture a new job title merely to match the vacancy. If an internal title is unusual, clarify it without misrepresenting it: Commercial Finance Lead (official title: Senior Finance Business Partner). The clarification must preserve the real title. Changing “Accountant” to “Finance Manager” because the vacancy uses that title would be misleading.
Step 8: Build Skills into the Resume Naturally
Relevant terms serve different purposes depending on where they appear: the headline establishes your target identity, the summary connects seniority and value, core competencies index genuine capabilities, employment experience demonstrates how skills were used, and technical skills lists systems and tools at a defensible level of proficiency. Don’t force the same keyword into every section — strategic repetition reinforces relevance, but mechanical repetition reduces readability and can make a document look engineered rather than credible.
Step 9: Avoid Keyword Stuffing and Hidden Text
Keyword stuffing is excessive repetition without useful context. Hidden-text tactics place keywords in white font, shrink them unreadably, or paste the whole job description into the file. These tactics make the document unpleasant to read, can surface visibly during copying or conversion, may read as manipulation to a recruiter, and still don’t prove the required level of experience even when the term matches.
The better test is simple: would the wording still make sense and remain defensible if a hiring manager asked you to explain it line by line?
The ATS–Recruiter Alignment Test. Before finalizing an important claim, bullet or keyword, run it through two questions: Can the system identify the relevant term — does it, or a recognizable variant, actually appear in a section a parser or search function can read? And can the recruiter see credible evidence behind it — is there a specific, defensible example sitting right next to it? A line that passes only the first is a keyword with nothing behind it. A line that passes only the second is good writing a search function may never surface. The strongest resume content passes both at once, which is exactly what the Keyword–Context–Evidence framework above is built to produce.
Phase 3: Reduce Formatting and Parsing Risk
Formatting risk isn’t binary. A design element that works in one system may parse poorly in another. The goal is to place essential information in the safest structure and reserve visual complexity for where it adds real value.
Step 10: Use Recognizable Section Headings
Standard headings help systems and people locate information quickly: Professional Summary, Core Competencies, Professional Experience, Education, Certifications, Technical Skills. Creative labels such as “My Journey” or “Where I Have Made an Impact” may sound distinctive, but they increase the effort required to classify the content. Distinctiveness should come from the evidence, not from renaming familiar sections.
Step 11: Control Columns, Tables, Text Boxes and Graphics
A single-column layout is the lowest-risk default for online applications because the reading order is obvious. That doesn’t mean every two-column resume fails or every table is prohibited — it means design choices should be assessed by how essential the information is and how easily the file can be extracted.
Risk level Typical elements Practical treatment
Lower risk Single-column text, standard headings, ordinary bullets, clear dates, text-based PDF or DOCX. Suitable as the default online-application version.
Moderate risk Simple two-column layout, restrained tables, icons beside duplicated text. Test extraction and keep essential career information in the main reading flow.
Higher risk Image-only text, complex tables, layered text boxes, information only in headers or footers, word art or heavy graphics. Avoid in the portal version, or maintain a separate clean version.
Greenhouse specifically identifies graphics, photos, word art, complex tables, headers, footers, text boxes and columned layouts as possible causes of partial or unsuccessful parsing. That some other systems can process some of these elements doesn’t remove the cross-platform risk. If you use a two-column format, place employment history, achievements and education in the main column — never the only copy of your contact details, titles or dates inside a decorative sidebar.
Step 12: Present Contact Details, Dates and Employers Clearly
The parser shouldn’t have to infer which date belongs to which employer, or whether a line is a title, company or location.
FINANCE MANAGER
Company Name | Dubai, UAE | January 2022–Present
Keep your name and contact information in the document body, not only in the header or footer. Spell out abbreviated job titles where the abbreviation could be ambiguous, use a consistent date format, and make overlapping positions or concurrent engagements clear. A one-line company description helps when an employer name is unfamiliar.
Step 13: Choose the Right File Format
The employer’s instructions take priority. Current platforms commonly accept both PDF and Word, but support is product-specific — Greenhouse accepts DOC, DOCX, PDF, RTF and TXT uploads, while its separate MyGreenhouse candidate FAQ recommends uploading a PDF for best results within that particular candidate-portal experience. This is exactly why “PDF is always best” and “Word is always safest” are both overstatements.
See Greenhouse’s supported candidate-upload formats and
Greenhouse’s MyGreenhouse FAQ for Candidates.
For a PDF, confirm the text can be selected and copied — a scanned image saved as PDF is still an image and may not parse reliably. For a Word document, remove comments, tracked changes and hidden text before submitting.
Step 14: Test the Resume Before Submitting
You can’t reproduce every employer’s ATS, but you can catch common document problems first:
Copy the full resume into a plain-text editor and check the reading order, headings, dates and bullets.
Open the final file on another device to confirm nothing has shifted or disappeared.
Upload early enough to review the portal’s populated fields, and correct anything editable.
Search the document for the role’s essential terms and confirm they appear in genuine context, not only in a skills list.
Check the filename, hyperlinks and contact details; remove comments and tracked changes.
Keep a clean alternative version available if the portal rejects or badly parses the file.
Important: If a portal populates your work history incorrectly, don’t assume the recruiter will repair every field. Correct the application record wherever possible before submitting.
Prefer to build it yourself? Explore Oravanto’s available CV templates and role-specific resources, and select the format suited to your application channel. For online portals, choose an ATS-conscious design and still test the final document in the actual portal.
Phase 4: ATS Myths That Distort Good Resume Writing
Fear-based ATS advice often turns a practical document problem into a fictional contest between the candidate and a machine.
Myth 1: “Most resumes are automatically rejected by the ATS.” Some applications are auto-rejected because of configured screening rules; others are filtered, searched or reviewed manually. There is no universal rejection process across every employer and system.
Myth 2: “A single ATS score tells you whether the resume will pass.” Commercial checkers use their own assumptions. Employers use different systems, fields and configurations. A score can identify possible gaps — it isn’t an employer-issued certification.
Myth 3: “Copying the job description guarantees a match.” Copied language may increase term overlap, but it doesn’t establish credibility or results, and it can make the resume repetitive and inaccurate.
Myth 4: “White-font keywords are invisible and effective.” Hidden text can surface during conversion, copying or review, and it creates an integrity problem.
Myth 5: “Every ATS rejects columns, tables and PDFs.” Systems vary — some process these elements, others read them partially or out of order. The right approach is risk management and testing, not an absolute prohibition.
Myth 6: “The ATS decides who gets hired.” Recruiting software supports a workflow. Hiring decisions involve configured rules, recruiters, hiring managers, interviews and organizational judgment.
Myth 7: “More keywords are always better.” More terms can weaken focus. The best resume prioritizes the capabilities central to the role and supports them with evidence.
Myth 8: “An ATS-conscious resume must look plain or unfinished.” A clean resume can still use strong typography, spacing, hierarchy and a restrained accent color. Simplicity and professionalism are compatible.
Phase 5: Career Situations and International Applications
The ATS principles stay the same, but the content strategy changes with your career history, seniority and target market.
Career changers shouldn’t imitate the target job description as though the transition has already happened — build a credible bridge instead. Use the target role’s terminology where you can support it through transferable evidence, recent qualifications or adjacent projects. A finance professional moving into data analytics might legitimately use Power BI, dashboard development and forecasting, but shouldn’t claim data-engineering ownership without evidence. A combination format can help by presenting relevant capabilities before the full chronological history, while still keeping employers and dates transparent.
Employment gaps and non-linear careers should never be concealed through unusual formatting — ambiguity creates more risk than a clearly presented gap. Where explanation is needed, use neutral, accurate wording focused on relevant activity (study, caregiving, consulting, professional development), and keep it consistent with anything the online application separately requests.
Managers and executives often write in broad leadership language that’s difficult to search and difficult to evaluate. Terms like transformation, strategy and commercial leadership need to connect to scale and outcomes — an executive resume should still contain recognizable functional terms (P&L management, board reporting, M&A integration, digital transformation) where relevant, but must show enterprise scope and impact rather than becoming a senior-level keyword list.
Creative and design-led professionals don’t need to abandon visual presentation — they need to separate the purposes of different documents. Keep a clean online-application resume that establishes experience and achievements, then link to a portfolio or use a more visually distinctive version for direct outreach and interviews. The portfolio should carry the design burden; the ATS version should make the professional case without requiring the system to interpret the design.
Multilingual and international applications depend heavily on the platform. Greenhouse documents full resume-parsing support for numerous languages including Arabic, English and French; SAP SuccessFactors lists a different supported-language set and notes its own parsing limitations; Oracle can rely on configured partner services and recommends testing parser performance for languages like Arabic in relevant implementations. See Greenhouse’s non-English parsing support and Oracle’s multilingual support guidance. Apply in the language the employer requests, use terminology recognized in the target market while preserving accurate titles, and test bilingual or right-to-left documents especially carefully.
Across the United States, Canada and multinational GCC employers, online applications are common and an ATS-conscious version is useful. In the GCC, direct email, referrals and recruiter outreach also remain important, so a visually refined version alongside the portal version can be genuinely valuable.
Phase 6: The Oravanto ATS Resume Self-Audit
Before submitting, review the document across six areas.
Targeting and relevance
Is the target role clear within the first section?
Does the summary reflect the vacancy’s central outcomes rather than generic strengths?
Are the most important requirements supported by actual evidence?
Have irrelevant keywords and lower-value details been removed?
Searchability
Are job titles, skills, systems and qualifications written in standard language?
Are important acronyms paired with the full term where useful?
Do essential keywords appear in context, not only in a competencies list?
Can you explain and defend every term included?
Structure and parsing
Are the section headings conventional and clear?
Are the name and contact details in the document body?
Are employers, titles, locations and dates visibly associated?
Does plain-text copying preserve the correct reading order?
Evidence and credibility
Do recent roles show scope, ownership and outcomes?
Are numbers accurate and meaningful?
Does the wording match your actual seniority?
Application consistency
Do the online fields match the resume?
Have screening questions been read and answered carefully?
Have automatically populated fields been checked and corrected?
Final file quality
Does the employer accept the selected file type?
Can PDF text be selected and copied?
Have comments, tracked changes and hidden text been removed?
Have you opened the submitted version for one final review?
A “no” answer doesn’t automatically mean the resume will fail — it identifies a preventable risk or a weakness that may reduce clarity, searchability or recruiter confidence.
A note on online ATS checkers. These tools can be a useful diagnostic — flagging missing terminology or formatting risks you might have overlooked — but they can’t see how a specific employer’s system is configured, which fields a recruiter searches, or how a hiring manager will judge your evidence. Use one to generate questions, not to outsource judgment. A higher score isn’t automatically a stronger application, and rewriting an accurate, persuasive resume just to chase one is a mistake.
ATS-Friendly vs Visually Designed Resumes
The debate is often framed as a choice between an ugly ATS resume and an attractive one that can’t be processed. That’s the wrong choice — the better approach is channel-specific.
Application channel Recommended version
Employer portal or high-volume application Clean, ATS-conscious structure with standard headings and controlled design.
Recruiter email or direct referral A polished professional version, provided the content stays clear and the file opens easily.
Creative or portfolio-led opportunity A concise resume plus a strong portfolio — visual design used deliberately, not as a substitute for evidence.
Networking and interview follow-up A refined presentation version can support personal branding and recall.
The content should stay consistent across versions. The design may change; the facts, dates, titles and achievements should not.
When Professional Help May Be Valuable
Many professionals can build an effective ATS-conscious resume themselves, particularly with a clear target, strong writing skills and time to analyze relevant vacancies.
Professional support may be worth it when your resume contains relevant experience but generates few interviews, your career history is complex or non-linear, you’re moving into a new function or industry, your technical background is hard to translate into business value, you’re targeting management or highly competitive roles, or your resume, cover letter and LinkedIn profile communicate different professional identities. A professional service shouldn’t promise to “beat every ATS” or guarantee interviews — it should improve targeting, structure, keyword relevance, evidence and factual consistency.
Need a professionally written CV or resume? Oravanto develops professionally written CVs and resumes for job seekers, career changers, experienced professionals, managers and executives targeting opportunities across the United States, Canada, the GCC and other international markets. Explore Oravanto’s CV and Resume Writing Services.
Prefer to create it yourself? Explore Oravanto’s available CV Templates and Career Resources, including role-specific CV Kits and CV-and-cover-letter bundles, and choose the format suited to your target role and application channel — an ATS-conscious design for online portals, a more visual option elsewhere.
Frequently Asked Questions
What does ATS-friendly mean?
It generally means a resume is structured so common recruitment systems can extract and search the content with lower risk. It is not an official certification or a guarantee across all platforms.
Does an ATS automatically reject resumes?
Some systems can automatically reject applications based on configured screening rules. Many other applications are searched, filtered or reviewed manually — the exact process depends on the employer.
What is the best ATS resume format?
A clean reverse-chronological format with standard headings, clear dates, text-based content and a straightforward reading order is the safest general default.
Should I submit PDF or Word?
Follow the employer’s instructions. Both formats are accepted by many modern platforms, but support and parsing behavior vary. Use a text-based PDF or clean DOCX and review the uploaded fields.
Can an ATS read two-column layouts or tables?
Some parsers handle them, others read sections out of order or miss content entirely. Keep essential employment history and contact information in a clear single-column main flow for the portal version, and test the actual document — that remains the lower-risk default regardless of which specific elements you’re using.
How many keywords should a resume contain?
There’s no correct number. Include the role’s most important and accurate terms where they fit naturally, then support them through experience and achievements.
Should I copy keywords exactly from the job description?
Use the employer’s recognized terminology when it accurately describes your experience. Don’t copy whole sentences, claim skills you don’t possess, or repeat terms unnaturally.
Can I use hidden white text to add keywords?
No. It’s an unreliable manipulation tactic, may become visible, and can damage credibility.
Do ATS systems read cover letters?
Some systems store cover letters as searchable attachments; others use them mainly for human review. Submit a targeted cover letter when requested or when it adds meaningful context.
How do I know whether my resume parsed correctly?
Review any fields the portal populates, check the plain-text reading order, and correct errors before submitting. Keep an alternative clean version available.
Are ATS practices the same in the US, Canada and the GCC?
No. Employers use different platforms and workflows in every market. Multinational employers often use global systems, while smaller organizations may rely more heavily on direct human review. The clean-document principles remain useful across markets.
Final Thoughts
The most effective ATS strategy is not to write for a machine at the expense of the reader.
Build a document that presents recognized terminology clearly, survives ordinary parsing and search, answers the employer’s requirements, and gives a recruiter credible evidence of your ability to perform the role. Use standard structure where it reduces risk. Tailor the content where relevance matters. Test the actual file. Answer application questions accurately. Keep a separate visual version when the channel justifies it.
A strong resume does not “beat” an applicant tracking system. It moves through the system without losing the professional case it was designed to make.
Primary Sources and Further Reading
This guide was developed using current primary documentation from recruitment-platform providers. Platform functionality can change and may be configured differently by each employer.
Greenhouse Support — Unsuccessful resume parse
Greenhouse Support — Talent Filtering
Greenhouse Support — Application rules overview
Greenhouse Support — Supported candidate-upload formats
Greenhouse Support — MyGreenhouse FAQ for Candidates
Greenhouse Support — Resume parsing with non-English languages
Oracle Help Center — Candidate Search
Oracle Help Center — Enable Multilingual Support
SAP Help Portal — Configuring Resume Parsing
SAP Help Portal — Quick Facts About Candidate Search
Greenhouse Support — Keyword suggestions