Telecom Hiring in India: The Skills in Demand for 2026
How 5G, fibre, cloud-native cores and private networks rewrote the telecom skill mix — plus indicative pay bands and how to reskill rather than only hire.
Read more →
Most employers who say hiring developers in India is hard are describing a symptom, not a cause. The role stays open four months. Three candidates accept and two never join. The shortlist arrives full of CVs inflating two years of work into five. Each is a separate failure with a separate fix, and lumping them together as “the market is tough” guarantees none get fixed.
This guide breaks the problem into the nine challenges that actually cost employers time and money when hiring software developers in India, and pairs each with something concrete you can change this quarter. It closes with a working hiring funnel and realistic drop-off ratios so you can size your pipeline instead of guessing. Written from live mandates as a recruitment agency in Mumbai staffing technology teams since 2001.
Challenge 1: Candidate ghosting and offer-drop
A strong developer in India frequently runs three or four processes at once. Offer-drop rates reported across the industry commonly sit in the 20 to 30 per cent range for in-demand technology roles, and the drop rarely happens the day the offer goes out — it happens in the middle of a long notice period.
What actually works: shorten the gap between final interview and offer letter to 48 hours. Ask at first screening how many processes the candidate is running and where each stands. Have the hiring manager, not HR, make the offer call. Then run a structured engagement plan across the notice period — a call in week one, a team introduction in week three, onboarding logistics confirmed two weeks before joining. Each touchpoint is a chance to detect wobble early.
Challenge 2: The 60 to 90 day notice period
Long notice periods are standard at most large Indian IT employers, and they are the single biggest reason a hire made in January starts in April. Worse, a long notice period is a long window for a counter-offer.
What actually works: budget for buyouts explicitly. Many employers release an employee earlier if the shortfall is paid, and a one-month buyout on a ₹18 LPA role is far cheaper than three more months of an unfilled position. Ask about buyout policy during screening, not at offer stage. Where the requirement is genuinely urgent, deliberately widen the shortlist to include candidates already serving notice or between roles.
Challenge 3: Salary inflation and counter-offers
Developers with in-demand skills often expect 30 to 50 per cent hikes to move, and their current employer will counter when the resignation lands. Counter-offer acceptance is common enough to plan for as a default, not an exception.
What actually works: approve a salary band before you start sourcing, not after you have fallen in love with a candidate. Screen on expectation early — a candidate 40 per cent above your ceiling is not worth four rounds. Pre-close on the counter-offer explicitly: “If your current employer comes back with a matching number, what will you do?” A candidate who answers that badly is telling you something useful.
Challenge 4: Inflated experience and CV fraud
Fabricated employment history, borrowed project experience, inflated current CTC and occasionally entirely fake employers are a real problem in Indian technology hiring — particularly at the two-to-six-year band and particularly for remote roles.
What actually works: verify before offer, not after joining. Insist on payslips or Form 16 for CTC verification, run PF/UAN employment history checks, and use a professional background verification vendor for education and prior employment. In interviews, ask candidates to walk through a specific decision they made on a project — people who did not do the work cannot answer follow-ups about trade-offs.
Challenge 5: Drowning in unfit applications
A job board posting for a backend role in a metro can pull several hundred applications, the large majority irrelevant. Screening them manually consumes days and the good candidates get buried.
What actually works: stop optimising for application volume. Write the brief around three non-negotiable requirements and state a realistic salary range in the advertisement — the single most effective filter available. Add a short mandatory screening questionnaire. For genuinely scarce skills, switch from advertising to direct approach entirely; targeted talent sourcing produces a shortlist of twelve relevant people rather than four hundred irrelevant ones.
Challenge 6: Assessing skill fairly
Whiteboard algorithm interviews screen for interview practice, not job performance. Unpaid eight-hour take-homes get declined by exactly the senior candidates you most want. Neither is solved by adding rounds.
What actually works: a 90-minute structured technical conversation plus one time-boxed practical exercise capped at two hours, reviewed live so you can probe the reasoning. Pair programming on a realistic problem is the highest-signal format for mid and senior engineers. Standardise a scorecard across interviewers so decisions are comparable, and cap the process at three rounds.
Challenge 7: Competing with GCCs and product companies on brand
Global capability centres and well-known product companies have brand recognition, structured career paths and often deeper pockets. A candidate weighing your 150-person company against a name their family recognises is not comparing on the axis you would prefer.
What actually works: compete on what they cannot offer — ownership of a whole product area, direct access to leadership, decisions made in days rather than quarters, a shorter commute. Make these concrete in the brief and the interview, not vague culture claims. And be faster: speed is a real weapon against organisations that need six weeks to schedule five panel rounds.
Challenge 8: Remote and hybrid expectations
Developer expectations on work location remain ahead of what many Indian employers offer. A fully on-site mandate in a metro shrinks your addressable pool substantially and pushes salary expectations up to compensate for the commute.
What actually works: decide the policy before opening the role and state it in the advertisement. If you require on-site, price it in and say why. If you can offer two or three flexible days, treat it as a negotiating asset for offer stage rather than giving it away in the first call.
Challenge 9: Retention past the 12-to-18 month mark
Filling a role only recovers half the cost. Attrition clustered around the first-year mark, usually driven by expectations mis-set during hiring, restarts the whole cycle.
What actually works: be honest in interviews about the unglamorous parts — legacy code, support rotations, client escalations. Candidates surprised at month three leave at month twelve. Structure a real 90-day onboarding with a named buddy and defined deliverables, and commit to a compensation review at twelve months rather than leaving it to an annual cycle the candidate may just miss.
The nine challenges, summarised
| Challenge | Why it happens | What actually works |
|---|---|---|
| Ghosting and offer-drop | Multiple simultaneous offers; long gap to joining | 48-hour offer turnaround; hiring manager makes the call; structured notice-period engagement |
| Long notice periods | 60–90 day standard at large employers | Budget buyouts; ask policy at screening; include candidates already serving notice |
| Salary inflation and counter-offers | Scarce skills; retention pressure on current employer | Pre-approved bands; screen expectations early; explicit counter-offer pre-close |
| Inflated experience and CV fraud | Weak pre-offer verification; intermediary padding | Payslip and UAN checks pre-offer; probe project decisions in depth |
| Volume of unfit applicants | Broad advertising; vague job briefs | Three non-negotiables; publish salary range; switch to direct approach for scarce skills |
| Unreliable skill assessment | Puzzle interviews and oversized take-homes | Structured technical conversation plus a two-hour capped practical; common scorecard |
| Brand disadvantage | Competing with GCCs and product companies | Sell ownership, leadership access and speed; be concrete, not aspirational |
| Remote and hybrid mismatch | Policy decided late or left ambiguous | Fix and publish the policy upfront; use flexibility as a closing asset |
| Early attrition | Expectations oversold during hiring | Honest interviews; real 90-day onboarding; 12-month review commitment |
The most expensive mistake is a slow decision after a good interview. In our experience across live technology mandates, the majority of losses on strong candidates trace back to a gap of more than a week between the final round and a firm offer — not to compensation. Before you open a role, get the salary band approved and the interviewers’ diaries blocked. A process that can move in 48 hours beats a process that pays five per cent more and takes three weeks.
Plan your pipeline: a realistic hiring funnel
Under-sized pipelines are why roles stall. The ratios below are indicative planning figures for a mid-level developer role in an Indian metro — a starting model to recalibrate against your own data after two or three hires.
| Stage | Indicative volume | Pass rate to next stage |
|---|---|---|
| Profiles sourced or applications received | 200 | ~15% |
| CV-screened as relevant | 30 | ~50% |
| Recruiter screening call completed | 15 | ~55% |
| Technical assessment or first technical round | 8 | ~50% |
| Final round with hiring manager | 4 | ~50% |
| Offers extended | 2 | ~75% accept |
| Offers accepted | 1–2 | ~80% actually join |
| Joined | 1 | — |
Two implications. First, two hires needs roughly 400 sourced profiles — or a far better-targeted 60, which is the entire argument for search over advertising. Second, the biggest leaks are CV screening and offer-to-joining. Tightening the brief fixes the first; disciplined notice-period engagement fixes the second.
Frequently asked questions
How many interview rounds should we run for a developer role?
Three is usually right: a recruiter or hiring manager screen, one substantive technical round with a practical component, and a final round covering design, collaboration and role fit. A fourth rarely changes the decision and measurably increases drop-off. If you need more signal, deepen a round rather than adding one.
Is it worth paying a notice-period buyout?
Frequently, yes. Where a vacancy is costing you delivery time, buying out one or two months is usually cheaper than the delay, and it closes the counter-offer window early. Agree the mechanism in writing and confirm the current employer will actually accept a buyout before committing.
How do we verify a candidate’s real current CTC?
Ask for the last three months’ payslips and the most recent Form 16 before releasing the offer, and cross-check employment dates through UAN or PF service history. Make it standard for every candidate and state it upfront in the process, so it never reads as an accusation.
Should we hire freshers to reduce cost?
Only if you have genuine mentoring capacity. Freshers are considerably cheaper on CTC but need six to nine months and senior engineer time before contributing independently. A common working ratio is one fresher per two experienced engineers; beyond that, senior productivity drops enough to erase the saving.
Fixing the process, not just the vacancy
Nearly every challenge above is solvable with process discipline: a tight brief, a pre-approved band, three rounds, verification before offer and real engagement through the notice period. None of it requires a bigger budget — it requires deciding these things before the role opens rather than improvising each time.
Ace Corporate Services has completed over 5,000 placements for 500+ client companies across 15+ industries since 2001, running technology mandates end to end — sourcing, screening, verification support and offer management. If your developer roles stay open too long or your offers keep dropping, see our IT recruitment services and permanent staffing, or contact us on +91-22-67554705 or info@acecorpsers.com.
Need hiring help right now?
Talk to a senior recruitment consultant today. Free consultation.
Post a Hiring Requirement →