The other half of the ATS conversation, less covered in candidate-facing content: what the recruiter actually does with the system after the parser finishes. The parser extracts your data; the recruiter then opens a dashboard, applies a few filters, and starts triaging. Most candidates picture that triage as more thorough than it is.

This is the recruiter side of the ATS piece. Knowing what filters they typically use, how much time they spend per candidate, and what their workflow actually looks like changes how you should write your resume — particularly the parts most candidates over-engineer.

What a recruiter actually does in the dashboard

The default flow for most recruiters reviewing a role:

A few things to notice in the workflow:

• The default sort is rarely by match score. Recruiters often sort by date (newest first), by referral status, or by source (referrals + paid campaigns first). The "ranked-by-AI" picture that ATS marketing implies is real for some platforms but not the dominant workflow.
• Most candidates never have their resume opened. The recruiter scans the dashboard row, makes a yes/maybe/no judgment based on row-level data (title, years, top keywords), and moves on. The full document gets opened roughly 1 in 5 times.
• The "maybe" column is purgatory. Candidates who land there don't get rejected, but they also don't advance unless the yes pile runs thin. Most never hear back.

The implication: your resume's row-level data — title, parsed years of experience, top-matched keywords — does most of the work. The bullets matter when the recruiter opens the document, but the open is contingent on the row being interesting first.

Which filters recruiters actually apply

A common candidate worry: "What if a recruiter sets a filter that excludes me?" Worth knowing what filters they actually set, not what filters the ATS supports.

The hierarchy in practice:

Years of experience is the single most-applied filter. It's also the one most likely to silently drop candidates because of parsing problems — if your work history dates parse incorrectly, the system computes the wrong number and the filter excludes you. This is fixable; see resume mistakes that get an auto-reject for the date-format guidance.

Location and work authorization are routine for geo-specific or US-only roles. Even "remote" roles often have hidden filters — same time zone, specific country list, or sometimes a state list (because of tax/employment law).

Keyword match is more tactical than candidates assume. Recruiters set 2–4 specific must-have keywords for a role, often based on what the hiring manager flagged. The much-discussed "ATS keyword scoring" is mostly happening at the ranking level (the score the dashboard shows), not the filter level. A high score helps your row stand out; the filters knock out resumes that miss the manual must-haves.

Education-level filtering is less common than candidates expect. A "Bachelor's required" line on a posting is usually not enforced as a hard filter unless legal requirements demand it (immigration sponsorship, regulated industries, government). For most roles, the degree line is hiring-manager preference; recruiters fill the role with the best available candidate, degree or not.

How much time they actually spend

A useful frame for how to write a resume: how much time will the recruiter actually spend on it?

Seven seconds on the dashboard row. One in five candidates gets the resume opened. About thirty minutes per day per role across all inbound. That's the budget your resume is competing for.

Specific implications:

• Optimize for the row, not the page. The information that appears in the dashboard row — name, most-recent title, parsed years, top-matched keywords — does the gatekeeping work. Make those parse correctly.
• The first bullet of your most recent role is the highest-leverage line on the page. When a recruiter does open the full resume, they read top-down. The first bullet under your most recent title carries weight far out of proportion to the others.
• Bullet length matters. A bullet that runs three lines gets read once at most. A two-line bullet gets read fully and has its content remembered. A one-line bullet feels insubstantial. Aim for two lines, max twenty-five words.

What recruiters look at on the dashboard row

The typical dashboard row shows:

• Name
• Most-recent title (parsed from the resume)
• Years of experience (calculated from date ranges)
• Education (top entry only)
• Top 3–5 matched keywords (ATS-computed)
• Application source / referral flag
• A button to open the full resume

Each of these is a place where parsing problems silently hurt you. If the parser misread your most-recent title, the row shows the wrong thing. If your dates didn't parse, the years field is blank or low. If your skills section is unconventional, the matched-keywords list is sparse.

The fix is the same as the parsing piece: clean format, real section headings, standard date formatting. The benefit shows up at the dashboard level, where most decisions are actually made.

What recruiters don't look at

Some elements that get a lot of resume-advice attention have less impact than candidates assume:

• Resume design. Almost no recruiter dashboards show the actual rendered resume on the row. They show the parsed data. Design choices that don't affect the parsed output are invisible at the gatekeeping step.
• Cover letters. Most ATS dashboards put cover letters one click away from the resume — and most recruiters don't take that click unless something else has flagged the candidate as interesting. Spend the time on the resume instead.
• Custom answers to application questions. Many recruiters skip the optional fields entirely on first scan. The hiring manager may read them later if you advance.
• Photos. Some companies have explicit anti-bias policies that flag photos. Most parsers strip them. Net effect is small or slightly negative.
• References. Almost never read at the application stage. Save the page real estate.

What this means for the resume

Take the recruiter workflow seriously and the implication for your document is:

1. Make sure parsing works. Your dashboard row depends on it.
2. Front-load the most relevant role. Reverse chronological, with your most relevant work in your most-recent position when possible.
3. Make the first bullet under your most recent role the strongest one — most relevant to the target, with a concrete outcome.
4. Use the keywords from the posting in places where they're true. The dashboard's "top matched keywords" list shows the recruiter what you've actually done that matches their must-have list.
5. Don't over-design. The recruiter doesn't see most of it. The parser does, and the parser prefers plain.

The 7-second dashboard scan and the 1:5 open rate aren't insults. They're the mechanics of triaging hundreds of applications a day. Resumes that account for them — that put the right information in the right place at the right level of polish — get more callbacks than resumes that try to win the long-form read first.