Free lesson · The Job Search System

How Recruiters Search and Screen

Easy14 min readjob-searchcareerresume

How Recruiters Search and Screen

Student: Swati, you mentioned something in the last lesson that stuck with me - that the best job search is one where the recruiter comes to you. How does that actually work? What are recruiters doing on their end?

Swati: I'm glad that stuck, because understanding recruiter behavior is one of the highest-leverage things you can learn. Most candidates think of recruiters as gatekeepers - people who decide whether to let you in. That's partially true, but it's incomplete. Recruiters are also hunters. They're actively searching for candidates every single day, and if you understand how they search, you can position yourself to be found.

Let me introduce you to how this actually works. I've worked closely with recruiters at Yahoo, LinkedIn, Stripe, and Google. The tools have changed over the years, but the process is remarkably consistent.

The Recruiter's Day

Before we get into search mechanics, let me give you context on what a recruiter's day looks like. This matters because it explains why they behave the way they do.

A technical recruiter at a FAANG company is typically managing 15 to 25 open roles simultaneously. For each role, they need to source candidates, screen resumes, schedule interviews, coordinate with hiring managers, and manage candidate communication. They're measured on two things: time-to-fill (how quickly they close a role) and quality of hire (how well the person performs after joining).

Student: 15 to 25 roles at once? That seems like a lot.

Swati: It is a lot. Which is why efficiency is everything for a recruiter. They don't have time to read every resume carefully. They don't have time to craft personalized outreach to every potential candidate. They rely on tools, shortcuts, and pattern recognition. If you understand their shortcuts, you can position yourself on the right side of them.

Here's what a typical recruiter's day looks like:

graph LR
    A["8:00 AM<br/>Review new<br/>applications"] --> B["9:00 AM<br/>Sourcing on<br/>LinkedIn"]
    B --> C["10:30 AM<br/>Phone screens<br/>with candidates"]
    C --> D["12:00 PM<br/>Hiring manager<br/>calibration calls"]
    D --> E["1:00 PM<br/>Interview<br/>scheduling"]
    E --> F["2:30 PM<br/>More sourcing<br/>or outreach"]
    F --> G["4:00 PM<br/>Candidate<br/>follow-ups"]
    G --> H["5:00 PM<br/>Pipeline<br/>reporting"]

    style B fill:#51cf66,color:#fff
    style F fill:#51cf66,color:#fff

This diagram shows a typical recruiter's daily schedule from 8 AM to 5 PM. The day includes reviewing new applications, sourcing candidates on LinkedIn, conducting phone screens, having calibration calls with hiring managers, scheduling interviews, doing more sourcing and outreach, following up with candidates, and pipeline reporting. The sourcing blocks at 9 AM and 2:30 PM are highlighted to show that active candidate searching happens twice daily and is a major part of the recruiter's workflow.

Notice something? Sourcing - actively searching for candidates - takes up two dedicated blocks of the day. This is when the recruiter is on LinkedIn, running searches, looking at profiles, and deciding who to reach out to. Your LinkedIn profile, your GitHub, your online presence - they all need to be optimized for those sourcing sessions.

How LinkedIn Recruiter Search Works

The primary tool tech recruiters use for sourcing is LinkedIn Recruiter. This is not the same LinkedIn you use. It's a paid enterprise product with search capabilities far beyond what regular users see. Here's what a recruiter can do with it.

Student: Wait, so there's a completely different version of LinkedIn that recruiters use?

Swati: Yes. LinkedIn Recruiter (and its lighter version, Recruiter Lite) gives recruiters access to the entire LinkedIn network - not just their connections. They can search for any engineer in the world who has a LinkedIn profile. And they search using Boolean operators, filters, and keyword matching.

Let me show you what a typical recruiter search looks like when I tell my recruiter "I need a backend engineer with distributed systems experience, L5 or L6 level."

The recruiter opens LinkedIn Recruiter and types something like this:

("software engineer" OR "backend engineer" OR "SDE") 
AND ("distributed systems" OR "microservices") 
AND ("Java" OR "Go" OR "Python")

Then they apply filters:

The search returns a ranked list of profiles. LinkedIn's algorithm ranks profiles based on keyword match density, profile completeness, recent activity, connection proximity, and whether the candidate has turned on "Open to Work."

Student: So my LinkedIn headline and profile content directly determine whether I appear in these searches?

Swati: Directly. If a recruiter searches for "distributed systems" and your profile says "backend developer" but never mentions distributed systems - even if that's what you do every day - you won't appear. You're invisible. Not rejected. Invisible. There's a difference, and the difference matters enormously.

Important: Your LinkedIn profile is your search engine optimization. Every keyword in your headline, summary, experience section, and skills section is an indexable term that recruiters can search for. If a term isn't in your profile, you don't exist for searches on that term.

Think of it this way: if you were building a product, would you launch it without making it findable on Google? Your LinkedIn profile is the SEO for your career. We'll optimize it in detail in Module 04.

The Keyword Game

Let me go deeper on keywords, because this is where most engineers unknowingly sabotage themselves.

Student: What do you mean?

Swati: Here's an example. I had an engineer on my team at Google who was an expert in building real-time data pipelines using Apache Kafka and Apache Flink. Incredible engineer. She wanted to explore external opportunities, so she updated her LinkedIn. Her headline said: "Senior Software Engineer at Google."

That's technically accurate. It's also almost useless for recruiter search. A recruiter searching for "Kafka engineer" or "streaming data" or "real-time pipeline" would never find her. She'd only appear for the incredibly broad "software engineer at Google" search, which returns thousands of results and she'd be buried.

I helped her rewrite her headline to: "Senior Software Engineer at Google | Real-Time Data Pipelines | Kafka, Flink, Streaming Systems."

Same person. Same skills. Same experience. But now she appears in targeted recruiter searches for her actual expertise. Within two weeks, she was getting recruiter InMails she'd never gotten before.

Student: That's such a simple change. Why doesn't everyone do this?

Swati: Because most engineers think of LinkedIn as a digital resume - a static document that lists what they do. They don't think of it as a search engine that recruiters query actively. The mindset shift is: your LinkedIn profile is not for you. It's for the recruiter who's searching for someone like you.

Brandon, you do this from the other side. What do you tell your recruiters to search for?

Brandon: I'll give you the exact conversation I had with my recruiter last month. I had a role open on my team at AWS - a senior engineer for our distributed storage infrastructure. I told my recruiter:

"Search for engineers with S3, DynamoDB, or large-scale storage experience. They should have at least 5 years of backend experience, ideally at a company that runs high-throughput systems - so current or former engineers at Google, Meta, Netflix, Uber, Stripe, or similar. Look for keywords like 'cross-region replication,' 'consistency models,' or 'eventual consistency.' I want someone who's operated these systems, not just built them."

My recruiter took that and built a Boolean search. Within an hour, she had 40 profiles. She narrowed it to 15 based on profile quality. She InMailed 10. Three responded. One of those three eventually got an offer.

Student: So 10 InMails led to 1 offer? That's a 10% conversion from outreach to offer?

Brandon: For recruiter sourcing, yes - it's the highest conversion channel. But notice what happened: the candidate who got the offer had the right keywords in their profile, had a complete LinkedIn presence, was active on the platform, and responded to the InMail within 24 hours. Every one of those things increased their probability of being found and contacted.

How Recruiters Screen Resumes

Student: Okay, so that's the sourcing side - recruiters finding candidates. What about when applications come in? How do they screen the pile?

Swati: Great question. Let's talk about the screening process because there are some real misconceptions about it.

When applications come in through the career page, they first hit the ATS - we'll cover that in detail in the next lesson. What comes out of the ATS is a ranked list that the recruiter reviews. Here's how a recruiter actually processes that list:

stateDiagram-v2
    [*] --> Glance: Resume arrives
    Glance --> Skip: No keyword match<br/>Wrong level<br/>Formatting issues
    Glance --> Skim: Keywords match<br/>Right level range
    Skim --> Skip: Weak bullets<br/>No impact metrics<br/>Job hopping
    Skim --> Read: Strong bullets<br/>Clear impact<br/>Relevant experience
    Read --> Skip: Missing requirements<br/>Cultural concerns
    Read --> Shortlist: Strong match<br/>Clear fit

    Skip --> [*]: Rejected
    Shortlist --> PhoneScreen: Scheduled

    note right of Glance: 3-6 seconds
    note right of Skim: 15-30 seconds
    note right of Read: 1-2 minutes

This state diagram shows three stages of recruiter resume screening. Stage one is the Glance, which takes 3 to 6 seconds - the recruiter checks for keyword match, appropriate level, and formatting. Resumes that fail are skipped. Stage two is the Skim, which takes 15 to 30 seconds - the recruiter looks at bullet quality, impact metrics, and job stability. Weak bullets or no impact metrics lead to a skip. Stage three is the Read, which takes 1 to 2 minutes - the recruiter does a full review of the remaining candidates. Those who pass are shortlisted for a phone screen. Most resumes never make it past the Glance stage.

The Glance (3 to 6 seconds). The recruiter scans for: current title and company, years of experience, and whether the resume "looks right." A messy, dense, hard-to-scan resume gets skipped at this stage regardless of content. A clean, well-structured resume with a recognizable company name and appropriate title advances.

The Skim (15 to 30 seconds). The recruiter reads the top 2 to 3 bullet points. They're looking for impact - numbers, scale, outcomes. "Built a thing" is weak. "Built a thing that handles 1M requests per day and reduced latency by 40%" is strong. They're also checking for relevance to the specific role.

The Read (1 to 2 minutes). Only resumes that pass both the Glance and the Skim get a full read. At this stage, the recruiter is looking for the complete picture - career trajectory, skill match, any red flags (frequent job changes, unexplained gaps, mismatched claims).

Student: So most of my resume's fate is decided in the first 6 seconds?

Swati: For cold applications, yes. This is exactly why we're going to spend an entire module - Module 02 - on building a resume that survives all three stages. And it's why we built the AlgoInsight AI Resume Builder. It generates resumes that are optimized for each of these screening stages - ATS-friendly formatting, impact-driven bullets, and clean structure that passes the 6-second glance test.

But I want to be clear about something: a great resume is necessary but not sufficient. The resume gets you past the screening. It doesn't get you the job. The interview gets you the job. The resume opens the door. What you do when you walk through that door is what our technical courses - DSA Mastery, System Design, Behavioral Interview Mastery - prepare you for.

What Makes a Recruiter Reach Out

Student: You mentioned InMails - when recruiters reach out to candidates. What makes a recruiter decide to send that InMail?

Swati: Brandon is better positioned to answer this because he actually directs his recruiters on who to reach out to.

Brandon: Sure. When my recruiter shows me a shortlist of sourced profiles, here's what makes me say "yes, reach out to that person":

Strong signal of relevant experience. Their current role or recent roles are clearly in the same domain as my open role. If I'm hiring for a storage infrastructure engineer, and someone's current title is "Senior SDE, Storage Infrastructure" at a peer company - that's an instant yes.

Evidence of impact. Their profile or resume shows outcomes, not just activities. "Led migration of 50TB data warehouse from on-premise to AWS, reducing query times by 60%" makes me want to talk to them. "Worked on data migration projects" does not.

Appropriate level. They're at the right career stage. I'm not going to InMail a Director to fill an L5 role. I'm not going to InMail a new grad for a Principal position. Level alignment saves everyone's time.

Active on LinkedIn. If someone hasn't updated their profile in three years, hasn't posted anything, and doesn't seem active, the recruiter assumes they're not open to opportunities. An updated profile with recent activity signals availability.

The "Open to Work" flag. This is controversial - some people think it looks desperate. I disagree. When a recruiter runs a search, they can filter for candidates who have the "Open to Work" setting turned on. If you're actively looking, turning this on makes you immediately more visible. You can set it to be visible only to recruiters, not to your entire network, which solves the "my current employer might see this" concern.

Tip: The Recruiter Decision Tree:

1. Does this person's profile match the search terms? (If no → skip)
2. Are they at the right level for the role? (If no → skip)
3. Do they show evidence of relevant impact? (If no → skip)
4. Are they currently active on LinkedIn? (If no → lower priority)
5. Are they "Open to Work"? (If yes → higher priority)

Optimize your profile for each of these decision points. Module 04 walks you through this step by step.

The Recruiter Perspective on Referrals

Student: What about referrals? How do recruiters handle those differently?

Swati: I touched on this in the previous lesson, but let me go deeper. When a current employee submits a referral, it typically goes into a separate queue. The recruiter treats it differently for a specific reason - there's a built-in quality signal. A current employee is putting their reputation on the line by referring someone. That social proof changes the recruiter's behavior.

Here's the practical difference:

Student: That's a massive difference. So even a mediocre resume gets more attention with a referral?

Swati: Not mediocre - the resume still needs to be solid. But a solid resume with a referral gets 5 to 10 times more attention than the same solid resume without one. The referral doesn't replace the resume - it amplifies it.

And here's something most candidates don't realize: the person referring you also gets a bonus if you're hired. At Google, the referral bonus is substantial. At Amazon, it's meaningful. So when you ask someone for a referral, you're not just asking for a favor - you're creating a situation where both of you benefit. That reframe makes the ask less awkward. We'll practice the actual referral conversation in Module 06.

Red Flags Recruiters Watch For

Student: Are there things that immediately disqualify someone?

Swati: "Disqualify" is strong, but there are red flags that make a recruiter pause. Let me give you the honest list:

Frequent job hopping without progression. Changing jobs every 6 to 12 months is fine if you're clearly growing - moving from junior to mid to senior. But if you're at the same level across four companies in three years, it looks like you can't stick anywhere or can't grow.

Vague descriptions of work. "Worked on backend services" with no details. If a recruiter can't tell what you actually built, they assume you didn't build much.

Typos and formatting errors. This sounds petty, but a typo in your resume tells a recruiter "this person didn't proofread." If you don't proofread your resume - the most important document in your job search - what does your code look like?

Mismatched claims. Saying you have "expert-level" knowledge in 15 technologies. Nobody is an expert in 15 things. Overclaiming erodes trust.

Negative framing. Any hint of negativity about previous employers - in your resume, LinkedIn, or during the recruiter call - is a red flag. It signals "this person might bring drama."

Warning: The one red flag that kills more applications than any other: A resume that doesn't match the job description. If the JD says "Java" and your resume only mentions Python, the recruiter assumes you're not a fit - even if you know Java perfectly well. The fix is simple: tailor your resume for every role you apply to. This sounds exhausting, but AlgoInsight's AI Resume Builder can tailor your resume to a specific job description in seconds. It reads the JD, identifies the keywords and requirements, and adjusts your resume to match - without fabricating experience you don't have.

The Takeaway: Think Like a Recruiter

Student: So the summary is - if I want to get more interviews, I need to think about what the recruiter is doing, not just what I'm doing?

Swati: That's exactly right. The candidates who succeed in the job search are the ones who can mentally model the recruiter's workflow and optimize for it. When you write your resume, you're writing for the recruiter's 6-second glance. When you build your LinkedIn profile, you're building for the recruiter's Boolean search. When you activate your network for referrals, you're accessing the recruiter's priority queue.

Every decision you make in your job search should be informed by the question: "How does this look from the recruiter's side?"

Interview: This Recruiter Knowledge Helps You IN the Interview Too

When an interviewer asks "Why are you interested in this role?" - and they will - you can draw on what you now know about the hiring pipeline. "I researched your team's work on cross-region replication, spoke with two engineers on the team, and believe my experience building similar systems at my current company maps directly to the challenges you're solving" is an answer that shows you understand how the system works. It demonstrates research, intentionality, and self-awareness - the exact three things Swati identified in Module 00, Topic 01.

Exercise: Starter: Go to LinkedIn and search for your own target role (e.g., "backend software engineer"). Note how many results appear. Now add one specific technology you're skilled in (e.g., "backend software engineer Kafka"). How much does the result count change? This is the power of keyword specificity.

Intermediate: Find a real job posting for a role you'd want. Extract every keyword and skill mentioned in the JD. Compare these against your LinkedIn profile. How many of those keywords are in your headline, summary, or experience sections? Create a "keyword gap" list of terms that should be in your profile but aren't.

Advanced: Search for "[your target company] recruiter" on LinkedIn. Find 3 recruiters who hire for your target role. Study their profiles - what do they post about? What do they say they're looking for? Understanding what recruiters advertise gives you insight into what they value. Save these profiles - you may reach out to them in Module 06.

Student: I feel like I've been playing a game without knowing the rules. Now I at least understand the board.

Swati: That's the whole point of this module. Before you optimize anything - your resume, your LinkedIn, your network - you need to understand the system you're optimizing for. And there's one more piece of this system we need to cover: the technology layer. In the next lesson, Deepika is going to explain how ATS systems and AI screening tools actually work under the hood. She built our AI evaluation engine, so she understands this from the engineering side. What she'll tell you might surprise you - some of what you've heard about "beating the ATS" is myth, and some of it is more real than you think.

Let's go.

Back to The Job Search System