Salary Transparency in India: We Read 29,778 Live Job Descriptions

You have felt this one. You read a job description end to end — the responsibilities, the “must-haves”, the four paragraphs about culture — and the one number that would tell you whether any of it is worth your time is simply absent.

We wanted to know how universal that is, so we measured it. We took the full text of every live job description in JobTether's scraped pool on 26 September 2026 — 29,778 job descriptions from 1,057 company career boards hiring in India — and searched each one for an actual compensation figure.

Five of the six systems this pool is read from publish their job-board interfaces: Greenhouse, Lever, Workable, Ashby and SmartRecruiters. The sixth, Workday, serves the same data to any browser from its career sites. Nothing here needs our scraper to reproduce.

0.7% of them stated a salary. And of that 0.7%, almost exactly half were denominated in a foreign currency.

We first published this on 1 August 2026 (6,309 job descriptions: 1.8% stating pay, 0.9% in rupees), re-ran it on 23 September (6,236: 2.0% and 1.1%) and again on 24 September, when the pool had nearly tripled (17,696: 1.0% and 0.6%). By 26 September it had grown again, to 29,778 job descriptions from 1,057 boards, almost all of the growth from large employers on Workday. That change in the sample is why the numbers below fell, not a change in the market. The 19,310 Workday postings state pay just 37 times (0.2%); the rest of the pool discloses at about the rate it always has (1.7%). The finding itself only got firmer.

The headline numbers

We sorted every job description into three buckets: it names a figure, it gestures at pay without a figure, or it is silent.

More than nine in ten job descriptions do not raise the subject of money at all. Not a range, not a band, not even the word “competitive”.

The disclosure that exists is mostly not Indian

This was the finding we did not expect. Of the 210 postings that named a figure, we split them by the currency they used:

• 107 (51%) in rupees — LPA, lakhs, or an explicit ₹/INR amount.
• 103 (49%) in foreign currency: 84 in US dollars, 6 in UAE dirhams, 5 in euros, 3 in Polish złoty, 2 in Australian dollars, and one each in Singapore dollars, New Zealand dollars and Philippine pesos. A few of these are postings listed in several countries at once, India among them, quoting the pay for another country.

Half of India's visible pay transparency is coming from overseas employers and offshore-staffing firms advertising into the Indian market — companies operating under norms, and sometimes laws, from somewhere else. Strip those out and INR-denominated salary disclosure is 107 postings out of 29,778: 0.36%. Fewer than four in a thousand.

The remote split says the same thing from another angle. Remote-eligible roles named a figure 5.5% of the time against 0.5% for onsite roles, an 11x gap. And although remote roles are under 5% of the pool, they account for 36% of all disclosures.

Who discloses, and who never does

Disclosure is not spread thinly across employers — it is concentrated in a handful of them while the rest never do it at all. Of the 549 company boards carrying 10 or more open roles, more than 500 did not state pay on a single posting.

That silent group includes most of the largest employers in the pool:

The employers that dodisclose are mostly small boards hiring for offshore or remote delivery work — Apt Resources (9 of 13), Fresh Prints (12 of 18), Fuku (7 of 13), Datamark (11 of 46). The clearest exception is Litmos, a learning-software company that puts a rupee range on every one of its 10 India postings, for example “₹22,00,000 to ₹28,00,000 plus 10% bonus” for a Cloud Engineer. These are not the household names. They are companies for whom stating the number is a recruiting advantage rather than a disclosure risk.

By city, seniority and ATS

The metro breakdown contains a mild surprise. Bengaluru — the largest job market in the pool by a distance and the centre of Indian tech — is among the least transparent of the major metros, ahead only of Pune and Chennai.

By seniority, disclosure falls as the role gets more senior: 1.0% for entry-level titles, 0.8% for mid/unlabelled, and 0.6% for senior, lead and director roles. The pattern is intuitive — senior compensation is individually negotiated and more variable, so publishing a band constrains the employer more.

There is also a large split by applicant tracking system: Workable-hosted boards disclosed 3.9% of the time, Greenhouse 1.5%, Ashby 1.2%, and Lever just 2 postings in 2,057. Workday, the system most large enterprises use, managed 37 in 19,310. That mostly reflects which kinds of employers choose each platform rather than the software itself — the same effect we saw when we measured how stale postings are by ATS.

India is now an outlier, not the norm

This used to be how hiring worked everywhere. It is not any more. As of 2026, 16 US states and Washington DC require a good-faith pay range in the posting itself, and the EU Pay Transparency Directive — whose transposition deadline passed on 7 June 2026 — extends a similar obligation across all 27 member states, requiring pay information in the vacancy notice or before the first interview.

India has no such requirement, and the data shows what a market looks like without one: 99.3% of postings keep the number private. That is the honest context for the advice that follows. Nothing is going to change this for you in the next quarter, so the question is how to work inside it.

What to actually do about it

1. Ask on the screening call, not later.With more than 99% of postings silent, the recruiter call is the first real chance to find out. “What budget has been approved for this role?” is a normal question — it targets the requisition, not the person, which makes it far easier to answer honestly than “what will you pay me?”
2. Treat “competitive salary” as zero information. Our data shows it appears on 6.9% of postings with no correlation to anything. It is not a signal that pay is good; it is a placeholder.
3. Give a researched range, not a single number, when asked first. The asymmetry is the point of the silence — you are expected to name a figure without knowing theirs. Anchoring with a band you can justify is the standard counter. Our guide to answering the salary expectations question covers the wording.
4. Prioritise the disclosers. A posting that states a number has pre-filtered itself for you. If it is below your floor you have saved four rounds of interviews; if it is above, you know the ceiling before you invest.
5. Do the negotiation where it counts. Since the range is invisible until late, most of your leverage arrives at the offer stage — which is exactly when most candidates stop pushing. Our salary negotiation guide covers that conversation.

Methodology, including what we got wrong first

We are showing the errors as well as the result, because the errors are where a study like this usually goes wrong quietly.

What we did.On 26 September 2026 we took a single snapshot of the full JD text of every job in the pool — 29,815 postings, of which 29,778 had readable text — across Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Workday boards, all filtered to India-based roles. We then searched each JD for a compensation figure using patterns for Indian and foreign formats: LPA, lakhs, ₹/Rs/INR amounts, and pay-word-adjacent numbers like “CTC 12,00,000” or “Salary: USD 2,500”.

The two false positives that would have ruined the number:

• Company money read as salary.Our first pass returned 3.5%. Then we noticed one company scored 57 out of 57 — because every one of its JDs carries boilerplate about an “Annualized Total Payment Value of over INR 150 lakh crore”. That is business volume, not pay. Another board's JDs mentioned “₹5,000 crore invested” by its customers. Requiring pay context and rejecting company-scale money language took the figure to 2.2%.
• Benefits read as salary.One board then scored 21 of 27 — on “health coverage up to INR 10 lakh” and “life insurance worth 3× your annual salary”. Those are perks, and the second one contains the word “salary”, so a keyword test passes it. The fix was proximity: we take the label nearest to the number on its left. “Coverage up to INR 10 lakh” is a benefit; “Salary Range - INR 80K-160K” is pay, even when the words “Group Medical Insurance” appear earlier in the same sentence. Final figure: 1.8%on the August snapshot, 2.0% on 23 September, 1.0% on the larger 24 September pool, and 0.7% on the 26 September pool. On that last run we read every disclosure by hand and removed one more false positive: a “P2P (Process to Pay)” process line.

Limitations, stated plainly:

• We measured the JD text, not structured pay fields.Some applicant tracking systems have a separate salary-range field that renders outside the description body. A posting using only that field would count as “silent” here. This is the most likely source of under-counting, and it means 0.7% is best read as a floor for disclosure in the JD itself.
• Conservative by design. After the corrections above, the detector requires a number to be explicitly labelled as pay. A JD that discloses in an unusual phrasing will be missed. We preferred under-counting to a headline inflated by boilerplate.
• This is not the whole Indian job market.It is company career boards on six modern ATS platforms, which skews toward tech, startups, GCCs and organised mid-to-large employers. Naukri-native listings, consultancy postings and walk-ins are not included — and Naukri's own structured salary field behaves differently from JD prose.
• Disclosure is not accuracy.We measured whether a number appears, not whether it is honest. A wide band like “5–25 LPA” counts as disclosure here while telling a candidate almost nothing.

The takeaway

The silence is not an oversight by individual companies; at 99.3% it is the market norm, and it is a norm that works in the employer's favour. You cannot fix that from your side of the table. What you can do is stop treating the missing number as something to be polite about — ask early, treat vague language as noise, and reserve your energy for the roles and the moments where the figure is actually decided.

And when you do get to that conversation, make sure the application that got you there was worth it. We also measured how many live Indian postings are already months stale — about a quarter of them — which is the other half of why job hunting here feels like shouting into a void.

The tables behind this study are free to download and cite (CC BY 4.0) on our research and data page.