How to Review &
Read a Resume
This module teaches you to evaluate a resume not as a reader � but as a decision-maker. You will learn to make a shortlist/eliminate call within 10�15 seconds, document every decision in Ceipal, and protect the pipeline from bad submissions.
Before You Open a Resume
Resume review is not reading � it is pattern recognition under time pressure. The three rules below govern everything that follows in this module.
Speed is the Skill
You are processing dozens of resumes per day. 10�15 seconds per resume is a trained discipline, not a shortcut. The faster and more accurately you decide, the more value you deliver to your team and clients.
Doubt = Opportunity
If you hesitate to eliminate, the candidate has passed the paper round. Pick up the phone. A screening call is always cheaper than a bad submission that wastes a client's time and your credibility.
Document Every Decision
Every eliminate or shortlist must have a note in Ceipal. No note = no accountability. Notes protect you, inform your team, and create a traceable pipeline that your Account Manager can act on.
Your goal when opening a resume is to eliminate it in under 10�15 seconds. If you CANNOT confidently eliminate it � that resume earns a screening call. You are not looking for reasons to hire. You are looking for fast, defensible reasons to filter.
Imagine you receive 150 applications for a Senior Java Developer role. If you spend 3 minutes on each, that's 7.5 hours just reading resumes � before any calls, submissions, or actual recruiter work happens. At 10�15 seconds per resume (using the 7-step framework), you complete the same review in 25�38 minutes, leaving your day free for high-value activities like candidate calls and client coordination.
The 10�15 second rule isn't about being careless. It's about being disciplined and systematic. Each step in the review process is designed to give you a binary signal: continue or eliminate. Once you train your eyes to look for specific patterns, the speed follows naturally.
The 7-Step Resume Review Process
From the moment you open a resume to the moment you log your decision in Ceipal � every step is purposeful. Follow this sequence every single time, without exception.
Check Ceipal Keyword Match
Before reading a single line of text, look at the ATS match score. Are all critical (must-have) skills present? If a critical skill is missing, you eliminate here without reading further. This is your first and fastest filter.
First 5 Seconds ATS-Driven FilterRead the Resume Bottom-Up
Most people read top-down and get anchored by a flashy current job title. Reading bottom-up (education ? early career ? mid career ? most recent role) reveals the true trajectory: where they started, how they grew, and whether recent experience is genuinely relevant.
Reverse Chronological ReadCheck the 5 Deal Breakers
Run through the non-negotiable elimination criteria: Education/Certifications, Total Experience, Relevant & Recent Experience, Location, and Visa/Work Authorisation. Any single failure = immediate eliminate.
Binary: Pass or EliminateEliminate with a Ceipal Note (if fails)
If any deal breaker fails, do not move on � log the decision immediately. Your note must capture: what failed, why it's a disqualifier for this specific requisition, and your recommendation (eliminate / flag). No note = the decision never happened.
Eliminate + LogAssess Light Relevant Experience (Borderline)
If the candidate has the right skills but fewer years than required (e.g. 3 years vs. 5+ required), assess whether the requirement is hard or flexible. If hard: eliminate. If flexible: move to a screening call and use the experience gap as a pay rate negotiation lever.
Borderline DecisionCheck Recency of Experience
Relevant experience more than 3�5 years old should be treated as light. Technologies evolve rapidly � a Java developer who hasn't used Java in 4 years may be significantly behind the current stack. Apply the same borderline logic as Step 5.
Recency = RelevanceFlag Employment Gaps
Scan the work history for unexplained gaps of 3+ months. Gaps are not automatic disqualifiers � they are unanswered questions. Log every gap found in Ceipal and verify the reason on the screening call before submitting to the client.
Flag ? Verify ? DecideThese steps are sequential and non-negotiable in order. You do not skip to Step 5 before running Step 3. The sequence is designed to eliminate the most candidates with the least effort at each stage � coarse filter first, fine filter later.
Ceipal Keyword Match � First 5 Seconds
Before reading a single word of the resume, let the ATS do the first filter. Ceipal's keyword match score is your fastest, most objective data point.
When you open a candidate profile attached to a requisition, Ceipal surfaces a keyword match score � a percentage indicating how many of the job's required keywords appear in the resume. This is your first look before investing any reading time.
- Are ALL critical / must-have skills present in the resume text?
- Are required tools and platforms explicitly listed?
- Does the match score meet the threshold your team has set for this role?
- Are keywords present in the skills section only, or also backed up in actual job descriptions?
Continue to Step 2 (bottom-up read). The resume has cleared the first filter. Proceed.
Eliminate immediately. Log in Ceipal: "Missing [skill name] � not a match for Req #[ID]." Stop here. Do not read further.
Some candidates (or professional CV writers) load the skills section with every technology a job posting mentions � even if the candidate has never actually used them. This inflates the match score artificially.
The test: Do those keywords also appear in the work experience section with context? A resume that lists "AWS, Kubernetes, Terraform" in skills but has no mention of cloud infrastructure in any job description is a red flag, not a green light.
Keywords appearing only in the skills section with no supporting evidence in job descriptions signal keyword stuffing. Always cross-reference with the actual experience section before clearing this filter.
Req: Senior Java Developer � Must-have: Java 7+, Spring Boot, AWS, RESTful APIs.
Candidate A's Profile: Match score 94% � Java ? � Spring Boot ? � AWS ? � REST ? ? Proceed to Step 2.
Candidate B's Profile: Match score 42% � Java ? � Spring Boot ? (not found) � AWS ? ? Eliminate. Log: "Missing Spring Boot and AWS � both hard requirements for Req #2025-042."
Read the Resume Bottom-Up
Most recruiters read top-down and get anchored by the candidate's current job title. Reading bottom-up � from education to present � reveals the truth of a candidate's trajectory.
Candidates design resumes to be read top-down. They put their most impressive current role first, hoping you form a positive impression before you discover weak early experience. Reading bottom-up breaks that design intent. You start with foundational facts � education, early career � before seeing the headline they want you to anchor to.
This approach also shows you trajectory: has this person been consistently growing in the right direction, or did they peak early and stagnate?
Education: Degree match (e.g., B.Sc. Engineering for a tech role), certifications (PMP, CPA, RN), graduation year (to calculate total experience), institution type (overseas degrees need verification).
Early career: Are their first jobs in the right domain? A Java developer whose first 3 jobs were all in Java/J2EE is building a coherent story. A Java developer whose first 3 jobs were in unrelated fields raises questions about depth.
Mid career: Where did they deepen their expertise? Did they take on increasing responsibility, or did they plateau? Are the tools and domains they used here consistent with the req?
Most recent role: This carries the most weight. Is it active or ended? Is it in the required domain? What's the recency of the skills you need? What's their notice period (if stated)?
Deal Breakers � The 5-Point Check
These are the non-negotiable elimination criteria. ANY ONE failing = eliminate immediately. There is no "maybe" at this stage.
There are only two outcomes at this step: PASS (all 5 criteria met) or ELIMINATE (any 1 criteria fails). You do not partially shortlist. You do not put a resume in a "maybe" pile. Binary decision, binary action, binary note in Ceipal.
Education / Certifications / Licences
Does the candidate hold the required degree, certification, or professional licence? Examples:
- PMP required for Project Manager roles
- RN licence required for all nursing positions
- CPA required for senior accounting roles
- B.Sc. or higher in Computer Science for many tech roles
Total Experience
Is the total years of experience within the required range? Both under- and over-qualification can be valid eliminates depending on client preference:
- Too junior: May not have the depth or independence the client expects
- Too senior: May be overqualified, salary expectations too high, risk of leaving early
- Always cross-check graduation year + work history start year
Relevant & Recent Experience
Does the candidate have hands-on experience in the specific domain or technology required � AND is it within the last 3�5 years? This is a two-part test:
- Relevant: Has the candidate actually done this work (not just listed the tool)?
- Recent: Skills decay. AWS experience from 6 years ago in a different role context is not the same as current AWS experience.
Location
Is the candidate in, or willing to relocate to, the required location? For remote roles, check timezone or work authorisation geography (a US-based remote role may still require US residency).
- On-site role: candidate must be local or relocation-willing
- Remote role: verify work authorisation geography, timezone fit
- Hybrid: check commuting distance
Work authorisation in US staffing is a hard stop. The visa section requires its own dedicated deep dive � navigate to the Visa / Work Auth section from the sidebar for the complete breakdown of all US visa types, what each means, and how to evaluate them.
Visa & Work Authorisation
In US staffing, work authorisation is a hard stop. You must know these visa types cold � a wrong visa call can create legal and compliance issues for both client and candidate.
A candidate without valid work authorisation cannot legally be placed. Submitting such a candidate wastes a client slot, damages your agency's credibility, and in some cases creates legal liability. Know your visa types before you open your first resume.
No sponsorship needed. Free to work anywhere, for any employer, on any contract type. Most preferred by clients � zero authorisation risk.
Employer-sponsored, role-specific. Check if the client accepts H-1B. Transfer (H-1B portability) is possible between employers but requires processing. Very common in IT and Tech roles.
Time-limited. Always check the expiry date. OPT is common for recent international graduates (up to 3 years under STEM extension). Loses validity if not extended in time.
Role-specific (limited to certain professions under USMCA). Renewable annually. Some clients accept TN, some don't � always check with your Account Manager before submitting.
Reserved for international students on F-1 visas who are enrolled in a degree program. Extremely limited, tied to academic enrollment. Very rarely placeable � flag to AM immediately.
Client must initiate and pay for the sponsorship process. Most W2 clients will not accept this � it's expensive and time-consuming. Unless your client has explicitly confirmed they sponsor, eliminate.
US candidates often (but not always) list their work authorisation status at the top of the resume or in a header section. Look for phrases like:
- "US Citizen" or "Green Card Holder" � no further action needed
- "H-1B Visa � open to transfer" � confirm client accepts H-1B before proceeding
- "EAD � valid through [date]" � check the expiry date immediately
- "OPT STEM Extension" � verify remaining months before placing
- "Require H-1B Sponsorship" � eliminate unless client sponsorship is confirmed
- No visa info listed � ask during screening call, do not guess
Always log visa status in Ceipal, even for USC/GC candidates: "H1B holder. Client #[name] confirmed H1B acceptance. Proceed." or "EAD valid through Aug 2026. Placement window sufficient for this assignment."
Ceipal Notes � Your Paper Trail
Notes in Ceipal are not optional. They are your accountability record, your team's communication layer, and your protection if a decision is ever questioned.
Open Candidate Profile
Navigate via candidate record or the job pipeline view. Search by name or candidate ID.
Click 'Add Note'
Found under the 'Activities' or 'Notes' tab. Select the appropriate note category from the dropdown.
Choose Note Type
Options: Reviewed / Screened / Shortlisted / Rejected / On Hold. Match status to your actual decision.
Write Your Note
Include: Decision + Reason + Key data points (skills gap, visa type, experience level).
Link to Requisition
Tag the Job ID or req number. The note must appear in the correct pipeline, not just on the candidate record.
Save & Confirm
Note is now time-stamped with your name and linked to the job. Visible to team and Account Manager.
Ceipal Note Templates � Copy & Adapt
Use these as your baseline. Always personalise with the candidate's specific details and the requisition number.
Skill Gap
Experience Below Threshold
Location / Visa Mismatch
Screening Needed � Light Experience
Employment Gap Flagged
Strong Match
Borderline Decisions
Not every resume is a clean pass or fail. Steps 5 and 6 handle the grey zone � and both follow the same decision logic.
Scenario: The candidate has the required technology or skill set, but fewer years of experience than the requisition specifies. Example: Req asks for 5+ years Java; candidate has 3 years.
This is not an automatic eliminate. First, ask: Is the year requirement a hard client constraint, or a soft guideline?
Client insists on exact years ? ELIMINATE. Log: "Experience below threshold for this client req. [X yrs vs Y required]."
Move to screening call. Use the lighter experience as a lever in pay rate negotiation. Lower experience justifies a lower bill rate � value to both you and the client.
Scenario: The candidate has the required years of experience overall, but the relevant experience is dated. Example: 7 years Java total, but the last Java role ended 4 years ago. Current role is in .NET.
Rule of thumb: Relevant experience over 3 years old should be treated as 'light.' Skills decay and technology stacks evolve rapidly. A Java developer who hasn't actively used Java in 4 years may be significantly behind on frameworks (Spring Boot, Java 17+, reactive programming, etc.) that the client needs today.
ELIMINATE. The client needs current proficiency. Log: "Java experience last active [year]. Current role unrelated. Not meeting recency standard."
Screen to assess whether the candidate has maintained the skill informally � through side projects, certifications, or freelance work. Verify before submitting.
Both steps follow identical logic. The only variable is whether the requirement is hard or flexible:
- Hard requirement ? Eliminate. Log specific reason tied to the client's stated criteria.
- Flexible requirement ? Screen. Use the gap (experience or recency) as a pay rate negotiation lever.
When a candidate is borderline, their gap in experience or recency gives you a legitimate justification to negotiate a lower bill rate with the client or a lower pay rate with the candidate. This is not a workaround � it's a professional lever that keeps good candidates in the pipeline at a price point that works for all parties.
Flag Employment Gaps
Gaps are not automatic disqualifiers � they are unanswered questions. Your job is to find them, note them, and verify them before submitting to a client.
- 3+ months unexplained: Any period between jobs that isn't accounted for by the next role starting. The baseline threshold � note it and verify it.
- Overlapping dates: Two jobs listed at the same time. Could be legitimate contract/consulting work � or a red flag. Clarify before assuming either way.
- COVID-era gaps (2020�2021): Common and often acceptable. Layoffs, furloughs, and industry shutdowns were widespread. Still ask � don't assume.
- Frequent job changes under 1 year each: Flag the pattern, not just individual gaps. Note the retention risk for your client.
- Year-only dates: Resumes showing "2019 � 2021" instead of "Jan 2019 � Mar 2021" can conceal gaps. Always ask for month/year in the screening call.
Find
Scan work history dates during bottom-up read. Calculate gaps mentally as you move through the timeline.
Note
Log in Ceipal immediately: "Gap identified: [dates]. Reason TBC. To verify on screening call."
Verify
On the call, ask directly: "I noticed a gap from [X] to [Y] � can you walk me through that period?"
Update
If gap is explained and acceptable, update the resume before submission with a brief note (e.g. 'Career break � family').
The way you ask matters. A confrontational question makes candidates defensive and less forthcoming. A neutral, matter-of-fact question gets honest answers.
"I noticed there's a gap in your work history from around [month year] to [month year]. Could you help me understand what you were doing during that time?"
"Why weren't you working from [date] to [date]?" � This is accusatory in tone and will likely make the candidate shut down.
Family care / parental leave � Personal health / medical � Relocation � Further education � Layoff / company closure � Career transition � Travel sabbatical. Always log the reason in Ceipal after verification.
Shortlist vs Eliminate � Decision Matrix
Apply this as a quick mental checklist on every resume. Run it in your head as you move through the 7 steps.
| Criteria | ? SHORTLIST | ?? SCREEN (Borderline) | ? ELIMINATE |
|---|---|---|---|
| Ceipal Keyword Match | All critical skills present | 80%+ match, 1�2 minor gaps | Critical skill absent |
| Total Experience | Meets exact requirement | Within 1�2 years of req | Below or far above req |
| Relevant Experience | Recent & domain-matched | Relevant but 3�5 years old | Irrelevant or very old |
| Location / Visa | Matches req exactly | Will relocate / H1B transfer possible | Hard mismatch, no flexibility |
| Employment Gaps | No gaps / all explained | Gap present, needs verification | Large unexplained gaps |
| Education / Certs | Meets or exceeds requirement | Partial match � assess on call | Required credential missing |
At-a-Glance Quick Reference
Eliminate When...
Screen When...
Red Flags to Catch During Resume Review
Red flags don't always mean eliminate � but they ALWAYS mean flag and verify. Never ignore a red flag and submit anyway.
Keyword Stuffing
Skills section lists 40+ tools with no evidence of use in job descriptions. If the experience section doesn't support the skills list, the skills list is probably copy-pasted from a job posting. Probe on the screening call: "Can you walk me through a project where you used [tool]?"
Year-Only Dates
"2019 � 2021" instead of "Jan 2019 � Mar 2021." Year-only dates can mask gaps of up to 11 months per transition (e.g., Oct 2019 to Jan 2021 appears continuous but contains a 3-month gap). Always request month/year dates on the screening call.
Frequent Job Hops
5 jobs in 4 years. Not always a red flag � contract/consulting work legitimately involves frequent transitions. But for full-time roles, short tenures suggest retention risk. Ask about the nature of each role (contract vs. full-time) and the candidate's reasons for leaving.
Vague Responsibilities
"Worked on various projects" with no specifics. This could mean the candidate is hiding shallow experience, or it could mean they're a poor resume writer. Probe on the call: "What specifically was your role on those projects? What decisions did you own?"
No Recent Activity
Last job ended 2+ years ago with no explanation. Could be contract work between full-time roles, a sabbatical, health issue, or extended gap. Never guess � always ask. Log it as a gap flag in Ceipal before the call.
Inconsistent Titles
"Software Engineer" on the resume but "Software Architect" on LinkedIn. Discrepancies between resume and LinkedIn are a common verification gap. Always cross-reference LinkedIn for senior roles. Inconsistency needs to be addressed on the call or flagged to the AM.
Resume Format Issues
Very hard to read, poor structure, spelling errors. For client-facing roles (business analyst, project manager, consultant), poor written communication on the resume signals poor written communication in the role. Note it. For purely technical roles, the bar may be lower � but always flag for the screening call.
Experience Timeline Mismatch
Claims "10 years of experience" but graduated 7 years ago. The math doesn't add up. This is a common resume exaggeration tactic. Always calculate: graduation year + years in work history. If the claimed experience exceeds what the math allows, flag it and verify on the call before submitting.
Live Walkthrough � 7 Steps in Action
Watch the full 7-step process applied to a real requisition and candidate. Follow step by step to see how each decision is made and logged.
Ceipal Keyword Check
Java ? � Spring Boot ? � AWS ? � Match score: 92%. All critical must-have skills present. Proceed to Step 2.
Bottom-Up Read
Graduated 2012 (B.Tech CS). Early roles in Java/J2EE (2012�2016). Mid career: Spring Boot adoption 2017. Current role: Java Lead at Flipkart since 2021. Clean upward trajectory throughout. No concerns. Proceed.
Deal Breaker Check
Total exp: 11 yrs ? � Relevant (Java/Spring Boot/AWS in current role) ? � H-1B holder ? (client confirmed acceptance) � Location: India, open to US relocation ?. All deal breakers pass.
No Elimination Triggered
No deal breakers failed. Resume passes filter. Moving to shortlist track.
Experience Check
11 years Java, 6 years Spring Boot, 3 years AWS hands-on. All meet or exceed requirements. Not a borderline case � strong match.
Recency Check
Current role (2021�present) is active and directly relevant in all three required skill areas. No recency concern.
Gap Check
Gap identified: October 2018 � April 2019 (6 months). No explanation provided. FLAG in Ceipal � verify reason on screening call before submitting.
Shortlisted for Req #2025-042. Strong match � Java 11 yrs, Spring Boot 6 yrs, AWS 3 yrs. H1B (client confirmed). Oct 2018�Apr 2019 gap flagged � reason TBC. Screening call to be scheduled.
Resume Review Decision Flow
The complete decision tree from resume opened to Ceipal note logged. Use this as a mental map every time you sit down to review a batch of candidates.
Test Your Understanding
Answer these scenario-based questions. Each reflects a real-world resume review situation you will encounter on the job.
Q1. You open a resume and the Ceipal match score shows 91%, but the candidate is missing Spring Boot � a must-have for the req. What do you do?
Q2. A candidate's resume shows "2018 � 2020" for Job A and "2020 � 2023" for Job B. Why might you be concerned, and what's your action?
Q3. A candidate has 7 years of Java experience total, but their last Java role ended in 2020. They've been working in Python since then. The req needs Java. What's the right call?
Q4. You shortlist a candidate for an on-site Chicago role. You then notice they're currently based in Bangalore, India with no relocation mentioned. What do you do?
Q5. You've shortlisted a candidate and are about to submit to the client. You haven't added a note in Ceipal. Is that acceptable?
Score: 0/5
Review the sections above for any questions you missed.
Glossary � Terms You'll Encounter Daily
Key terminology from this module and the broader US staffing context. Refer back here as you encounter unfamiliar terms on the job.
Eliminate in 10�15 Seconds
Train your eyes to decide fast. Doubt = screening call, not more time staring at the resume.
Ceipal Match First, Always
Let the ATS do the coarse filter before you read a single line. Critical skills missing = instant eliminate.
Deal Breakers Are Binary
No negotiation at Step 3. One failure = eliminate. There is no "maybe" at the deal breaker stage.
Note Every Single Decision
Shortlist or eliminate � both need a Ceipal note. No note = no accountability and no team visibility.