.png)
Top Mistakes Global Companies Make When Hiring Talent in India
- Saransh Garg
- 2 days ago
- 11 min read
We have run cross-border hiring mandates for over a decade. The single most expensive error we see repeatedly, across US, European, and APAC clients is attempting to hire talent in India without understanding that India has no single labour market. It has six. Bengaluru's mid-level backend engineer expects ₹22–28 LPA. The same profile in Jaipur expects ₹12–16 LPA. A global company that benchmarks against a generic "India salary" and posts roles on LinkedIn without a local strategy will either overpay, underhire, or spend four months learning what we could have told them in four minutes.
The mistakes global companies make hiring talent in India often begin before the first JD is written. Companies treat India as a monolith. It is not. What works for hiring Java engineers in Pune will not work for hiring ML engineers in Hyderabad. The legal structure for a contract hire is entirely different from a permanent hire. And the compliance risk of getting it wrong is not theoretical it is a tax notice, a PF dispute, or a wrongful termination claim.
Why Global Companies Hiring Talent in India Get the Strategy Wrong
The problem almost never starts with a bad candidate. It starts with a bad brief.
When a US SaaS company with 300 employees comes to us wanting to hire 8 backend engineers in India, the first question we ask is: what hiring model are you using? In at least 60% of first conversations, the answer is either "we haven't decided" or "we'll just put them on contractor invoices." Both answers cost money.
India's primary legislation governing employment is the Industrial Disputes Act, 1947, the Contract Labour (Regulation and Abolition) Act, 1970, and for professional workers specifically the Shops and Establishments Acts enforced at state level (Maharashtra, Karnataka, Telangana, Tamil Nadu each have their own version). These laws determine whether your contractor is legally a contractor, whether your "vendor" arrangement creates deemed employment, and whether your EOR actually provides the liability shield you think it does.
One of the most repeated mistakes global companies make hiring talent in India is treating India like a hiring-on-demand market with no compliance backbone. Companies post on Naukri or LinkedIn, collect CVs, negotiate rates, and wire money to individual engineers as "consulting fees." This works until it doesn't typically when a disgruntled contractor files a complaint with the local labour commissioner claiming deemed employment, or when Indian tax authorities flag consistent payments to individuals without GST registration or TDS deduction.
We have also seen a second pattern: companies that do invest in structure but choose the wrong structure. A European firm hiring three engineers does not need a private limited company in India. Setting one up takes 3–5 months and creates permanent establishment risk. The right answer for that size is an Employer of Record (EOR). But many founders only discover this after paying a CA ₹4–6 lakhs to incorporate an entity they didn't need.
The talent market compounds these errors. India's Tier 1 tech cities Bengaluru, Hyderabad, Pune, Chennai have attrition rates between 22% and 28% annually in the mid-senior tech bracket. A company that hires without a retention structure built into the contract is effectively rehiring every 14–18 months.
Which Indian Cities Have the Best Tech Talent for Global Hiring Mandates
India genuinely has the talent. The question is where, and for what stack.
When we receive a mandate for cloud engineers, our first filter is city. Hyderabad has the deepest AWS and Azure bench driven by the cloud COEs that Microsoft, Amazon, and Google have built there over the past decade. If you are hiring for GCP-native roles, Bengaluru gives you the widest shortlist. For data science and ML, Bengaluru and Pune both have strong supply, but Pune tends to deliver more product-aligned profiles versus Bengaluru's research-heavy talent pool.
The mistake at this stage: posting a single JD nationally and waiting. This generates volume but not quality. A national post for a senior Kubernetes engineer gets 400 applications. Fewer than 15 will have production-grade multi-cluster experience. Fewer than 5 will be comfortable with English-only async communication, which most global roles require.
What Indian engineers for cross-border roles typically lack and this is a pattern we test for specifically:
Client-facing communication in Western business contexts. Engineers from Indian product companies are often excellent technically but have had limited exposure to direct client calls with European or US stakeholders. We run a structured communication assessment as part of every shortlist.
Documentation culture. Many strong engineers from Indian service companies are used to verbal handoffs. Global remote teams require written async documentation. We test this with a take-home architecture documentation task.
Ownership mindset versus delivery mindset. Engineers from large IT services firms are trained to execute tickets. Engineers from startups or mid-size product companies are more comfortable with ambiguity. For global companies building distributed product teams, the latter profile is almost always the right hire — but they cost 30–40% more and take longer to find.
For full stack roles, the mismatch between resume and reality is highest. India has hundreds of thousands of engineers who list React and Node.js. The number who can build and own a production-grade full stack system end-to-end including CI/CD, monitoring, and incident response is far smaller. We use a live coding and system design round with a standardised rubric to filter this gap before any profile reaches a client.
Indian Employment Laws Every Global Company Must Know Before Hiring
This section alone could save you ₹10–40 lakhs in avoidable penalties.
The three hiring structures available to global companies in India are: direct contractor engagement, Employer of Record (EOR), and entity-based hiring (own PLC or branch office). Each carries a different compliance obligation under Indian law.
Direct contractor engagement is governed by the Contract Labour (Regulation and Abolition) Act, 1970 (CLRA). Under CLRA, if your contractor works exclusively for you, works on your tools, follows your working hours, and receives deliverable-based payment that functions like a salary a labour commissioner can deem them a permanent employee. We have seen this happen to two clients. In one case, a 14-month contracting relationship was reclassified, resulting in a PF arrears demand covering the full period, plus penalties.
EOR hiring is the cleanest model for companies with fewer than 20–25 India headcount. The EOR becomes the legal employer, handles EPF (Employees' Provident Fund under the EPF & MP Act, 1952), ESIC (if applicable), TDS under Section 192 of the Income Tax Act, and state-level shop-and-establishment registration. Your liability is capped.
Key Compliance Mistakes Global Companies Make When Hiring in India
The mistake companies make here: choosing an EOR purely on price. We have reviewed EOR agreements where the indemnity clause had a cap of ₹5 lakhs far below the potential liability on a compliance failure. Read the indemnity clause. Ask specifically whether the EOR covers labour commissioner disputes.
Among the most damaging mistakes global companies make hiring talent in India is misclassifying seniority to save on EPF contributions. Some companies try to keep CTC below ₹15,000 per month base to avoid EPF applicability. This is detectable, it is non-compliant, and it creates exactly the liability you were trying to avoid.
For contract hiring specifically, ensure your agreement includes a clear IP assignment clause governed by the Information Technology Act, 2000, and a Non-Disclosure Agreement enforceable under the Indian Contract Act, 1872. Without these, IP ownership in cross-border contractor arrangements is genuinely ambiguous under Indian law.
Working with a trusted international hiring partner significantly reduces exposure to these compliance gaps particularly for companies without an India-based legal team.
India Hiring Compliance Checklist: 12 Checks Before You Make an Offer
Before you make your next India hire, run through this checklist. Every "No" is a risk.
# | Checkpoint |
1 | Hiring model selected (EOR / contract / entity) before JD is written |
2 | Salary benchmarked by city, not national average |
3 | JD reviewed by someone with India market knowledge |
4 | Employment/contractor agreement reviewed against CLRA 1970 or EPF Act 1952 |
5 | IP assignment clause present and governed by Indian Contract Act 1872 |
6 | TDS deduction process confirmed with EOR or payroll partner |
7 | Background verification (BGV) process defined before offer stage |
8 | Notice period expectation communicated upfront (typically 60–90 days in India) |
9 | Onboarding plan exists for remote IST-to-home-timezone async collaboration |
10 | Retention structure (variable pay, increment timeline) documented in offer letter |
11 | Probation period defined (standard is 3–6 months under most state Shops Acts) |
12 | Exit clause and severance terms reviewed against Industrial Disputes Act 1947 |
Three items that clients most often miss: Item 8 (notice periods — we have had clients lose a candidate to a competing offer during a 90-day notice buyout they weren't prepared to fund), Item 9 (async collaboration structure this is the number one reason offshore hires underperform in the first six months), and Item 12 (severance India's ID Act requires retrenchment compensation of 15 days' wages per year of service for employees with more than one year of continuous service).
Keep this checklist at offer stage. If you are working with an offshore recruitment agency, they should be walking you through every item here before the offer goes out. This checklist is one of the simplest ways to avoid the mistakes global companies make hiring talent in India — and it costs nothing to use.
How We Structured a 6-Engineer India Hire for a Netherlands Fintech And What Nearly Went Wrong
Our process for cross-border mandates follows a fixed sequence: intake call with the hiring manager (not just HR), city and stack analysis, JD localisation for the Indian market, sourcing from our candidate database plus targeted outreach, two-stage technical assessment, communication assessment, reference check, compliance structure confirmation, offer support, and a 30-day post-join check-in.
The communication assessment is the stage most agencies skip. We do not skip it. We have declined to submit candidates who passed the technical round because their written async communication was not at the standard the client's team required. That conversation is uncomfortable. It is also the conversation that prevents a bad hire.
The mandate that almost collapsed: A 180-person fintech company based in Amsterdam came to us for 6 senior backend engineers Java and Kafka to be hired on a remote contract basis and paid through their existing Netherlands-based payroll via wire transfer to individual bank accounts. We flagged immediately that this structure would create TDS and GST compliance issues on the Indian side. They pushed back their legal team had "cleared" it.
We paused the mandate, put together a two-page compliance note referencing Section 195 of the Income Tax Act (TDS on payments to non-residents in reverse and the Indian engineers' own filing obligations), and recommended an EOR structure. They agreed, we restructured, and placed all 6 engineers within 11 weeks.
What almost went wrong: one of the six candidates had already verbally accepted and was about to resign their current role before the structure was confirmed. We held that candidate's notice by keeping them engaged with a detailed project briefing and a written conditional offer. They waited. The hire went through.
Outcome: 6 engineers placed, average notice period funded partially by client (45 of 90 days bought out), all 6 still active 14 months later.
This is the kind of structural error we see most often when working with new clients — and it is entirely avoidable with the right offshore recruitment partner who understands both sides of the engagement.
India Tech Hiring Costs: Salaries, EOR Fees, and Total Employer Spend
All figures below are for permanent or long-term contract hires. EOR fee assumed at $400–600/month per head (market range for reputable providers).
Seniority | India CTC (Annual) | Employer Cost with EPF/ESIC | EOR Fee (Annual) | Total Annual Cost (USD approx.) |
Mid (4–6 yrs) | ₹18–24 LPA | ₹20–27 LPA | $5,400–7,200 | $31,000–41,000 |
Senior (7–10 yrs) | ₹28–40 LPA | ₹31–45 LPA | $5,400–7,200 | $44,000–62,000 |
Lead / Architect (10+ yrs) | ₹45–70 LPA | ₹50–78 LPA | $5,400–7,200 | $66,000–103,000 |
For comparison: A mid-level backend engineer in Amsterdam costs €75,000–90,000 fully loaded. The same profile from Bengaluru or Hyderabad on an EOR costs $31,000–41,000. The difference is real. What we see clients reinvest that difference into: additional headcount (the most common choice), a local product manager to bridge the distributed team, and in two recent cases, a dedicated QA engineer they had been deferring for over a year.
Agency placement fee is typically 8–12% of first-year CTC for permanent roles, or a fixed monthly fee for contract mandates. This is a one-time cost amortised across the tenure of the hire.
Conclusion
Over the next 12–18 months, we expect global companies to face two new pressure points in India hiring: the phased implementation of the Code on Social Security, 2020 (which will revise EPF and gratuity applicability thresholds and affect how EOR providers structure their agreements), and increasing scrutiny from Indian tax authorities on cross-border contractor payments that bypass formal payroll. Both changes make the compliance checklist above more important, not less.
In our live mandates right now, we are seeing a sharp increase in requests from mid-size US and European companies who previously tried to hire in India independently, encountered compliance friction or bad hires, and are now coming to us to rebuild their India hiring practice properly. The mistakes global companies make hiring talent in India are well-documented and entirely avoidable with the right structure in place from day one.
If you are at that stage or want to avoid reaching it the conversation starts here: Talk to our team
Interesting Reads:
FAQs
1. What is the biggest compliance mistake global companies make when hiring contractors in India?
The biggest mistake is treating long-term contractors like full-time employees. If a contractor works only for one company, follows fixed schedules, and uses company systems, authorities may classify them as employees. This can create liabilities for PF contributions, gratuity, and compensation claims. Several companies face heavy penalties because contracts were not structured correctly. Using a proper EOR or maintaining genuine contractor independence reduces this risk.
2. Why do global companies underestimate India’s notice period reality?
Most experienced engineers in India have notice periods of 60–90 days. Global companies often expect candidates to join within a few weeks, which creates hiring delays. Employers either wait, negotiate a notice buyout, or risk losing candidates to competitors. Discussing notice periods early avoids surprises during offer stages. Proper planning helps companies secure strong talent faster.
3. Which Indian cities offer the best value for mid-senior tech hiring?
Pune and Hyderabad provide strong technical talent with relatively moderate salary expectations. Bengaluru has the largest talent pool but also higher salaries and attrition. Chennai performs well for enterprise technologies and stable long-term hiring. For AI and ML roles, Bengaluru and Hyderabad remain the strongest markets. Each city offers different advantages depending on the role and budget.
4. Does the Social Security Code affect India hiring structures?
Yes, the upcoming Social Security Code may change payroll and compliance costs. It is expected to revise PF wage calculations and expand benefits for contract workers. Companies using EOR models may see pricing and compliance structures change. Businesses should review agreements carefully for future compliance adjustments. Preparing early helps avoid unexpected financial impact later.
5. How is IP ownership handled with Indian EOR employees?
When hiring through an Indian EOR, the EOR is the legal employer. Intellectual property created by employees must be clearly assigned to the client company through proper contracts. Without strong IP assignment clauses, ownership gaps can arise. Many standard EOR agreements fail to address this adequately. Legal review of all IP clauses is essential before signing.
6. What is a realistic hiring timeline for senior tech roles in India?
Hiring senior engineers in India usually takes several weeks from sourcing to offer closure. Screening, technical interviews, assessments, and negotiations all add time to the process. After the offer, notice periods further delay onboarding. In most cases, companies should expect a full hiring-to-joining timeline of several months. Planning ahead is critical for urgent projects and launches.
7. Why do some hires from large IT services firms struggle in product companies?
Engineers from large services firms are often trained for process-driven delivery environments. Product companies usually expect more ownership, proactive communication, and independent decision-making. Some candidates need time to adjust to product-focused work cultures. Strong screening for problem-solving and communication skills helps identify adaptable talent. Candidates who demonstrate ownership often succeed in distributed teams.
8. How should companies structure variable pay to reduce attrition?
Engineers in India expect regular performance discussions and salary growth. Fixed-only salary structures often increase attrition risk. A balanced fixed and variable pay structure with clear review cycles improves retention. Retention bonuses tied to longer tenure can also reduce employee exits. Transparent communication around increments is equally important for long-term stability.
9. What should companies evaluate in an Indian recruitment agency?
A strong recruitment agency should understand cross-border hiring expectations and communication standards. Agencies with their own candidate networks provide better access to passive talent. Good recruiters also highlight compliance and hiring risks early in the process. Replacement guarantees and post-hiring support are important evaluation factors. The right agency improves both hiring quality and speed.
10. Can global companies hire in India without a recruitment agency?
Yes, companies can hire independently, especially with experienced internal hiring teams. However, challenges include incorrect salary benchmarking, compliance risks, and limited access to passive candidates. Technical candidates may also struggle in global remote environments without proper assessment. Companies with local market understanding usually perform better independently. For many businesses, specialist agencies reduce risk and save time.
Comments