What recruiters actually search before they call you
Not a background check, and not nothing either. The specific things that get looked up, in the order they get looked up.

Part of What people find when they search your name
A recruiter with a stack of candidates and twenty minutes between calls does not read your life story. They type your name into a search box, glance at what comes up for somewhere between thirty seconds and two minutes, and go back to the phone. That is the entire event. Anyone picturing a private investigator working through tabs is picturing something that happens to almost nobody, at almost no stage of an ordinary hiring process.
The paranoia around this is understandable and almost entirely misplaced, and the reassurance that usually gets offered instead — "nobody actually looks" — is also wrong, just in the other direction. Somebody does look, briefly and for a specific reason. The useful thing is knowing what that reason is, because it is much narrower than most people assume, and the one thing that actually trips it up is not a bad photo or an old opinion. It is a résumé that does not match what the search turns up.
The search is short and it goes in a fixed order
Ask a recruiter to describe what they do and most will tell you it barely counts as research. It is a sequence, and it is nearly always the same sequence, because it answers one question: is this person who and what they say they are.
First, the name, usually alongside the employer or the role, because a bare name search on anyone with a common name returns noise. Second, whichever professional profile surfaces first — nearly always LinkedIn, since it tends to outrank almost everything else for a personal name, a pattern covered in more detail in what people find when they search your name. That profile gets a quick read: current title, current employer, how long they've been there. Third, if the role or the employer named on the CV isn't obviously confirmed by the profile, a specific check — does this person actually appear to work, or to have worked, where they say they do. Fourth, and only if something in the first three steps looked odd, a broader look at whatever else the name returns.
Most searches stop at step two. A LinkedIn profile that matches the CV, updated recently, with a photo and a plausible history, answers the only question that was being asked. The search was confirmatory, not investigative — it existed to remove a doubt, not to build a case.
The mismatch that actually causes a problem
If there is one thing that turns a thirty-second glance into a real question, it is dates and titles that don't agree with each other. Not a spicy old post. Not a dated profile photo. A discrepancy between what the CV says and what the public record says about the same fact.
This happens more than people expect, usually for boring reasons. A CV says "Senior Analyst, 2021–present" and LinkedIn still says "Analyst" because nobody updated the title after the promotion. A CV lists a role ending in March and the LinkedIn profile shows the next job starting in January, an overlap that reads as either a formatting slip or two things being true that shouldn't both be true. A CV names a division or a legal entity that doesn't match the parent company on the profile, because the person wrote down the brand and LinkedIn has the registered subsidiary.
None of these are lies. Almost all of them are the ordinary residue of updating one profile and not the other, or of a company restructuring after someone stopped paying attention to their own page. But a recruiter who notices the gap cannot tell that from the outside, and the honest response to an unexplained gap is not to reject the candidate, it's to ask about it — which means the mismatch has just spent part of a short call on a clarification instead of on the actual conversation. The fix costs nothing and takes less time than writing this paragraph took: before a job search, open the CV and the LinkedIn profile side by side and make the titles, employer names and date ranges agree exactly. That single hour of housekeeping does more for a first impression than almost anything else on this list, including the things people worry about far more — and it matters for the same reason the CV itself gets skimmed rather than read; the mechanics of that first skim are covered in the seven-second CV scan.
What genuinely isn't being looked at
The reassurance worth actually believing, because it maps to what recruiters describe doing rather than to what would be comforting to hear: nobody at the confirmatory-search stage is reading your last three years of tweets, scrolling your Instagram from university, or forming an opinion about your politics from a comment you left in 2019. That is not because such content couldn't theoretically be found. It's because finding it takes longer than the search is budgeted for, and because it doesn't answer the question the search exists to answer.
This is worth saying plainly because the fear of it produces bad decisions — locking down every account, deleting a decade of posts, scrubbing a personality out of every public profile in case someone reads too much into it. Nearly all of that effort goes toward an audience that, at this stage of the process, isn't there. If something on your accounts is genuinely alarming — evidence of dishonesty, a public dispute with a named former employer, something a stranger would reasonably read as a red flag — that's a different and narrower problem than ordinary personality, and worth addressing on its own terms rather than as part of a general scrub.
Photographs are their own small case worth naming honestly. A recruiter noticing that your LinkedIn photo is a decade old is not a rejection trigger; people age, and everyone knows what a five-year-old headshot looks like. What a current, professional photo does is remove a half-second of doubt at the exact moment someone is trying to confirm you're a real, consistent, present person — the same job the whole confirmatory search is doing. It's a small thing that supports the larger pattern rather than a thing that matters on its own.
Where a background check is a completely different process
The confusion between this quick search and formal screening is common and worth clearing up, because they share almost nothing except both happening to a job candidate.
| Recruiter's search | Formal background check | |
|---|---|---|
| When | Before or right after the first call | After an offer, or late in process |
| Consent | None asked, none needed | Required by law in most jurisdictions |
| Source | Public search results, mainly LinkedIn | Vendor databases, direct employer contact |
| Verifies | Plausibility — does the story hold together | Fact — actual employment dates, actual criminal record where legally checkable |
| Duration | Minutes | Days |
| Record kept | No | Yes, retained by the employer or vendor |
A formal check calls your former employer's HR department and asks them to confirm the dates on file, which is a different kind of verification entirely from a recruiter eyeballing a profile. It can also surface things a search engine cannot see at all — verified qualifications, right-to-work status, in relevant jurisdictions a criminal record — and it happens with your knowledge and consent, usually late in the process, once an offer is close. Treating the early, informal search as if it carries the weight of the later, formal one is the source of most of the unnecessary anxiety here. They are not the same event, and the thing that trips up the second one — an employer who has no record of you working there when you said you did — has nothing to do with anything a search engine would show.
Make the confirmatory search easy on purpose
Once the actual sequence is clear, the response to it is not defensive, it's constructive. The search exists to confirm you're real and consistent; the useful move is to make that confirmation immediate rather than to worry about what else might be found.
That means the same housekeeping already mentioned — matching titles, matching dates, matching company names — done everywhere your name appears publicly, not just on the one profile you remember to update. It means a current photo, because it answers the "is this a real, present person" question before it's even asked. And for anyone whose name is shared with other people, or whose career doesn't read cleanly from job titles alone, it means having somewhere that resolves the ambiguity in one look rather than making a recruiter guess — the case worked through in what to do when you share a name with someone else. None of this is about impressing anyone. A recruiter spending two minutes on a confirmatory search is not evaluating your taste or your prose; they're checking whether the story in front of them holds up, and the entire job of the search, from your side, is to make sure it does.
Questions people ask
- Do recruiters actually Google every candidate?
- Most do a short confirmatory search before or shortly after a first call, usually under two minutes, rather than a deep investigation. It is closer to checking than researching.
- Will an old photo or an embarrassing post from years ago stop me getting hired?
- Rarely on its own. Recruiters are mainly checking that your name, employer and dates line up with what you told them; something odd usually prompts a question in the interview rather than a silent rejection.
- What's the difference between a recruiter's search and a formal background check?
- A recruiter's search is unofficial, unrecorded and done from a phone in a few minutes. A formal background check happens later, with your consent, through a vendor, and covers things a search engine cannot see at all, like verified employment dates and criminal records.
- Should I remove old social media posts before a job search?
- Only if something is genuinely alarming. The better use of the same hour is making sure your current job title and dates match everywhere, since that mismatch is what actually raises a recruiter's eyebrow.