The pattern we see, week after week
A founder writes a job description for a "Senior Backend Engineer." The JD asks for 8+ years experience, deep Go expertise, distributed systems at scale, payment infra background, and a target comp of ₹65 LPA. The founder believes this is reasonable. The recruiter believes this is reasonable. The hiring manager has signed off. Three weeks in, the search is stuck.
The problem is not effort. The recruiter has approached 180 profiles. The problem is that the role described — at that comp — does not exist in the volume the search assumes. The market for that exact profile in Bangalore is somewhere between 80 and 140 people total. Maybe 12-15 are open to a conversation in any given month. And the compensation anchor is ₹20 LPA below what most of them are currently making.
Three signals the brief is wrong
The three diagnostic questions we ask before any search starts:
| Question | What it tells you |
|---|---|
| What is the total addressable pool for this exact profile in this city? | If the answer is under 200, you are running a sniper search. Process and patience matter more than volume. |
| What does the 60th-percentile comp look like, not the median? | Strong candidates are above median. If your offer sits at median, the strongest 40% will not engage. |
| What would make a candidate switch in the next 90 days? | If the answer is "more money," the search will not close. The candidates worth hiring rarely move for cash alone. |
