How Recruiters Search, and How to Be in the Results

Where Do You Actually Show Up in a Recruiter's Search?

You show up when four fields line up: your current title, the plain-language name of your work, your location, and how recently you were active. A recruiter searching a database is running the sourcing half of hiring, and it works on a different mechanism than the screening half most advice is actually written for.

What both halves have in common is that a person types words into a box and the software hands back whoever matched them. Greenhouse's filtering tool, which searches the full text of resumes and internal notes during application review, states that to appear in the results "the keyword from your search must exactly match the keyword in the application" ¹. That is one vendor's wording for one product, and other systems stem words, expand synonyms or match on embeddings. It is still the plain mechanical reason to name your work the way the field names it.

None of that is a resume-score number, and no algorithm is deciding anything about you. A person types a query because they're trying to fill a specific role, and the software returns whoever's profile matches the words they chose.

In the Harvard Business School and Accenture "Hidden Workers" survey of 2,275 senior leaders in Germany, the UK and the US, fielded in early 2020, 63% said they run a recruitment management system, rising to 75% in the US, and more than 90% of those said they use it to filter or rank middle-skills and high-skills candidates before a person looks ². Sourcing and screening often run on the same underlying software, which is part of why the two get confused.

But the query a recruiter types to find you is not the same event as the filter your resume runs through after you've applied. A search is initiated by a person looking for people, before anyone has decided to reject anyone; a screen runs against applicants who already opted in by applying. Writing for one well doesn't automatically write for the other, and advice that treats them as one problem tends to serve neither.

What each of the four fields has to carry:

• An accurate, current job title, in the field's own vocabulary
• Location, set to where you'd actually work
• Recency: when the profile was last updated or active
• The plain-language name of your work, not an internal title

Don't Stuff Your Profile, Match It

Put the terms where the work is described rather than in a band at the top. Workday's own documentation states its skills-suggestion feature reads the entire uploaded resume, not only a Skills section, when inferring what to recommend ³. A term inside a real bullet registers.

A wall of unearned keywords registers too, in the sense that the search still returns it, and that's exactly the problem: being returned by the query was never the hard part. Terms with no supporting sentence around any of them read as padding to the recruiter who opens the result a moment later, and that reader is the one deciding anything.

Employers running keyword-based screening are told the exact-match era of that particular tool is already ending, because writing to a scored vocabulary now costs anyone seconds with a model open. A recruiter's search survives that shift better than a screen does, since a person still reads what comes back rather than a rule deciding automatically, but a profile obviously written for the machine reads exactly as generic to the person as it does to the query. The match gets you into the room. It doesn't get you a callback once you're in it.

Write the One Line That Gets You Opened

Write your headline in the vocabulary a recruiter would type into the search box, not the internal title your employer gave the role. "Senior Backend Engineer, Payments" is a string a hiring team is actually typing. "Member of Technical Staff II" is one almost nobody types outside your own company, however senior it sounds internally.

The summary line under the headline does different work: it's what a recruiter reads before deciding whether to open the full profile. One sentence naming the kind of problem you work on, in plain language, does more there than a paragraph of adjectives, because it answers the question the recruiter is actually holding: is this the kind of person I'm looking for.

The same rule holds for any AI-fluency claim you add to that headline or summary. Employers checking a line like "uses AI daily" are told to verify it in about ten minutes, off an artifact rather than the claim itself, so a vague line adds a keyword without adding anything a ten-minute check would confirm. Name the tool, the task, and something you could point to if asked, since that specificity is what survives the ten minutes, and the vagueness is what a stuffed profile can't.

When Inbound Won't Carry Your Search

Inbound sourcing favors certain titles, seniorities, and locations by design, and for some roles and career stages it will never carry a search on its own. A recruiter's query is built out of titles, years and specifics, and an early-career profile has less of each, so a thin work history gives a search little to match against however the profile is worded. Treat inbound as a complement to applying, not a replacement.

Which employer you're trying to reach also matters more than which software sits behind their hiring. In a correspondence study that sent more than 83,000 fictitious applications to entry-level jobs at 108 of the largest US employers, which third-party application-system vendor a firm used explained only 0.1% of the variation in racial contact gaps between firms, and the authors conclude that screening algorithms are unlikely to drive the differences they measured between employers ⁴. The software a company bought is rarely the thing standing between a strong candidate and a reply. Where you're looking, and whether that employer is looking at all, more often is.

See a sample report >