Divya Kulshreshtha
Case Study · Naukri PremiumX · 2026
Case Study · Info Edge Naukri PremiumX

Search that carries a recruiter's judgment.

Naukri already held most of India's premium talent. The market didn't believe it — and the product gave recruiters very little reason to. PremiumX is the flagship tier built on top of Resdex, the company's core revenue product; I led design across web and app. This case study is about the part that took longest to get right: teaching a search product to argue for a candidate, not just return one.

Naukri PremiumX premium hiring experience FIG. 01 — Premium discovery surface
i
Perception, not supply
002 / 009
The business case

The talent was already here. The market didn't believe it.

This didn't arrive as a design brief. It arrived as a business problem. Naukri holds the overwhelming majority of India's premium white-collar talent, and is still read by the market as the place you go for volume — not for a VP. Recruiters working senior roles were starting somewhere else, often paying several times more to do it, and the perception was losing enterprise conversations before a product demo ever began.

When I went looking for why, the answer wasn't supply. Even when the right people sat in the database, the route to them ran through a search built for a different job. A pool you can't reach is, from a recruiter's seat, indistinguishable from a pool that isn't there.

What was true 85%+

of India's premium white-collar professionals — CTC above ₹30L — were already on the platform.

What the market believed

"Senior people aren't on Naukri."

The same sentence kept coming back — from enterprise accounts, from our own sales leaders, from the recruiters I sat with. Premium candidates weren't there. Passive candidates couldn't be found. The profiles that were there couldn't be trusted.

None of it was an inventory problem. Every one of those sentences traced back to something the product was doing, or quietly defaulting to, inside search.

Pool figure published by Naukri (Info Edge); premium defined as CTC > ₹30L, estimated from FY'23 ITR projections. Source: Naukri PremiumX announcement.

And it didn't thin out at the top.

The usual answer to "85% of the pool" is that the missing 15% is the part you actually want — the CXOs, the people who'd never keep a profile updated. It isn't. Availability holds almost flat from a ₹30L mid-level hire to a ₹1Cr+ executive, which is the single number that should have changed the conversation and never got told.

India's premium pool 18.5L

professionals earning above ₹30L, across every sector and seniority.

Already on the platform 16L

of them hold a profile — the inventory the market assumed didn't exist.

Open to a move in a year 9.4L

active within twelve months, which is the pool a live mandate can realistically reach.

Availability by seniority — the cut that mattered
Mid level₹30L – 50L · Principal Engineer, Sr. PM, AVP
85%11.2L of 12.5L
Senior level₹50L – 1Cr · Director, Head of Sales, VP
84%4.5L of 5.2L
Executive level₹1Cr+ · BU Head, CHRO, MD, Country Head
85%83K of 90K

Company figures from Naukri's corporate pitch deck, shared here under NDA. Pool sizes are estimates projected from FY'23 ITR data, not audited counts — I've kept them because the shape is the point, not the decimal.

Three complaints, three things the product was doing.

I took the sentences recruiters kept repeating and traced each one back to a mechanic in the product. Each turned out to be a design decision rather than a market truth — which is the only reason any of it was fixable.

“

I don't see enough premium candidates.

What was underneath

Premium, diluted in a mixed pool

Premium and non-premium profiles came back in the same result set, so the premium half never read as premium. A recruiter paying for senior talent was scrolling past everyone else to find it — and concluding the pool was thin.

~60% of premium searches ran as mixed searches
“

Profiles aren't up to date, and aren't accurate.

What was underneath

The screening fields were the unreliable ones

Not general data decay — specifically CTC, experience, current company, notice period. The exact fields a senior shortlist turns on were self-declared and often stale, so recruiters confirmed all of it on a call before trusting any of it.

~50% of year-active profiles inaccurate on CTC & experience · 20% current company and role · 14% skills · 12% notice period
“

I can't find passive profiles.

What was underneath

A default that hid them

Search defaulted to candidates active within six months, and almost nobody changed it. The passive half of the pool — the half that matters most for senior roles — was excluded before a keyword was typed. The product was manufacturing the perception it was being blamed for.

~70% of searches ran on the ≤6-month activity default

Figures from Naukri's internal analysis of premium search behaviour, reviewed with the product team — shared here under NDA and directional rather than audited. They're the reason the same three sentences kept repeating.

The frame I was handed.

The business case came with its own structure: four things a corporate buyer is told they need in order to hire premium talent. It's a clean sales frame and it shaped the brief. Two of the four survived contact with recruiters. The other two were describing the wrong problem — which is most of what the next two sections are about.

i

Talent availability

A pool deep enough that the right person is in it at all. The one pillar that was already true — and the one nobody outside the company believed.

ii

Faster discovery

Find and identify premium candidates quickly. Stated as a speed problem. This is the one I ended up designing against.

iii

Easier connect

Reach candidates where they'll actually respond. True as far as it goes — but more channels wasn't the missing piece.

iv

Cost-efficient hiring

Maximise outcomes, minimise spend. Real — though at this level the cost that decides anything is the wrong hire, not the licence.

Then the part no default could fix.

Cleaning up the pool and the defaults gets a recruiter to the right people. It doesn't help them choose between them — and at this level, choosing is the entire job. Three things made that hard before a single screen existed.

01 / 03

The deciding signal isn't a field

Pedigree, company scale, how long someone stays, whether they've moved from startup to enterprise. What separates two similar-looking CVs is a pattern across a profile, not a value inside it.

02 / 03

The recruiter isn't the only reader

A shortlist has to survive a hiring manager who wasn't in the search. Recruiters need language for why this person over that one — and a row in a result list gives them none of it.

03 / 03

A wrong hire compounds for years

At this level the real cost isn't the tooling or the time-to-fill. It's the eighteen months spent discovering the hire was wrong, and starting again.

The bet the tier was built on

If someone is hiring for a premium role, PremiumX should be the only place they need to open — the pool, the proof it's real, and the case for a shortlist in one product instead of three.

ii
Sitting with senior recruiters
003 / 009
The User Perspective

They weren't trying to go faster.

I went in expecting time pressure. What I heard was a confidence problem. Senior recruiters can find profiles — what's hard is knowing which of the eleven credible people in front of them is the one worth defending. Speed was never the bottleneck. Judgment was, and the product carried none of it.

So the research turned into one question the product had never modelled: what is a senior recruiter actually reading when they look at a profile for four seconds?

Signal 01 — tenure pattern

Stability is read as a shape, not a number

Nobody looks at total years of experience. They look at the shape of the stints — three-year averages read as commitment, a run of eighteen-month moves reads as risk, and one long stint next to one short one reads as a story worth asking about.

What search showed instead

Total experience, as a single number.

Signal 02 — company type

Two identical titles, different jobs

A Staff Engineer at a product company and one at a services firm have done different work, even when the keywords match perfectly. For premium roles this is often the first cut a recruiter makes — and it was invisible in search.

What search showed instead

A company name. The recruiter had to already know the company.

Signal 03 — stage & scale

Scale is the thing that doesn't transfer

Someone who grew a team from four to forty inside a Series-C is a different bet from someone who ran forty inside a five-thousand-person org. Recruiters were reconstructing this by hand, company by company, from memory.

What search showed instead

Nothing. Company scale wasn't a searchable idea.

Signal 04 — institute pedigree

"Premium institute" means something different per role

For a strategy hire it's a specific set of business schools. For a silicon role it's a different set of engineering institutes that barely overlaps. Every recruiter was maintaining a private version of this list and rebuilding it inside a query, every single time.

What search showed instead

A free-text education field.

Signal 05 — verification

Trust was happening outside the product

Current CTC, notice period, actual designation — the details that decide whether a conversation is even worth starting. Recruiters were confirming these on calls and in spreadsheets, days before the first real interaction.

What search showed instead

Self-declared fields, treated as facts.

Signal 06 — the second reader

The shortlist has to survive a second reader

Every recruiter described the same downstream moment: defending a shortlist to a hiring manager who wasn't in the search. They needed the distinguishing detail in language they could repeat out loud.

What search showed instead

A match percentage. Impossible to argue with, impossible to argue from.

iii
Reading the brief correctly
004 / 009
The Real Problem

The brief said "premium search." That wasn't the problem.

The ask arrived as a tier: build a premium variant of Resdex, price it higher, win leadership hiring. Held against what recruiters actually described, five assumptions inside that sentence didn't survive.

i

The brief assumed

Premium hiring is slow — so make discovery faster.

What it actually was

Premium hiring is uncertain. Speed was never what recruiters were short of.

ii

The brief assumed

Recruiters need better results.

What it actually was

Recruiters need better reasons. A result you can't defend isn't a result.

iii

The brief assumed

Show more of the pool.

What it actually was

Show what the pool is made of. Volume without shape is just a longer scroll.

iv

The brief assumed

Reach candidates across more channels.

What it actually was

Reach them with more context. The outreach was never the missing part — the relevance was.

v

The brief assumed

Win on price — be the cheaper premium option.

What it actually was

Win on predictability. A fixed search quota isn't a discount, it's a different shape: a head of talent can plan a year of senior hiring against it, which per-message and per-seat pricing makes impossible. And the cost that actually decides anything is hiring wrong twice.

THE FRAME THAT SHAPED EVERY DECISION AFTER

So I stopped designing a faster search, and started designing one that could hold an opinion — surfacing the pattern a senior recruiter would have assembled by hand, in language they can repeat to a hiring manager.

iv
What I designed
005 / 009
The flagship moment

Three things the base product could never do.

Before the principles and the feature work, this is the shape of what a recruiter actually gets in PremiumX — and each one answers, directly, a sentence they'd been saying for years.

i

Active and passive, in the same view

No activity default silently deleting the better half of the pool. Someone who changed jobs eight months ago and someone who applied this morning appear in one result set, with availability stated plainly on both — so a recruiter can weigh the approach rather than discover it later.

Answers“I can't find passive profiles.”
ii

A pool that's premium all the way down

Every profile in a PremiumX result is a premium profile. The mixed result set — the one that made a deep pool read as a thin one — doesn't exist in this tier. Nothing to scroll past, and no reason left to assume the senior people are elsewhere.

Answers“I don't see enough premium candidates.”
iii

Naukri Checked, with the CTC broken down

Not a verified tick. 14+ details cross-checked by Naukri — including a validated CTC breakup rather than one self-declared number, plus notice period, designation, company duration and location. The screening call, already made.

Answers“Profiles aren't up to date, and aren't accurate.”
The Product

Four principles, then the features.

PremiumX shipped as a distinct tier inside Naukri's design system — elevated and quiet, across web and app, without breaking the workflow recruiters already had. Everything in it traces back to four rules I held the work to.

i

Depth before speed

A shallow pool searched quickly is worse than a deep pool searched carefully. Availability comes first; everything else is downstream of it.

ii

Show the pattern, not the score

A single match number renders beautifully and settles nothing. Surface the evidence a recruiter would have assembled by hand instead.

iii

Verification is product, not homework

If a recruiter has to leave the product to confirm something, the product hasn't finished its job.

iv

Arm the recruiter, don't automate the relationship

At this level, outreach is human work. The product's job is making sure that human arrives with something worth saying.

CAPABILITY — 01 / 06 ● The unified pool

The people who aren't looking, surfaced first

Classic search assumes a good result is someone who wants a job. For senior roles that assumption filters out the strongest candidates before you start. PremiumX puts active seekers and passive premium professionals into one search — and deliberately weights toward the passive half, because that's the half a recruiter could never reach on their own. The active pool was never the hard part.

The pool itself is premium-only, which matters more than it sounds. Mixing tiers in one result set was what made a deep pool read as a thin one; separating them is what let the depth finally be visible.

Passive-weighted Premium-only results Availability stated, never hidden
active seekers passive premium one unified view FIG. 02 — Active + passive, one pool
NChecked ctc breakup notice period designation job-search status location duration skills + 7 more 14+ details cross-checked by Naukri FIG. 03 — Verification, moved inside the product
CAPABILITY — 02 / 06 ● Verified trust

NChecked — the legwork, already done

The verification recruiters were doing on calls and in spreadsheets, moved inside the product. Naukri's team cross-checks 14+ details on a profile — company duration, notice period, designation, location, job-search status and more — so the first conversation starts from confirmed ground rather than from claims.

The one that changed conversations most was compensation. Not a single self-declared CTC number, but a validated breakup — because at senior levels the number is rarely the number, and a recruiter who has to ask about it on a first call has already spent the call.

It appears twice on purpose: as a filter while you're narrowing, and as a badge while you're deciding. Those are two different jobs, done at two different moments.

CAPABILITY — 03 / 06 ● Encoded hiring patterns

Where this team actually hires from

Every recruiting team has a pattern it can't articulate — the kinds of companies its good hires keep arriving from. Not just the industry, but the stage, the scale, and the way those places operate. Similar Companies reads that pattern from a team's own hiring history and expands a search along it: the twenty companies a recruiter would have listed from memory, plus the ones they'd have forgotten.

The distinction that made it work — not "companies in the same sector," but companies of the same flavour.

Stage & scale match Learned from real hires Beyond sector tags
this team's past hires stage · scale · culture pattern Series C · fintech · 400 ppl Growth-stage · product-led Post-IPO · same operating scale same sector · wrong stage same sector · wrong scale matched on flavour, not on tag FIG. 04 — Similar companies, by flavour
Strategy role IIM-A · B · C ISB · XLRI · FMS IIM · tier 2 Silicon role IIT-M · B · KGP IISc · BITS NIT · VLSI programmes overlap: almost none one filter, role-aware nobody types a college name FIG. 05 — "Top institute" is role-dependent
CAPABILITY — 04 / 06 ● Pedigree, per role

"Premium institute" isn't one list

What counts as a top institute depends entirely on what's being hired for — the set that matters for a strategy role and the set that matters for a silicon role barely overlap. Recruiters were each carrying a private version of this and rebuilding it inside every query.

Top Institutes encodes it as a role-aware, one-click filter: the right engineering, business or specialist institute set for the role in hand, without anyone typing a college name or maintaining a list.

Role-aware sets One click, not a query No list to maintain
CAPABILITY — 05 / 06 ● Connect, carrying context

Arriving with something worth saying

A senior candidate who isn't looking owes you nothing, and the first message is the whole audition. PremiumX opens the channels they actually answer on — phone, WhatsApp, email, notification, inbox — from inside the shortlist, so outreach doesn't mean leaving the product and rebuilding context somewhere else.

But the channel was never the hard part. What makes a first approach land is knowing the compensation shape, the notice period and the one thing about this person's trajectory worth naming out loud — all of which the recruiter now has before they type. The product doesn't automate the relationship. It makes sure the human starts the conversation already informed.

Phone · WhatsApp · email · inbox Context travels with the contact No automated sequences
what the recruiter already knows ₹48L · fixed 39 + var 9 30-day notice · Bengaluru avg 3.4 yrs / stint startup → enterprise phone whatsapp email inbox · notif a first message a senior person answers written by the recruiter, not the product FIG. 06 — Channels carry the context, not the message
one word, two different seniorities global taxonomy CXO Executive Manager Associate reads as senior how India uses it CXO VP · Head Manager Executive two years out of college same word ranked on Indian seniority, not translated titles · salary bands · institutes · company stage FIG. 07 — Why a global taxonomy mis-ranks Indian seniority
CAPABILITY — 06 / 06 ● Premium matching

A ranking that reads context, not keywords

Generic matching scores keyword overlap, which is exactly why relevance collapses at the top of the market — the ten most senior people for a role rarely describe themselves the same way. The PremiumX ranking reads what recruiters said actually decides: industry context, company stage and scale, the shape of someone's tenure, and the recruiter's own shortlisting history.

Underneath that sits the argument I'd defend hardest. Seniority vocabulary doesn't port between markets. "Executive" in a global title hierarchy describes a senior operator; in India it routinely belongs to someone two years out of college. A matcher trained on global hierarchies gets Indian seniority wrong in precisely the band this product exists to serve — so the ranking runs on an India-specific taxonomy, reading titles, salary bands, institute tiers and company stages the way they're actually used here.

It's the least visible thing in the product and the reason everything above it works — which is why it's last here rather than first. A recruiter should never have to think about it.

Industry context India-specific taxonomy Learns from your shortlists

And one piece that hadn't shipped yet

iimjobs & hirist · in build

Info Edge already owns the two networks where a large share of India's senior product, tech and business talent actually spends its attention — iimjobs and hirist. A recruiter searching in PremiumX shouldn't have to know that, or run the same mandate three times.

The design was a single surface: recommendations from both networks suggested inside the PremiumX workflow, and one job post reaching all three. It was in build when I wrote this, so I've marked it rather than claimed it — but it's the clearest example of the positioning working, where the tier stops being a search product and starts being the destination.

v
Reading, not retrieving
006 / 009
The intelligence layer

The part that reads, not just retrieves.

Surfacing the right people is half the job. The other half is the reading a recruiter would otherwise do by hand — across the whole pool, then across one profile, then down to the single detail worth repeating to a hiring manager. Three layers, zooming in.

INTELLIGENCE LAYER — 01 / 03 ● Pool intelligence

Read the whole pool before reading anyone

Before scrolling a single profile, a recruiter sees what the search actually returned — the product/service split, the seniority and institute mix, how much of it is verified, and the standout profile types inside it.

A result count tells you how much work is ahead. This tells you what kind of pool you're hiring from — and, often more usefully, whether the query itself was wrong.

Pool highlights Segment breakdown Query sanity-check
2,480premium profiles for “Staff Frontend Engineer · fintech”
Pool insights
Product · 64%Service · 36%
38% Tier-1 institute 52% 5–10 yrs exp 2.1k NChecked
Standout profile types in this pool
Design-system leads Payments frontend Startup → enterprise movers
FIG. 08 — Pool-level highlights & segments
Ananya Rao Staff Frontend Engineer · Bengaluru
AI summary
Search Staff Frontend Engineer · fintech · React

8 yrs building consumer fintech UIs — led the React design-system rebuild at a Series-C startup, now scaling it inside an enterprise. Strong on payments-grade frontend and team leadership; every stint 3 yrs+.

✓ High credibility — 14 details NChecked, no gaps in tenure
FIG. 09 — Search-specific candidate summary
INTELLIGENCE LAYER — 02 / 03 ● Search-aware summaries

A summary written for this search

For each candidate, a short read tied to the role actually being hired for — drawn from their real trajectory rather than a generic bio, and rewritten when the search changes.

It answers the only question a recruiter asks before opening anything: is this worth my next ten minutes?

Query-specific Credibility signals Rewritten per search
INTELLIGENCE LAYER — 03 / 03 ● Profile signal chips

The context that sets a candidate apart

Each profile distilled into the signals recruiters described reading — average years per stint, product versus service background, startup-to-enterprise trajectory, institute tier, promotion velocity, team size. The things they'd otherwise have dug out by hand.

These are also, deliberately, the sentences a recruiter repeats in a hiring manager review. That's the real reason they exist. Not a score to trust — evidence to argue with.

Stint stability Product / service Startup → enterprise
Ananya Rao 8y exp · ₹48L · 30-day notice
Profile signals
Avg 3.4 yrs / stint Product company Startup → enterprise Tier-1 institute 2 fast-track promotions Leads team of 12
Signals summarise what sets this profile apart — no profile-opening required.
FIG. 10 — Differentiating profile chips
vi
Where the product stops
007 / 009
The human layer

Some mandates don't get solved by a search box.

PremiumX ships with people attached — a paid, expert-led sourcing service and a concierge layer for enterprise accounts. Portfolios usually hide this part, because a service sitting next to the software reads as an admission that the software wasn't enough.

I'd argue the opposite. Past a certain altitude the constraint stops being discovery and becomes the recruiter's own attention: the search takes minutes, the screening and the persuading take weeks. Designing the tier honestly meant drawing the line where software stops helping and saying so out loud — instead of adding one more feature to the screen and calling it solved.

Service tier 01

PremiumX Assist

Premium & senior mandates · ₹30L – 75L

A dedicated team of Naukri recruiters takes sourcing and screening off the client's desk entirely, so their own hiring team spends its hours interviewing rather than combing a database. The product is still underneath it — the difference is who's driving.

What lands5 interview-ready candidates per mandate
Service tier 02

PremiumX Assist Plus

Leadership mandates · ₹75L and above

Same shape, different altitude. Leadership searches where the credible list is short, every approach is bespoke, and a clumsy first message is visible across an industry. Volume tooling is the wrong instrument here and everyone involved knows it.

What lands5 interview-ready candidates, each individually approached

How a mandate actually moves.

Three steps, and the second one is the one that carries the weight.

01 / 03

Delegate sourcing and screening

The client hands over a mandate, not a keyword string. Naukri's team does the work of turning the hiring need into an approach — which is where most of the judgment lives.

02 / 03

Receive a pre-qualified shortlist

Only candidates already screened and already interested. A matching shortlist and an interested shortlist are different objects, and at senior levels the second one is the only one worth having.

03 / 03

Get interviews scheduled

Scheduling runs off the client's feedback, so the loop closes inside the service instead of landing back on an in-house recruiter's calendar.

And a layer above the tooling.

Concierge support sits with enterprise accounts through the whole mandate rather than at the point of search. Four things it does that no filter does.

i

Mandate structuring

Turning a vague role into a searchable, defensible brief before any sourcing starts. Most senior searches that fail, fail here — long before a tool is involved.

ii

Sourcing craft

Boolean construction and curated shortlists pulled from Resdex. The part recruiters consistently said takes longest to do well, done by people who do only this.

iii

Live market benchmarks

Salary and location data at the moment of the decision, so a counter-offer conversation runs on evidence rather than on someone's instinct about the market.

iv

Pipeline visibility

Real-time tracking of where every candidate sits — which is the thing a hiring head is actually asking for whenever they ask for an update.

vii
The calls I had to make
008 / 009
Decisions & trade-offs

Six calls that could have gone the other way.

None of these were obvious at the time, and each one cost something. They're the decisions I'd want to be asked about.

Decision 01

Signal chips instead of a single match score

A percentage is cheaper to build, cheaper to render, and tests well — people like a number. It also ends the conversation. Nobody can take "92% match" into a hiring manager review and do anything with it.

What I chose

Six to eight discrete signals per profile, each one a sentence a recruiter can repeat out loud. It's noisier, it eats vertical space, and it forced a much harder ranking problem underneath. It's also the only version that survives the second reader.

Decision 02

Elevating passive talent without overselling it

The value of PremiumX is the half of the pool that isn't job-hunting. The risk is just as clear — rank those profiles highly and a recruiter burns outreach on people who never reply, then stops trusting the product entirely.

What I chose

Passive profiles rank alongside active ones, but availability is stated plainly on every card rather than buried in a detail view. The product argues that someone is worth approaching. It never implies they're waiting.

Decision 03

The same thing in two places, on purpose

NChecked exists as a filter in search and as a badge on the profile. By design-system logic that's duplication, and it was challenged on exactly those grounds.

What I chose

Both stayed. The filter serves narrowing — a bulk decision made before you've looked at anyone. The badge serves judgment — one decision, about one person, while you're looking at them. Same data, two different jobs; collapsing them would have broken one.

Decision 04

Designing against the speed frame

Every product in this category markets premium hiring on speed, and speed demos beautifully. It's also the wrong goal here — nobody hiring a VP is trying to do it faster, they're trying not to do it twice. Building for speed would have meant fewer signals, more automation in the outreach, and a single score.

What I chose

Confidence over speed, everywhere the two competed. It cost surface area — denser cards, more to read, a slower first impression — and it's the reason this earns a flagship tier rather than being a faster search box.

Decision 05

Putting a human service next to the product

Assist and Concierge are people doing, by hand, work the product is nominally built to do. The argument against was blunt and fair: a service beside the software signals the software isn't sufficient, and every mandate that goes to a recruiter is a mandate not teaching the product anything.

What I chose

Ship both, and stop pretending the line wasn't there. Above a certain mandate value the bottleneck isn't discovery, it's attention and persuasion — neither of which a screen supplies. The honest version of a flagship tier includes the part where a person takes over, and designing that handover well is more useful than hiding it behind another feature.

Decision 06

An India-first taxonomy over a portable one

A global seniority model is cheaper to maintain, easier to explain, and travels to any market Info Edge might enter next. Building the ranking around Indian title conventions, salary bands, institute tiers and company stages means none of it generalises — every new market would need the work done again.

What I chose

India-specific, deliberately. A global model mis-reads Indian seniority precisely in the band this product sells into — "Executive" alone would have mis-ranked an entire tier of candidates. Portability is worth nothing if the ranking is wrong in the only market you're currently in.

viii
Looking back
009 / 009

The hard part was never finding people. It was giving a recruiter something to say about them.

i

What worked

Every feature that landed traces back to a sentence a recruiter said out loud. The ones that tested weakest were the ones I'd reasoned into from the brief — and the perception gap only started closing once the product could answer those sentences directly, instead of trying to out-market them.

ii

What I'd redo

The intelligence layer arrived after the filters and the pool work. The signals turned out to be the product's actual argument — they should have been designed first, and everything else built to deliver them.

iii

What it proved

A premium tier isn't a pricing decision with a skin on it. It earns the name only when a recruiter working senior roles has no reason left to start anywhere else.

16L

premium professionals (CTC > ₹30L) holding a profile on the platform

9.4L

of them active within a year — the pool a live mandate can actually reach

14+

details cross-checked by Naukri on every NChecked profile

1,800+

enterprise customers using PremiumX for premium and leadership hiring

Company figures — business metrics for the product, not design-attributable outcomes. Pool sizes are estimates projected from FY'23 ITR data rather than audited counts, premium defined as CTC > ₹30L; taken from Naukri's corporate pitch deck (shared under NDA) and its public announcement. Sources: Naukri PremiumX announcement, Storyboard18.

Connect for the full story

Premium discovery that earns its place.

There's more behind the ranking model, the NChecked trust layer, the service tiers and the rollout across web and app — including the parts that didn't work. I'm glad to walk through the decisions and trade-offs directly.

← All selected work Plate Nº 05 / 006 · Naukri PremiumX Agentic Recruitment →