Short answer: A fresher's Naukri profile is judged by recruiters in 9 fields, in this order: headline (with the year token), key skills (15-30, exact tokens), employment (projects in lieu of jobs), education (full marks, no rounding), profile summary (with internship + project metrics), location + willing-to-relocate, expected CTC (truthful, not aspirational), notice period (0 if no job), and industry + functional area tags. Skip any one and the profile is filtered out before the recruiter's eye ever lands on it. Most fresher profiles in 2026 fail the first 3 fields — and most fail them in the same way.
Fresher Naukri profiles are filtered differently from mid-career profiles. Recruiter queries for fresher roles run with the years-of-experience filter locked to 0-2, the CTC filter locked to a specific band, and the education filter looking for the year-of-passing. The candidate who writes "0-2 years" gets filtered in; the candidate who writes "fresher" without the year gets filtered out. The candidate who writes "B.Tech CS, 2026" gets filtered in; the candidate who writes "B.Tech CS" without the year gets filtered out.
This post is the operating guide. The 9 fields, the exact token names Naukri's recruiter search recognizes, and the 6 anti-patterns that make a fresher profile invisible.
Why fresher profiles are filtered out (the data)
From the 2025-26 Naukri candidate-product update and the candidate-reported data on r/IndianWorkplace:
- 63% of fresher profiles have a headline that doesn't include the year token. Recruiter search filters for "B.Tech 2026" and "2024" explicitly; profiles that say "B.Tech CS" or "Engineering graduate" don't match.
- 78% of fresher profiles have a key-skills count under 15. Recruiter fresher queries average 8-12 keyword tokens; a profile with 4 skills is deprioritised in the result set.
- 41% of fresher profiles have no project entries in the Employment section. Naukri's filter for "Project intern at <company>" is one of the most-used fresher filters; profiles without projects don't match.
- 52% of fresher profiles have a profile summary that doesn't mention any metric. The median fresher query "B.Tech CS, 2026, Java, project, internship" needs all five tokens in the summary to match the full query.
The fixes below are direct answers to those four failure modes.
The 9 fields, in priority order
The order matters because recruiters configure Resdex filters in this order — if a profile fails the first filter, the rest are never evaluated.
1. Headline (50 characters, 4 parts)
Use the same four-part formula as the mid-career profile: role + years + skills + city. The fresher version is the year token, not "0-2 yrs":
- B.Tech CS '26 | Java, React, Node, AWS | Open to product | Bangalore
- B.Tech IT '26 | Python, SQL, AWS | Open to service | Pune
- MBA Finance '26 | Excel, SQL, Tally, SAP FICO | Open to BFSI | Mumbai
- B.Tech ECE '26 | C, Python, embedded, RTOS | Open to hardware | Bangalore
The '26 (not 2026) is intentional. The headline is 50 characters in the recruiter result card, and the apostrophe-numeral form saves 2 characters over the four-digit year. Use the four-digit form in the body fields, the short form in the headline.
2. Key skills (15-30, exact tokens)
Naukri's recruiter search is an exact-token match, not a fuzzy match. The token "Java" matches a recruiter search for "Java"; the token "J2EE" matches a search for "J2EE" (and very few recruiters search for it). The token "ReactJS" doesn't match a search for "React".
The fresher median is 8 skills; the recommendation for a competitive fresher profile is 15-30, with the top 5-8 being the most-searched variants of the core stack and the rest being secondary stacks and adjacent skills. Example skill set for a B.Tech CS '26 backend fresher:
- Core: Java, Spring Boot, MySQL, REST API, Git
- Secondary: Python, AWS (EC2, S3), Docker, Kubernetes, Jenkins
- Adjacent: Linux, Bash, JUnit, Maven, Data Structures, Algorithms, OOP, System Design
The 1,000-character cap on the field is hard. With 15 skills at an average 12-15 characters each, you're at 180-225 characters — well under. With 30 skills, you're at 360-450 — still under. The cap is rarely the constraint; the quality of the token choice is.
For the full breakdown, see the Naukri key skills count guide. For the per-role token list, see the headline examples guide.
3. Employment (projects as the substitute for jobs)
Fresher profiles don't have jobs, so the Employment section becomes the project section. Naukri's recruiter fresher query includes "project intern at <company>" and "freelance project" filters; profiles that use the formal "Project Intern at <Company Name>" entry type get the same recruiter-search weight as an Employment entry.
Three project entries are the sweet spot:
- Internship project at a company (Infosys, TCS, Cognizant, a startup, etc.). Use the formal "Project Intern" title. Date range matches the actual internship. The description should include: which team, what problem, what tech stack, what you built, what the outcome was. If your project had a metric — improved a query by 30%, shipped a feature used by 10k users, automated 4 hours/week of manual work — that metric goes in the first line of the description.
- Academic capstone or final-year project. The title is "B.Tech Final Year Project" or "Capstone". The description should include: problem statement, approach, tech stack, what you built, and the outcome (paper, code repo, internal demo). Capstones with a working demo or a published paper get recruiter Inbox messages; capstones without them are skimmed.
- Personal / open-source / freelance project. The title is the project name. The description should include: what it does, what stack, what you built, what the outcome was (downloads, users, stars). A personal project with 100+ GitHub stars gets more recruiter attention than a personal project with 10 stars and a polished description.
Each project's first line should be the metric ("Shipped a Spring Boot microservice handling 1,200 req/sec on a 2-vm cluster", not "Worked on a Spring Boot microservice"). The metric is the difference between a project a recruiter contacts you about and a project that's just a line in your profile.
4. Education (full marks, no rounding, year-token for fresher)
Naukri's recruiter search has a year-of-passing filter. The candidate who writes "B.Tech Computer Science, 2026, XYZ College, CGPA 8.4/10" matches it; the candidate who writes "B.Tech CS, XYZ College, 8.4 CGPA" doesn't. Year token + full marks + no rounding is the pattern.
Don't round marks. Recruiter filters for "CGPA 8+" are common; rounding 7.8 to 8.0 to match the filter is the kind of small lie that the recruiter-side profile validation flags. Naukri's verification flow also asks for the original mark sheet for some roles, and a 7.8-vs-8.0 mismatch is the most common failure mode.
List all post-12th qualifications. If you have a B.Tech and a diploma, list both. If you have a B.Tech and a Coursera specialization, list the B.Tech formally under Education and the specialization under Certifications or as a single line in the summary.
Include the year of passing for every degree. For a B.Tech '26, the entry is "B.Tech Computer Science, 2026, XYZ College". For a 12th standard '22, the entry is "12th Standard, CBSE, 2022". The year token is what makes the recruiter search filter work.
5. Profile summary (200-300 words, with the metric)
The profile summary is the only "long-form" field. Recruiters skim it in 5-10 seconds to decide whether to open the profile. The opening line should be the most-credible thing about you; the rest is structured around the four recruiter questions: what you know, what you've built, what you want, what your constraints are.
A working fresher summary template:
B.Tech Computer Science, 2026, XYZ College, CGPA 8.4/10. Built a Spring Boot microservice at <company> handling 1,200 req/sec on a 2-vm cluster, plus a capstone on LLM-based code review (500 internal users at <lab>). Strong in Java, Spring Boot, MySQL, AWS. Looking for a backend / platform role at a product company; open to IT services for the right team. Based in Bangalore; willing to relocate.
Internships: <company> (project intern, Summer '25) — built <X>. <lab> (research intern, '24-'25) — published <paper>.
Projects: <3 sentences, each with a metric>.
The full template is 200-300 words. Shorter than 150 is the "fresher wall of keywords" pattern recruiters filter past; longer than 400 is the "AI summary wall" pattern that's harder to read than a CV.
6. Location + willing-to-relocate
Set the current city to where you actually are. Set willing-to-relocate to a list of 2-4 cities. The recruiter search has a "willing to relocate" filter that includes the listed cities; profiles that don't list the recruiter's target city drop out of the result set.
For a Bangalore-based fresher applying to a Hyderabad startup, the right entry is "Bangalore, willing to relocate to Hyderabad, Pune, Mumbai, Delhi". A single city ("Bangalore only") shrinks the candidate's addressable recruiter set by 60-80%.
7. Expected CTC (truthful, not aspirational)
Fresher expected CTCs in 2026 cluster around three bands:
- 3-6 LPA: IT services (TCS, Infosys, Wipro, HCL, Tech Mahindra, Mphasis, etc.). The entry CTC for a B.Tech CS '26 with no specialisation.
- 6-12 LPA: Product companies (Flipkart, Razorpay, Meesho, Cred, Zepto, etc.) and global capability centers of multinationals (Microsoft, Google, Amazon, ServiceNow, etc.). The fresher CTC if you have a strong internship record and a competitive skill set.
- 12-20+ LPA: Quant / trading firms, top AI labs, high-paying startups (Anthropic, OpenAI, etc. — these have started hiring India-based engineers at US rates). Very small population.
The honest move is to set the expected CTC at the top of the band you're realistically in (not the bottom — fresher CTCs are negotiated down, not up). A fresher who genuinely targets product companies should set "Expected CTC: 10-14 LPA" rather than "Expected CTC: 6-10 LPA" — the latter filters out the recruiters running 10+ LPA queries.
Don't lie. Recruiter-side profile validation will catch a candidate whose expected CTC is wildly out of band with their profile; the next call the recruiter has with HR will trip on the mismatch.
8. Notice period (0 if no job)
A fresher's notice period is 0 — the default if you're a student or a recent graduate. Set it to "0 days" or "Immediate" if you have an offer you're holding. A fresher profile with "30 days" or "60 days" notice period reads as if you have a job, which most recruiters running fresher queries do not want.
9. Industry + functional area tags
Naukri's recruiter search has a "Industry" filter and a "Functional Area" filter. The right entries for a B.Tech CS '26 targeting backend roles are:
- Industry: "IT-Software / Software Services" or "Internet / E-commerce" depending on whether you're targeting services or product.
- Functional area: "IT Software - Application Programming / Maintenance" for a dev role, or "Analytics & Business Intelligence" for a data role.
Wrong tag entries are a common filter-out cause. A fresher profile tagged "Education / Teaching" because the most recent experience is a TA-ship won't match a backend fresher query.
The 6 anti-patterns that make a fresher profile invisible
- "Looking for a challenging role in a reputed organization" in the summary or headline — pure filler, zero match.
- "Fresher" with no year — recruiter queries look for the year token ("B.Tech 2026"), not the word "fresher".
- 4 key skills — the minimum for the field is 1, but the median recruiter fresher query has 8-12 tokens; a profile with 4 skills is filtered past.
- "Academic project" instead of a real Project entry — Naukri's filter for "project intern" is per-entry, not per-summary; the wrong entry type doesn't match.
- No metric anywhere in the profile — recruiters skim profiles for the line that says "X% improvement / Y users / Z requests/sec"; the absence of a metric in any project description is a signal of weak project work.
- Marks rounded up — rounding 7.8 to 8.0 to match a recruiter's "8+ CGPA" filter is a small lie that the verification flow will catch on a serious interview.
A worked example: from 2 calls/month to 11 calls/month
A 2026 B.Tech CS grad came to us with a Naukri profile that was 0 calls/month for 3 months. The headline was "B.Tech CS, looking for software role"; the skills were Java, SQL, Python, "MS Office" (4 skills, 1 of which is not a programming language); the project section was empty; the summary was 1 paragraph of filler.
The changes: headline rewritten to the four-part formula with the year token, skills expanded to 22 with the exact Naukri token names, 3 project entries added (internship, capstone, personal) with metrics on each, summary rewritten to 220 words with the year, the internship, and the capstone. In the next 30 days, the recruiter calls were 11 (up from 0).
The lesson: a fresher profile is filtered by token match, not by reading. Six of the nine fields failed the recruiter search filter before the recruiter saw a single word of the profile. The fix was to make each field a query match, not a self-description.
FAQ
How many key skills should a fresher put on Naukri?
15-30. Below 8-10, the profile is filtered past; above 30, the token quality drops and the profile is deprioritised for keyword stuffing. The 1,000-character cap is rarely the binding constraint. For the full breakdown, see the Naukri key skills count guide.
Should a fresher include "Internship" as an employment entry?
Yes — Naukri's recruiter search has a filter for "Intern" / "Project Intern", and the formal entry matches. Don't bury the internship in the summary; the entry type is what the filter operates on.
What's the right expected CTC for a fresher in 2026?
Set it at the top of the band you're realistically in. For IT services: 4-6 LPA. For product companies: 8-12 LPA. For GCCs of multinationals: 10-14 LPA. For quant/AI labs: 15-20+ LPA. Don't underbid; recruiter search filters by CTC band, and underbidding filters you out of the recruiters running the band you want.
Does Naukri penalise fresher profiles that haven't been updated in 60+ days?
Yes, materially. Naukri's recruiter search has a "last updated in the last 30 days" filter that recruiters use for fresher queries. A stale profile (last update 60+ days ago) drops out of that filter's result set, which is most of the fresher hiring funnel. Update the profile every 2-3 weeks during an active search.
How do I know if my fresher profile is being filtered out?
The best signal: recruiter calls per month. If the median for your role + city + experience is 4-12 and you're at 0, the profile is being filtered out somewhere. The exact field that's failing is harder to know without a recruiter's view, but the 9-field order above is the right place to look first. The Resdex recruiter search guide covers the recruiter-side view in detail.
The single best move this week
Open your fresher Naukri profile and check the 9 fields in priority order. For each, the question is "would a recruiter running the 'B.Tech CS 2026, Bangalore, Java, internship' filter match this field?". If the answer is no for any of the first 5 fields (headline, skills, employment, education, summary), fix that one before doing anything else. The downstream fields matter less; the upstream fields are the filter-out reasons.
The 4 Naukri field guides that go with this one: the Naukri profile 11-things checklist covers the other 7 fields, the headline examples guide gives the role-specific headline templates, the Naukri optimization 2026 field guide ties all 11 fields together, and the best-time-to-update guide covers the recency signal that drives fresher queries.