What Recruiters Actually Care About (And What They Don't)

Most job seekers optimize their resume for the wrong person. They polish for the hiring manager — the technical person who will eventually evaluate their skills — when the resume's first reader is almost always a recruiter or an automated screening system.

The recruiter and the hiring manager care about completely different things. Get this wrong and your resume never reaches the person who would actually want to hire you.

This is what 20 years of being on both sides of the hiring table has taught me.

The four stakeholders your resume passes through

Before anyone makes you an offer, your resume typically goes through:

An ATS (Applicant Tracking System). Software. Keyword-matches your resume against the job posting. Ranks candidates. The first cut.
The recruiter. Human. Scans 30-100 resumes per day. Decides which 5-10 to surface to the hiring manager.
The hiring manager. The person who will be your boss, or close to it. Decides who gets a phone screen.
The interview panel. Decides whether you get an offer.

Each stakeholder filters differently. Your resume has to clear all four. Most candidates over-optimize for stage 4 and never get past stage 1.

What the ATS actually checks

Keyword matching, mostly. The ATS scans your resume for terms from the job description and ranks you by overlap.

This is why "tailoring your resume to the job description" actually matters. Not because the recruiter wants you to suck up — because the ATS literally counts keywords.

What clears the ATS:

Exact keyword matches from the job description (if the post says "Splunk," your resume should say "Splunk," not "SIEM tools")
Standard section headers (Experience, Education, Skills) — fancy headers can confuse parsers
Plain text or simple Word formatting — heavy graphics, columns, and tables can break parsing
Common cert acronyms spelled out at least once: "CompTIA Security+ (Sec+)"

What breaks the ATS:

Resume submitted as an image or graphic-heavy PDF
Tables and multi-column layouts (some parsers can't read across columns properly)
Headers in unusual locations
Acronyms only — without expansion, the ATS may not connect them to the keyword
Skills mentioned only in cover letter, not on the resume

What the recruiter actually checks

Recruiters spend 6-30 seconds on the average resume. They're looking for fast disqualifiers and fast confirmations.

They care about:

Clearance status, if the role requires one. "Active TS/SCI" at the top of the resume saves them a phone call.
Location. Remote, hybrid, on-site — does it match? Many recruiters auto-reject based on location even if you'd relocate.
Required certs, present. If the job requires Security+, the recruiter wants to see it without scrolling.
Recency of experience. A two-year gap with no explanation is a flag. Recent relevant experience is gold.
The "stuck below their level" signal. If you have 10 years of help desk and they're hiring for a senior security engineer, they'll skip. Wrong direction.
Job-hopping pattern. Five jobs in five years is a recruiter red flag, fair or not. Provide context if your resume looks like this.

They don't care about:

Your career objective statement. Skip it; nobody reads them.
Your GPA, unless you're under two years out of school.
Hobbies and personal interests sections.
The exact bullet wording for jobs that ended 8 years ago.
Your "soft skills" listed as a section. Show, don't tell.

What the hiring manager actually checks

If your resume reaches the hiring manager, the bar shifts. They're looking for proof of skill and judgment, not keyword matches.

They care about:

Specifics in your job descriptions. "Tuned 200+ detection rules, reducing false positive rate by 40%" beats "Worked with detection rules." Numbers and outcomes matter.
Evidence you've done the work. GitHub repos, blog posts, conference talks, certifications that require demonstration (OSCP, CPTS, SAL1) — these are signal.
Career narrative coherence. Have you been moving toward this role? Or did you randomly apply because the salary looks good? Hiring managers can tell.
Communication ability. Your resume is a writing sample. Bad grammar, formatting inconsistency, or vague descriptions all hurt.
Cultural fit indicators. They're checking whether you're a "smart, gets things done" type or a "loud, demanding, will be a problem" type. Tone matters.

They don't care about:

Generic certifications without supporting work history. CEH alone won't impress them.
A wall of skills listings. Anyone can list "Python, Bash, PowerShell." Show what you built with them.
Padding. They'd rather see one strong page than three weak ones.
Buzzword density. "Synergized cross-functional initiatives" gets ignored.

The shortcut almost nobody uses

Referrals.

Roughly 30-50% of jobs at established companies are filled via internal referral, often before the posting ever goes wide externally. A referral typically:

Skips the ATS entirely
Bypasses the recruiter's auto-reject filters
Gets your resume in front of the hiring manager directly
Often comes with a quiet endorsement that primes the manager to like you

How to get referrals if you don't know anyone:

Show up where the people work. Local DEF CON groups (DC702 in Vegas, DC404 in Atlanta, DC312 in Chicago, etc.), BSides conferences, ISSA chapters, vendor user groups.
Engage publicly. Comment thoughtfully on LinkedIn posts from people at companies you want to work at. Reply to their conference talks on X. Be visible.
Write. A blog with real posts about real work attracts attention from people in the field. See the broader strategy here.
Ask. After three or four substantive interactions with someone at a target company, asking "do you know if there's a place for someone like me at $COMPANY?" is reasonable, not gauche.

Referrals are the single highest-ROI thing you can pursue. One referral can be worth fifty cold applications.

LinkedIn matters more than candidates think

Recruiters actively source on LinkedIn. They search for specific titles, certifications, locations, and skills. If your LinkedIn looks like a half-filled resume, you're invisible.

LinkedIn tactics that work:

Headline with your target role, not your current one. If you're a help desk tech aiming for SOC analyst roles, your headline should signal that: "IT support specialist | Pursuing SOC analyst role | Security+ | TryHackMe SAL1."
Skills section fully populated with skills that match your target job postings.
Experience descriptions with specifics and metrics, just like the resume.
"Open to work" turned on (visible to recruiters only, if you don't want it public).
Activity. Post once a week. Doesn't have to be original — sharing a CVE analysis with a sentence of commentary counts.

LinkedIn rewards activity. A profile that hasn't been touched in a year ranks lower in recruiter searches than a profile that posts weekly.

What candidates over-invest in

More certs. Past Security+ plus one vendor cert in your direction, additional certs have rapidly diminishing returns at the job search stage. Spend the time on a portfolio instead. Skip list here.
Resume design. A clean, parseable resume in standard format outperforms a beautifully designed resume that breaks ATS parsing.
Cover letters. Important but oversold. Most recruiters skim them; many don't read them at all. Spend more time on the resume and LinkedIn.
Applying to more jobs. 200 cold applications usually produces worse results than 20 referred applications. Quality of access beats quantity of attempts.

What candidates under-invest in

The portfolio. A GitHub, a blog, a few conference talks, a CTF placement. Concrete proof of skill matters more than another cert.
The network. The thing you don't have when you need it. Start building it before you're job-searching.
The pitch. "Tell me about yourself" is asked in every interview. Most candidates ramble for two minutes about their resume. A tight 60-second narrative beats this consistently.
The follow-up. A short, specific email 24 hours after an interview, referencing something specific that was discussed, is rare and memorable.

The honest meta-truth

The job posting describes the company's ideal candidate. The recruiter is filtering to a smaller pool that's "good enough." The hiring manager is selecting from that pool the people they'd actually want to work with.

Each stakeholder has different criteria. Optimize for all four in this order: ATS first (clear the filter), recruiter second (get on the surface list), hiring manager third (prove skill), interview panel fourth (prove fit).

Skip any of these and the rest doesn't matter.