.png)
How European Companies Hiring in India: EOR vs Entity
- Saransh Garg
- 20 hours ago
- 12 min read
Setting up a legal entity in India costs between INR 8 lakh and INR 20 lakh in one-time legal, registration, and compliance fees, and the process takes 90 to 180 days before you hire a single engineer. For a German mid-market SaaS firm or a Dutch fintech expanding its engineering bench, that timeline alone can derail a hiring plan. European companies hiring in India via EOR vs entity is not a philosophical debate. It is a cash flow and speed decision that shapes your first two years of operations on the ground.
If you need three engineers in Bengaluru by next quarter, an EOR gets them onboarded in 10 to 14 days. If you need 40 engineers and plan to build a permanent GCC over three years, an entity eventually pays for itself. Everything in between is where companies consistently get it wrong, and where we have spent years helping clients make the smarter call.
Why European Tech Companies Cannot Find Senior Engineers at Home Anymore
The demand signal from Europe has been consistent and has accelerated sharply. The strongest inbound hiring mandates we receive are from Germany, the Netherlands, Sweden, Ireland, and France, primarily in cloud infrastructure, data engineering, and full-stack product development.
What is driving this is not just cost. European talent markets are structurally constrained.
Germany's Federal Employment Agency reported a shortage of over 137,000 IT professionals in recent years. The Netherlands has seen average software engineer salaries breach EUR 90,000 annually for mid-level roles, making scaling a 20-person engineering team prohibitively expensive for Series B and C companies.
Swedish tech companies we work with regularly cite six-to-nine-month hiring timelines for senior backend engineers domestically. Ireland, which hosts European headquarters for several large US technology firms, faces acute shortages in cybersecurity and cloud operations.
India, by contrast, produces approximately 1.5 million engineering graduates annually. Cities like Bengaluru, Hyderabad, Pune, and Chennai carry deep, established talent pools for exactly the roles European companies need most. The talent availability is not theoretical. We fill these mandates in weeks, not months.
What is important to understand is that India's employment compliance framework is among the most layered in Asia. You are not just hiring engineers. You are navigating the Shops and Establishments Act at the state level, the Employees' Provident Fund and Miscellaneous Provisions Act 1952, the Payment of Gratuity Act 1972, the Code on Wages 2019, and in some states, Professional Tax obligations that vary by city. Getting any of these wrong creates retroactive penalties and can complicate an exit or restructure of the team later.
Which Indian Cities Actually Deliver for European Tech Hiring
When a European company asks us where to build their team, the answer depends entirely on the role. We stopped giving a blanket Bengaluru recommendation years ago because it has not been accurate for every stack.
For cloud and DevOps roles, Bengaluru and Hyderabad remain dominant. Both cities have a large cohort of engineers with AWS, GCP, and Azure certifications, and a mature culture of platform engineering. If you are a European company building out cloud engineering capacity, these two cities give you the deepest bench with the shortest sourcing timelines.
For data engineering and AI or ML roles, Pune and Bengaluru lead. Pune in particular has a strong cohort of engineers trained by product companies and GCCs over the last decade. We regularly source senior data engineers and machine learning engineers from Pune for European clients who need Python-heavy, pipeline-focused profiles.
For full-stack and Java development, Chennai and Bengaluru stand out. Chennai has a disproportionately strong Java developer ecosystem, partly because of its legacy as a hub for banking and insurance technology. For European fintech clients specifically, Chennai often outperforms other cities in relevant domain experience.
One thing Indian engineers across all cities typically lack for European clients, and this is something we test for explicitly, is hands-on experience with GDPR implementation at the code level. Many strong engineers have heard of GDPR but have never worked in a codebase where data residency, right-to-erasure pipelines, and consent management were first-class engineering concerns.
We screen for this with scenario-based technical questions, not just CV keywords. We have turned down candidates who passed the algorithm round but could not explain how they would architect a data deletion workflow compliant with Article 17 of the GDPR.
What the Legal Framework Actually Means for European Companies Hiring in India EOR vs Entity
Under Indian law, the moment you have people on Indian soil drawing a salary, you have employer obligations, regardless of whether you have registered a legal entity. This is the single most common misconception we encounter from European companies entering the market for the first time.
If you hire through an Employer of Record (EOR), the EOR becomes the legal employer in India. They handle EPF contributions, currently 12 percent of basic salary from both employer and employee, ESIC where applicable, gratuity provisioning under the Payment of Gratuity Act 1972, and TDS deductions under the Income Tax Act 1961. Your company holds a service agreement with the EOR, not an employment contract with the individual engineer.
If you incorporate a Private Limited Company under the Companies Act 2013, you become the direct employer. You then carry your own compliance stack: monthly PF filings, annual returns, labour law registrations under the Shops and Establishments Act in whichever state your office is in, and, if you cross 10 employees, ESIC registration in applicable wage brackets.
The mistake we see most often is a European company signing a statement of work with a freelancer or a small Indian vendor, paying a monthly retainer, and believing they have avoided the employment relationship entirely. Under Section 2(s) of the Industrial Disputes Act 1947, the definition of workman is broad enough to cover many contractor relationships if the nature of the work, supervision, and dependency suggest employment. A Dutch SaaS company we worked with had been running this arrangement for 14 months with three engineers before their Indian legal counsel flagged the misclassification risk. They converted to an EOR structure within six weeks of receiving that advice.
For contract hiring, the EOR model provides the cleanest legal wrapper, especially for European companies not yet ready to commit to permanent infrastructure. For scale-ups moving toward a GCC model, the entity route becomes the right answer once team size and long-term commitment justify the fixed compliance overhead.
EOR vs Entity Decision Framework: Which Model Fits Your India Plans
Use this framework before making the call. We use a version of this internally when advising clients during intake.
Decision Factor | EOR Is the Right Call | Entity Is the Right Call |
Hiring timeline | Need engineers in under 30 days | Can wait 90 to 180 days for setup |
Team size in Year 1 | 1 to 15 engineers | 15 or more engineers with growth plan |
Commitment horizon | 12 to 24 months, testing India | 3 or more years, building permanent capacity |
Budget for setup | Avoid INR 8 to 20 lakh upfront legal cost | Can absorb one-time entity cost |
Compliance appetite | Want compliance fully outsourced | Have in-house legal or finance to manage |
Payroll complexity | Standard fixed salaries | Variable pay, ESOPs, complex structures |
IP ownership priority | EOR contract includes IP assignment clauses | Entity gives tighter IP control |
Exit flexibility | EOR exit is 30 to 90 days notice | Winding down entity takes 6 to 18 months |
Talent attraction at senior level | Less critical at early stage | India Pvt Ltd branding helps attract senior talent |
GCC ambition | No GCC planned | GCC is the medium-term goal |
How to read this: if you tick five or more boxes in the EOR column, start with EOR. If the entity column dominates, the entity route will serve you better over a three-year horizon despite the higher setup cost. If it is genuinely split, we recommend a 12-month EOR pilot with a contractual right to convert employees to entity payroll without triggering a fresh notice period.
This is a structure we have negotiated into several European client engagements at the outset.
One important cost note: EOR fees in India typically range from USD 150 to USD 400 per employee per month depending on the provider and salary level. Over 24 months with a team of 10, that is USD 36,000 to USD 96,000 in EOR fees alone. That math changes the entity-versus-EOR decision materially once you cross 12 to 15 headcount.
How We Place Engineers for European Clients: Process and a Real Proof Point
Our process for European companies begins with a three-day scoping exercise covering employment law exposure, existing vendor relationships in India, and the seniority mix of roles needed. We do not run generic discovery sessions. We run structured intake that surfaces the compliance and operational decisions early.
For technical roles, we run a four-stage assessment.
First is a structured screening call covering role-specific depth and GDPR or data compliance awareness.
Second is a timed technical test calibrated to the client's actual stack, not generic coding puzzles. Third is a live architecture or problem-solving session with one of our senior technical evaluators.
Fourth is a 30-minute communication session specifically testing async skills, since the engineer will be working across a 3.5 to 4.5-hour timezone gap with their European team.
For senior roles, we add independent reference verification with previous managers identified from work history, not candidate-provided contacts.
The team at AnjuSmriti Global runs this process across all engagement types, whether remote contract roles or permanent placements through entity structures.
Client scenario, anonymised: a Swedish healthtech company, Series C, 120 employees, approached us needing five backend engineers and two data engineers in Bengaluru to build EU data residency infrastructure. They had already spent four months trying to hire through a generic job board and a local staffing firm that did not understand their stack, which was Go, PostgreSQL, and Kafka.
Their CFO was uncomfortable with not owning the employment relationship and wanted to set up an India entity immediately. We pushed back. At seven engineers, entity cost and compliance overhead would have consumed their first 18 months of operational attention. We recommended an EOR structure with IP assignment clauses built into each employment agreement.
What almost went wrong: one shortlisted candidate had a non-compete clause from a previous employer covering healthcare data platforms in APAC markets. We caught this during independent reference verification and replaced the candidate before the client ever saw the profile. Had we not caught it, they would have onboarded someone legally unable to work on their core product in India.
Outcome: all seven engineers were onboarded within 19 days of the mandate being signed. Eighteen months later, that team had grown to 14 engineers. They are now mid-way through Private Limited Company registration, exactly the trajectory we mapped at the start of the engagement.
Real Salary Numbers for Indian Engineers Hired by European Companies
All INR figures below are annual cost to company. EUR equivalents are approximate for comparison context.
Backend, Cloud, and Data Engineers based in Bengaluru or Hyderabad
Seniority Level | India Annual CTC (INR) | India Annual CTC (EUR approx) | European Equivalent Salary |
Mid-level (3 to 5 years) | INR 18 to 26 lakh | EUR 19,000 to EUR 27,000 | EUR 65,000 to EUR 80,000 |
Senior (6 to 9 years) | INR 30 to 45 lakh | EUR 31,000 to EUR 47,000 | EUR 90,000 to EUR 115,000 |
Lead or Architect (10 or more years) | INR 50 to 75 lakh | EUR 52,000 to EUR 78,000 | EUR 130,000 to EUR 160,000 |
Add-ons for EOR model per employee annually: EPF employer contribution is approximately 12 percent of basic salary, typically 40 to 50 percent of CTC. Gratuity provisioning adds approximately 4.8 percent of basic per year. EOR platform fees run USD 150 to USD 400 per month, or roughly INR 1.5 to 4 lakh per year.
Add-ons for entity model, annual overhead for a team of 10: Company secretary and compliance costs INR 3 to 6 lakh per year. Payroll processing and statutory filings add INR 2 to 4 lakh per year. Registered address or office costs INR 1.5 to 3 lakh per year. Entity setup is a one-time cost of INR 8 to 20 lakh.
European clients typically reinvest the salary differential, often EUR 40,000 to EUR 60,000 per engineer per year, into product development velocity, additional headcount, or R&D budgets that would not otherwise be fundable at European salary levels. That reinvestment is what makes India hiring a growth strategy, not purely a cost exercise.
Conclusion
The EOR-to-entity conversion curve is accelerating. European companies that began India hiring two to three years ago on EOR structures are now hitting the team size and permanence thresholds where entity setup makes financial sense. We are seeing this in active mandates right now, with several European clients mid-way through Private Limited Company registration after starting their India journey with an EOR arrangement we structured for them.
For companies still at the decision point, the answer on European companies hiring in India EOR vs entity is almost always the same: start EOR, build the team, prove the model, then convert. The compliance risk of getting this wrong in year one is far higher than the EOR fee overhead in year two.
If you are a European founder, CTO, or HR lead making this call, we can walk you through the numbers specific to your headcount, city preference, and timeline in a single working session.
Interesting Reads:
FAQs
1. Does the Payment of Gratuity Act 1972 apply to engineers hired through an EOR for a European company?
Yes, and this surprises most European clients. Any employee who completes five years of continuous service is entitled to gratuity equivalent to 15 days of last drawn salary for each completed year. When hired through an EOR, the EOR carries this obligation. Responsible EOR providers provision for this monthly. Before signing, confirm in writing how gratuity is provisioned and whether it is included in the quoted fee or billed separately at the five-year mark.
2. Which European markets are currently generating the most hiring demand for Indian engineers?
Germany, the Netherlands, Sweden, and Ireland are the four most active source markets. German mandates concentrate on cloud infrastructure, SAP modernisation, and data engineering driven by industrial sector digitisation. Dutch companies focus on fintech data and DevOps roles. Swedish mandates cover product engineering and backend development for B2B SaaS firms. Irish companies, many of which are European HQs for US technology groups, hire across cloud operations, cybersecurity, and QA automation. All four face structural domestic talent shortages at the senior level that India directly addresses.
3. Can a European company retain IP ownership when engineers are employed through an Indian EOR?
Yes, but only with explicit contractual language. Under Indian law, IP created in the course of employment generally belongs to the employer, which in an EOR arrangement is the EOR itself. A tripartite IP assignment agreement between the EOR, the engineer, and your European entity is required to transfer ownership. Any experienced EOR serving European product companies will have a template for this. Always review the IP clause before the first engineer is onboarded, not after.
4. What is the minimum team size that justifies setting up a Private Limited Company in India?
Based on client experience, the financial break-even point is approximately 12 to 15 engineers. Below that threshold, the one-time entity setup cost plus annual compliance overhead typically exceeds EOR fee savings. The more important variable is permanence. If there is any realistic chance of reducing the India team to zero within 24 months, avoid entity setup entirely. Winding down a Private Limited Company in India takes 6 to 18 months and involves regulatory filings with the Registrar of Companies, which is far more operationally demanding than exiting an EOR agreement.
5. How do German Works Council (Betriebsrat) obligations apply when a German company hires engineers in India?
Under the Betriebsverfassungsgesetz, companies with a Works Council must notify and in some cases obtain consent from the Betriebsrat for significant operational changes. Hiring additional headcount in India through an EOR does not automatically constitute outsourcing, particularly when Indian engineers work alongside the German team rather than replacing existing roles. However, if India hiring is explicitly tied to a headcount freeze or reduction in Germany, consultation becomes mandatory. We advise German clients to brief the Betriebsrat proactively before the India team reaches a size that could be interpreted as a structural change.
6. What notice periods should European companies expect for Indian engineers, and how does this affect project continuity?
Most mid-to-senior engineers in Bengaluru, Hyderabad, and Pune are on 60 to 90-day notice periods, significantly longer than the two to four weeks typical in Europe. This is actually an advantage: it gives longer planning windows when someone resigns. The complexity runs in the other direction. If you need to exit an engineer quickly, you are typically obligated to pay out the notice period in lieu, or negotiate a shorter exit individually. We include a clause in all placements requiring immediate notification when any engineer indicates exit intention, maximising lead time for backfill planning.
7. Are Indian engineers on EOR payroll eligible to receive stock options in the European parent company?
Yes, but the process requires careful structuring. Under FEMA and RBI regulations, Indian residents can receive ESOPs from a foreign parent. Grant, vesting, and exercise events each carry reporting and tax implications in India. At exercise, the spread between fair market value and exercise price is taxed as a perquisite under Salaries. We strongly recommend running any ESOP structure through a Chartered Accountant in India and an international tax advisor in the home country before the first grant is issued. Getting this right at the start avoids double taxation disputes later.
8. How long does converting an EOR-employed engineer to direct entity payroll take once the India entity is registered?
The conversion process takes 30 to 60 days and involves three parallel workstreams: issuing a new employment contract under the India entity and terminating the EOR agreement, transferring the engineer's Provident Fund UAN to the new employer's EPF code, and ensuring continuity of health insurance with no coverage gap. The PF transfer step is the most common source of delay, often taking two to three weeks through the EPFO portal. Start the conversion process 60 days before the intended effective date. The employee's continuity of service is legally preserved throughout, which is important to communicate clearly to maintain trust during the transition.
Comments