The Naukri recruiter-search algorithm ranks profiles on 11 specific fields. Recruiters filter on these fields; the algorithm surfaces profiles that pass the filters. The 11 fields are well-known to anyone who has worked on Naukri's ranking system, and the order of fix matters: fix the Basics first (the algorithm filters on these), then the Experience, then the Skills, then the Activity signals.
This post is the 11 fields, the order to fix them, the 5 things that mark the profile as stale, and the 1-hour optimization that moves the needle the most. The First Day AI Job Search Plan is calibrated for Naukri + Indeed + LinkedIn; the Naukri profile optimization is the highest-leverage piece for India-based candidates.
How the Naukri algorithm ranks profiles
The Naukri algorithm has 3 ranking signals:
Signal 1: Field match. When a recruiter searches for "Python developer with AWS experience in Bangalore," the algorithm matches each keyword against the profile's 11 fields. The match score is the percentage of the recruiter's filters that the profile satisfies. The top 5% of matches are shown first.
Signal 2: Profile activity. The algorithm tracks when the profile was last updated, how often it's been updated in the last 6 months, and how often the candidate responds to recruiter messages. The activity signal is a freshness multiplier: a profile with 100% field match but no activity is ranked below a profile with 80% field match and weekly activity.
Signal 3: Recruiter behavior. The algorithm tracks which profiles recruiters click on, message, and shortlist. The behavior signal is a quality multiplier: a profile that recruiters engage with is ranked higher than a profile that recruiters ignore.
The 3 signals combine to a final ranking score. The top 5% of profiles for any given search are shown on the first page. The bottom 50% are not shown at all.
The 11 fields below are the inputs to the field-match signal. The activity signal is updated separately. The recruiter-behavior signal is earned over time.
The 11 fields, in 4 sections
Section 1: Basics (4 fields)
Field 1: Headline (50-60 char)
The headline is the most-searched field. Recruiters see the headline in the search results; the candidate's response rate depends on the headline's match to the recruiter's filter.
The wrong headline: "Software Engineer" (too generic) The right headline: "Senior Software Engineer | Python, AWS, Kubernetes | 8 YOE | Bangalore"
The right headline has 4-6 keywords, the candidate's seniority, the years of experience, and the location. The headline is 50-60 characters. The keywords are the destination role's top 5 keywords (read 5-10 JDs to identify them).
The fix: Rewrite the headline today. The headline should change as the destination role changes. If you're applying to data roles, the headline should include "data" and "SQL." If you're applying to product roles, the headline should include "PM" and "user research."
Field 2: Current CTC (LPA)
Recruiters filter on current CTC. A recruiter looking for a candidate with 8-12 LPA current CTC will not see a candidate whose current CTC is 14 LPA. The filter is a real filter; the algorithm respects it.
The fix: Set the current CTC accurately. Don't over-inflate; recruiters will ask. Don't under-inflate; you'll be filtered out.
Field 3: Expected CTC (LPA)
Recruiters filter on expected CTC. The expected CTC is the candidate's stated minimum. A recruiter looking for a candidate with 12-16 LPA expected will not see a candidate whose expected is 18+ LPA.
The fix: Set the expected CTC accurately. The expected CTC should be 30-50% above the current CTC for a typical job change. A candidate with 10 LPA current should have 13-15 LPA expected.
Field 4: Location (current + willing)
Recruiters filter on location. The location field has 2 sub-fields: current location (where you are) and willing to relocate to (where you'll go).
The fix: Set both accurately. If you're in Bangalore and willing to relocate to Hyderabad, set both. The location filter is a real filter; the algorithm respects it.
Section 2: Experience (3 fields)
Field 5: Employment history (titles)
Recruiters search by title. A recruiter looking for a "Senior Software Engineer" will see candidates whose most recent title is "Senior Software Engineer" or similar. The title is the filter; the algorithm respects it.
The fix: Set the titles accurately, but in the destination role's vocabulary. The 3-bullet reframe covers the title-level reframe. If you're a "Senior Mechanical Engineer" applying for a "Senior Software Engineer" role, reframe the title to "Senior Software Engineer" (with the source domain's experience described in the bullets).
The trade-off: The title reframe is honest if the work is honest. The title is the job title; the work is the substance. The reframe is the bridge.
Field 6: Key skills per role
Each role in the employment history has a "key skills" sub-field. The algorithm matches these skills against the recruiter's filter.
The fix: Set the key skills per role, not in aggregate. Each role has 4-8 key skills that match what the candidate did in that role. The skills are the destination role's top 5 keywords, calibrated to each role.
Field 7: Projects / achievements
Each role has a "responsibilities" or "projects" sub-field. The algorithm matches the project's keywords against the recruiter's filter.
The fix: Set the projects with specifics. The 3-bullet reframe applies here. The projects are 3-5 specific initiatives with numbers, calibrated to the destination role's vocabulary.
Section 3: Skills (2 fields)
Field 8: Top 8-12 keywords
The Skills section is a canonical list of 8-12 tools, technologies, or skills. The algorithm matches the list against the recruiter's filter.
The fix: Set the Skills section to 8-12 keywords, not 25. The 8-12 should be the destination role's top 5 keywords + 3-7 supporting skills. Don't list 25 skills; the algorithm doesn't favor volume.
The order: The top 4-5 skills should be the destination role's top keywords. The next 4-7 should be the supporting skills. The order matters for the algorithm's surface; the top skills are weighted higher.
Field 9: Certifications (verified)
Certifications are a separate field. The algorithm matches the certification name against the recruiter's filter. Verified certifications (with a verifiable URL or vendor ID) rank higher than unverified.
The fix: List certifications only if you have them, and only if they're verified. Don't list unverified certifications; the algorithm doesn't favor them, and recruiters check. If you have a verification URL, include it.
Section 4: Activity (2 fields)
Field 10: Profile completeness (90%+)
The algorithm tracks profile completeness. A profile at 90%+ completeness is ranked higher than a profile at 60% completeness. The completeness is the percentage of fields filled.
The fix: Fill every field. The basics, the experience, the skills, the certifications, the resume (uploaded), the photo (optional but recommended), the summary. The 90%+ target is achievable in 1 hour.
Field 11: Last updated (this month)
The algorithm tracks when the profile was last updated. A profile updated this month ranks higher than a profile updated 6 months ago. The "last updated" is the timestamp of the most recent edit.
The fix: Update the profile at least monthly. The update can be small (a 1-character change to the headline, a re-anchored bullet, a new skill) but the timestamp must move. The algorithm uses the timestamp as a freshness signal.
The order to fix them
Hour 0-1: Section 1 (Basics). Headline, current CTC, expected CTC, location. These are the highest-leverage fields because the algorithm filters on them first. A candidate with 100% match on Section 1 is in the top 5% for any search that matches their headline.
Hour 1-2: Section 2 (Experience). Employment history, key skills per role, projects. The 3-bullet reframe applies here. The reframe moves the experience from source-domain vocabulary to destination-domain vocabulary, increasing the field match.
Hour 2-3: Section 3 (Skills). Top 8-12 keywords, certifications. The Skills section is the simplest field to optimize. Read 5-10 JDs for the destination role; the top 5 keywords are the Skills section.
Hour 3+: Section 4 (Activity). Profile completeness, last updated. The activity signals are updated continuously. The fix is to update the profile at least monthly.
The 1-hour optimization that moves the needle the most is Section 1 (Basics). The Basics are the algorithm's primary filter. A candidate with 100% match on Basics is in the top 5% for any matching search.
The 5 things that mark the profile as stale
Stale signal 1: No update in 6+ months.
The algorithm's freshness signal is "last updated." A profile updated 6+ months ago is marked stale. The fix: update at least monthly.
Stale signal 2: Photo missing or low-quality.
A profile with no photo or a low-quality photo is ranked lower than a profile with a clear, professional photo. The fix: upload a clear, professional photo. The photo should be head-and-shoulders, well-lit, neutral background.
Stale signal 3: Resume not uploaded.
A profile without a resume is incomplete. The algorithm marks it as low-completeness. The fix: upload the resume. The resume should be the same as the destination role's resume (the ATS-optimized version).
Stale signal 4: Headline 1-3 words.
A headline like "Software Engineer" or "Manager" is too generic. The algorithm doesn't have enough keywords to match the profile to recruiter searches. The fix: rewrite the headline with 4-6 keywords, the seniority, the YOE, and the location.
Stale signal 5: No skills listed.
A profile without a Skills section is incomplete. The algorithm doesn't have the keywords to match the profile. The fix: list 8-12 skills, with the top 4-5 being the destination role's top keywords.
The 1-hour optimization
For candidates who have 1 hour to optimize the Naukri profile, the 1-hour plan is:
Minutes 0-15: Headline rewrite.
Rewrite the headline in destination-domain vocabulary. The headline is 50-60 characters, with 4-6 keywords.
Minutes 15-30: CTC + Location.
Set the current CTC, expected CTC, and location accurately. The recruiter-search filter respects these fields.
Minutes 30-50: Skills section.
Read 5-10 JDs for the destination role. The top 5 keywords are the Skills section. Add 3-7 supporting skills.
Minutes 50-60: Update any bullet.
Open one of the existing roles, edit one bullet, save. The "last updated" timestamp moves. The freshness signal updates.
End of hour 1: The profile is at 90%+ completeness. The Basics are filled. The Skills are optimized. The activity signal is current. The profile is in the top 5% for any matching search.
The 1-hour optimization moves the needle. The candidate who invests 1 hour is in the top 5% for any matching search; the candidate who doesn't is in the bottom 50%.
The weekly maintenance
The 1-hour optimization is the first-time fix. The weekly maintenance is the ongoing fix:
Monday: Update the headline. Change 1 keyword. The headline moves.
Wednesday: Re-anchor 1 bullet. Open one of the existing roles, edit one bullet, save. The bullet re-anchors to a new keyword; the activity signal moves.
Friday: Check the response rate. Open the Naukri inbox. Count the recruiter messages received in the last 7 days. If the rate is dropping, re-anchor more bullets. If the rate is stable, maintain.
The weekly maintenance is 15 minutes. The maintenance keeps the profile in the top 5%.
Common mistakes
Mistake 1: Listing 25 skills.
The Skills section is 8-12 keywords, not 25. The algorithm doesn't favor volume. The fix: list 8-12, with the top 4-5 being the destination role's top keywords.
Mistake 2: Inflating CTC.
The current CTC should be accurate. Don't inflate; recruiters will ask. The fix: set the current CTC accurately.
Mistake 3: Generic headline.
A headline like "Software Engineer" is too generic. The fix: 4-6 keywords, the seniority, the YOE, the location.
Mistake 4: Stale profile.
A profile updated 6+ months ago is marked stale. The fix: update at least monthly.
Mistake 5: No resume uploaded.
A profile without a resume is incomplete. The fix: upload the resume.
Mistake 6: Title mismatch.
A candidate whose most recent title is "Senior Mechanical Engineer" but who's applying for a "Senior Software Engineer" role has a title mismatch. The fix: reframe the title to the destination role's vocabulary, with the source domain's experience described in the bullets.
Mistake 7: No response to recruiters.
The activity signal tracks response rate. A candidate who doesn't respond to recruiters is marked low-activity. The fix: respond to every recruiter message within 24 hours.
The Naukri + Indeed + LinkedIn strategy
For India-based candidates, the 3 platforms have different strengths:
- Naukri: Highest volume of recruiter searches. The algorithm is keyword-driven. The Basics, Experience, and Skills are the most-searched fields.
- Indeed: Volume of job applications. The algorithm is similar to Naukri but with less recruiter-search activity. The resume upload is the most-searched field.
- LinkedIn: Network-driven. The algorithm is different — LinkedIn's "Open to Work" badge, profile views, and recruiter messages are the most-searched signals.
The strategy:
- Naukri profile: Optimize the 11 fields. The 1-hour optimization + the weekly maintenance.
- Indeed resume: Upload the destination-domain resume. Update monthly.
- LinkedIn profile: Optimize the headline, summary, experience, and "Open to Work" badge. Update weekly.
The 3 platforms are complementary. The First Day AI Job Search Plan is calibrated for all 3.
FAQ: Naukri profile optimization
How often should I update my Naukri profile?
At least monthly. The algorithm's freshness signal is "last updated." A profile updated 6+ months ago is marked stale. The fix: update at least monthly, ideally weekly.
What's the right CTC to set?
Set the current CTC accurately. The expected CTC should be 30-50% above the current CTC for a typical job change. The recruiter-search filter respects the CTC fields.
How many skills should I list?
8-12. The Skills section is 8-12 keywords, not 25. The top 4-5 should be the destination role's top keywords.
Should I list certifications I don't have?
No. The algorithm doesn't favor unverified certifications. Recruiters check. The fix: list certifications only if you have them, and only if they're verified.
How long should the headline be?
50-60 characters. The headline is 4-6 keywords, the seniority, the YOE, and the location.
Should I include my photo?
Yes. A profile with a clear, professional photo ranks higher than a profile with no photo. The photo should be head-and-shoulders, well-lit, neutral background.
What if my current title is in a different domain?
Reframe the title to the destination role's vocabulary. The 3-bullet reframe applies to the title. The work is honest; the title is the bridge. If the profile keeps getting filtered before recruiters see it, the 48-hour fix for rejected domain changers covers the rest of the profile.
How do I know if my profile is in the top 5%?
The Naukri algorithm doesn't show the rank directly. The proxy is the response rate. A profile in the top 5% gets 4+ recruiter messages per week. A profile below the top 50% gets 0-1 messages per week. The fix: optimize the 11 fields; the response rate increases.
What if the algorithm filters me out for CTC?
The recruiter-search filter respects the CTC fields. If you're filtered out, the fix is to update the CTC fields accurately. A candidate with 10 LPA current should have 13-15 LPA expected; the filter is at the recruiter's discretion.
What if I'm switching domains?
The 3-bullet reframe applies. The title, the experience bullets, and the Skills section are reframed. The headline is rewritten. The reframe is the bridge.
What if I have 0 recruiter messages?
The profile is in the bottom 50% of the algorithm's ranking. The fix: optimize the 11 fields (1-hour plan), then maintain the weekly cadence. The response rate will increase.
What if I have 4+ recruiter messages per week already?
The profile is in the top 5%. Maintain the weekly cadence. Don't break what works.
What if the recruiter's message is irrelevant?
Respond anyway. The response rate is a signal. The irrelevant message is a data point. The algorithm tracks response rate; the recruiter's behavior is influenced by the response.
How do I know which keywords to use?
Read 5-10 JDs for the destination role. The recurring terms are the keywords. The top 5 keywords are the Skills section, the headline, and the key skills per role.
What if the destination role's keywords change?
Update the headline, the Skills section, and the key skills per role. The algorithm's ranking is updated to match the new keywords. The update is the fix.
What if I'm not getting any callbacks?
The 5-check test on the resume is the first place to look. The Naukri profile optimization is the second. The 1-hour optimization moves the needle. The fix: optimize the 11 fields, then maintain.
Related reading
- Why domain changers get rejected — and the 48-hour fix — the filters that catch title mismatches before a recruiter ever reads the resume.
- Mechanical to software: the 90-day plan — the full roadmap for the "Senior Mechanical Engineer → Senior Software Engineer" reframe above.
- How to negotiate salary in India (2026 playbook) — what to do when the recruiter messages and expected-CTC conversations turn into offers.
- How to Optimize Your Naukri Profile in 2026 (Field Guide) — the full field-by-field pass, in the order recruiter search runs.
- How Many Key Skills Can You Add on Naukri? — the 50-skill limit, the character cap, and how to choose.
- How Many Search Appearances on Naukri Is Good? — 2026 benchmark ranges and the ratio that predicts calls.
- How Recruiters Search Candidates on Naukri (Resdex Guide) — the five stages of recruiter search, decoded.
- Is Naukri Premium Worth It in 2026? — what the paid services change, what candidates report, and when paying beats the free levers.