How to evaluate a job offer in India: a five-factor check
Score the offer on five factors: where the cash sits on your role-and-city market band, how much of the CTC is guaranteed, what the employer type does to your trajectory, whether the role change compounds your next move, and how easily you could leave. Band position gates the decision; the other four rank offers that pass it.
Updated 2026-07-14 · By the Instill team
What our data shows
- 6+ in 24h
- first-person offer-evaluation threads we logged on r/developersIndia in a single day — the strongest single-day signal for this decision since we began scanningInstill demand scan, 14 Jul 2026
- 42 comments in 3 hours
- on one dilemma we tracked — leave a comfortable non-tech IT job for an IBM associate role in Bengaluru at ₹35k/month — the classic band-versus-trajectory tradePublic r/developersIndia thread observed in Instill demand scan, 14 Jul 2026
- 27 comments
- on an 18 LPA PSU-versus-private-software dilemma the same week — stability-versus-band is a live, recurring decision, not a textbook examplePublic r/developersIndia thread observed in Instill demand scan, 14 Jul 2026
- 5
- factors in the CCP offer evaluation — and only one of them (band position) is a gate; the rest are rankersCompensation Correction Protocol (CCP)
- 40%
- the spread city choice alone puts on the same role's fair price — evaluating a Bengaluru offer against a Tier-2 anchor (or the reverse) is the most common self-assessment error we seeCCP city calibration (expert estimate, see provenance note)
Band figures and city multipliers are calibrated expert estimates from Instill's salary-case practice, not published survey data. Demand-scan observations reference public forum threads (paraphrased, dated inline) logged by Instill's daily scans.
The five factors
Most offer regret traces back to evaluating on one axis — usually headline CTC, occasionally brand. The CCP evaluation scores five, in a fixed order, because they fail in different ways and at different times.
| Factor | Question it answers | Gate or ranker | Where it fails you if ignored |
|---|---|---|---|
| Band position | Where does the guaranteed cash sit on the P25–P90 band for this role, experience and city? | Gate | Below-P25 offers compound: every future hike calibrates against a broken anchor |
| Structure quality | How much of the CTC is guaranteed monthly cash versus at-risk or notional? | Ranker | A P60 headline with 25% variable can bank like a P40 |
| Employer type | Product, services, GCC, PSU, startup — what band and what ceiling does this class carry? | Ranker | Employer type sets the band your next three hikes calibrate against (~15% product uplift) |
| Growth moment | Does this role change what your CV says in two years — scope, stack, market? | Ranker | A flat lateral at +30% cash is often worth less over five years than a scope jump at +15% |
| Exit optionality | Notice period, bond or service agreement, clawbacks, skill marketability at exit | Ranker | A 90-day notice plus an 18-month clawback is a lock you priced at zero on joining day |
Band position gates everything
Price the role first: take the market band for the role and experience in the offer's city (apply the multipliers from the hub guide — Bengaluru 1.0×, Delhi NCR 0.9×, Pune/Hyderabad/Chennai 0.75×, Tier-2 0.6×, product uplift +15%), and place the offer's guaranteed cash on it. Above P50: negotiate the extras. P25–P50: negotiable if a growth factor is exceptional. Below P25: the offer is asking you to subsidize the role — walk, or treat the negotiation as a correction, not a tweak.
The ₹35k Bengaluru dilemma our scan tracked this week is the canonical hard case: an offer far below any band, carried entirely by the trajectory argument (non-tech to tech, Tier-2 to Bengaluru). The five-factor answer is that a below-P25 gate can be consciously overridden exactly once in a career stage, when the growth moment genuinely rewrites your market — and even then with a 12-month exit plan attached, because the anchor damage is real and compounding.
The stability trade has a price — make it explicit
PSU-versus-private dilemmas — like the 18 LPA HPCL case in this week's scan — are five-factor problems wearing a lifestyle costume. A PSU typically scores high on structure quality (nearly all guaranteed cash) and exit optionality is misleading in both directions: leaving a PSU is easy, but returning to its scarcity value is not. What it caps is factor four: the growth moment mostly stops repeating. The honest comparison is not this year's CTC but the five-year integral: private-software offers re-price every 18–24 months if you manage the band; PSU compensation moves on pay-commission time.
A decision rule that survives deadline pressure
Offer deadlines exist to prevent exactly this analysis, so pre-commit: gate on band position; strike anything failing exit optionality you cannot negotiate away (bonds, unexplained clawbacks); then rank survivors on structure, employer type and growth. If two offers remain within 10% of each other after that, take the one with the better manager and stop optimizing — at that margin the variance is in the humans, not the numbers. And ask for a week in writing; an employer that will not give seven days to a five-year decision is itself a data point.
The methodology
Compensation Correction Protocol (CCP) — offer evaluation module
CCP evaluates offers with the same city-calibrated P25–P90 bands used in hike-case diagnosis, so an offer decision and a correction case never disagree about what the market pays. The interactive version scores your specific offer on all five factors and flags which of the three levers — negotiate, accept, or walk — the evidence supports.
Developed and maintained at Instill. AI-assisted methodology, expert-verified.
Run this on your own numbers
The Salary Hike Case Builder walks your specific situation through this methodology — band diagnosis first, free — and builds the case document at the end.
Start the free diagnosisQuestions people ask
- Should I take a below-band offer from a big brand?
- Only if it is your one conscious gate-override: the brand or role genuinely rewrites your market position, you cap the experiment at 12–18 months, and you plan the correction (internal or external) from day one. A brand discount accepted passively becomes your permanent anchor.
- How do I evaluate an offer when I have no competing offer?
- The band is your competing offer. An offer at P40 for your role and city is 'competing' against the P50–P75 the market pays — negotiate against the band, not against your current salary. That is the entire point of pricing the role before the conversation.
- The recruiter wants an answer in 48 hours. What do I do?
- Ask for a week, in writing, citing a specific reason (family discussion, notice-period math). Most deadlines move; the ones that do not are usually protecting a weak structure from scrutiny. Run the gate factor (band position) immediately — 48 hours is enough for that even if the full comparison must wait.
- How much should the manager and team weigh in the decision?
- As the tie-breaker, decisively — but only after the financial factors are within 10%. A great manager on a below-band offer is buying your goodwill at a discount; a mediocre manager on an at-band offer can be survived and out-transferred.
- Does a long notice period at the new employer matter at accept time?
- Yes — it is exit optionality you are selling. A 90-day notice prices at roughly one lost opportunity per future job search (offers that will not wait a quarter). It is negotiable at offer stage more often than people try; it is nearly non-negotiable after joining. See the notice-period guide for the exit-side view.