.png)
Why Global Scaleups Use Employer of Record (EOR) for India Hiring
Updated: Aug 10
A scaleup hiring its first five engineers in India through an Employer of Record can have them on payroll within 10 to 15 business days. The same company setting up its own entity needs registration approval, a PAN and TAN, GST registration, and a Provident Fund establishment code before a single offer letter can legally go out, a process that usually takes six to ten weeks.
This is exactly why global scaleups use Employer of Record (EOR) for India hiring: it closes the gap between deciding to build an India team and actually having engineers shipping code. We have run EOR hiring for scaleups growing from 20 people to over 100, and the founders who delay asking "should we own an entity yet" almost always regret the compliance exposure, not the EOR fee.
Why India Entity Setup Is Too Slow for Scaleup Hiring Speed
Scaleups don't hire one or two people at a time. They hire in sprints of eight to fifteen, usually against a board approved runway extension or a product deadline tied to AI or platform investment. India has become the default answer to "where do we build this team," and Bengaluru, Hyderabad, and Pune now host more Global Capability Centers (GCC) than at any point before, with combined GCC headcount well past one and a half million and still rising as scaleups follow the same playbook enterprises used years earlier.
Right now, that demand is being driven heavily by AI infrastructure, cloud platform work, and DevOps automation. Scaleups building agentic tools, internal copilots, or AI powered products need engineers who understand both application code and the underlying cloud and data platform, and they need them fast. India's entity formation process was never designed for that speed. Before a company can legally pay a single employee, it typically needs incorporation approval, tax registrations, and a Provident Fund establishment code, each with its own processing window.
Where Scaleups Find the Best India Tech Talent for EOR Hiring
Three cities carry most of scaleup hiring, and each has a different strength.
Bengaluru has the deepest bench for product engineering, cloud infrastructure, and AI or machine learning roles, largely because engineers there have already worked inside fast moving product companies rather than services delivery teams. Hyderabad produces strong backend and data engineering talent, shaped by the large enterprise GCCs based there, though engineers coming from that environment sometimes need calibration on startup speed decision making.
Pune consistently delivers strong QA automation, DevOps, and mid level full stack engineers at a lower salary band, which is why we route a good share of full stack hiring there when budget per head matters more.
This is also where the choice between contract hiring and full time hiring usually comes up for the first time. Contract hiring works well for a short, clearly scoped piece of work, a specific migration project, a proof of concept, or a role you genuinely expect to end within a few months. Full time hiring, whether through EOR or your own entity, is the right call for anyone who will own a piece of the product long term, sit in daily standups, and be part of the core team's decision making.
Treating a full time role as a contract to save on statutory contributions is the single biggest mistake we see scaleups make, and it usually surfaces at the worst possible time, during due diligence for their next funding round.
What Indian Employment Law Means for Global Scaleups Using Employer of Record (EOR) in India Hiring
Every India employment relationship, EOR or otherwise, sits under a specific set of laws, and scaleup founders get this wrong more than any other client segment. The core statute is the state specific Shops and Establishments Act, which governs working hours, leave, and termination notice. Sitting alongside it is the Code on Wages, 2019, plus the Employees' Provident Fund and Miscellaneous Provisions Act, 1952, which requires a 12 percent employer contribution matched by 12 percent from the employee. Employees below a set wage ceiling also fall under the Employees' State Insurance Act, 1948, adding a further 3.25 percent employer contribution, and anyone who completes five years gets gratuity under the Payment of Gratuity Act, 1972.
None of this applies to a genuine contractor. That is exactly why some founders try to label full time, exclusively dedicated India engineers as contractors to avoid the stack entirely. Indian labour authorities look at how the role actually functions, not the label on the invoice. An engineer working fixed hours, using company tools, and working solely for one client for a year is an employee in substance.
At AnjuSmriti Global, this is the single most common compliance issue we catch before it becomes the client's problem, because an EOR is the legal employer of record from day one and every statutory contribution is already built into the payslip.
EOR vs Contract Hiring vs Full Time Entity Hiring: Which Fits Your Scaleup
This is the comparison our clients screenshot most often when mapping out their India hiring plan.
Factor | Contract Hiring | EOR (Full Time) | Own Entity |
Time to first hire | 3 to 5 days | 10 to 15 business days | 6 to 10 weeks |
Upfront cost | Near zero | Near zero | $15,000 to $25,000 plus |
Statutory benefits (PF, ESI, gratuity) | Not applicable if genuinely short term | Fully handled by the EOR | Your responsibility, in house or outsourced |
IP and confidentiality protection | Depends entirely on contract quality | Strong, built into the employment contract | Strong |
Best fit | One to three specialist roles, bounded scope | 5 to 40 employees | 40 plus employees, or a permanent India plan |
The rule we give founders is simple. Use contract hiring for anything short term and clearly scoped, use EOR from your first full time hire up through roughly 40 people, and start evaluating your own entity once you are consistently above that and India has become permanent rather than an experiment.
How Scaleups Hire Through EOR in 15 Days: Process and Proof Point
Our process runs in three stages. Role scoping and a technical rubric take two to three days, active search plus a first round technical screen take five to seven days, and client interviews plus offer and EOR onboarding take another three to five days, ten to fifteen business days end to end for a standard engineering role.
One recent mandate shows why the compliance layer matters as much as sourcing. A Series C fintech scaleup needed to stand up an eight person backend team in Hyderabad within six weeks to hit a regulatory deadline. We placed all eight through EOR inside the timeline.
What almost went wrong was that two candidates the client wanted had been working as "consultants" for their previous employer for over 18 months on what was, in substance, a full time exclusive engagement, meaning the same misclassification risk would have followed them. We flagged it before offers went out and moved both onto standard employment contracts instead. The team was fully staffed a week ahead of the deadline, with no compliance exposure carried forward.
What Does EOR Hiring in India Actually Cost a Scaleup
Real salary numbers for a backend or full stack engineering role hired through EOR in Bengaluru or Hyderabad. Mid level, three to five years, typically runs 18 to 28 lakh rupees a year. Senior, six to nine years, runs 32 to 48 lakh. Engineering lead or staff level, ten plus years, runs 55 to 85 lakh.
On top of gross salary, total cost under EOR adds employer PF at 12 percent of basic, employer ESI at 3.25 percent where applicable, gratuity provisioning around 4.8 percent, and the EOR provider's monthly fee, usually $300 to $550 per employee. All in, total cost of employment typically lands 18 to 24 percent above gross salary, well below what most scaleups assume, and without the upfront entity cost or ongoing in house compliance headcount. Most clients reinvest that saved cost directly into hiring faster, one or two extra senior engineers in month two instead of month five.
Conclusion
Over the next year, expect more global scaleups to skip the "own entity or nothing" debate entirely and default to EOR as the standard first move into India, the same shift that already happened at the enterprise GCC level. In live mandates right now, scaleups that would once have spent their first India quarter on incorporation paperwork are instead using that quarter to hire, ship, and prove the India team's value before committing to permanent infrastructure. This is the practical reason global scaleups use Employer of Record (EOR) for India hiring: it lets the hiring decision run on the company's own growth timeline instead of India's registration timeline.
If your team is weighing this decision, we are happy to map out what your specific headcount plan and timeline would look like under EOR versus a direct entity.
Interesting Reads:
FAQs
1.Does India's Provident Fund law apply to EOR employees hired for a scaleup's India team?
Yes. Any employee hired through EOR in India is a full employee of the EOR under the Employees' Provident Fund and Miscellaneous Provisions Act, 1952, entitled to the standard 12 percent employer contribution matched by 12 percent from the employee. This removes the risk of discovering later that a "contractor" should have received PF contributions all along, since it is deducted and deposited automatically every month.
2.Can a scaleup own the intellectual property an EOR employed engineer creates in India?
Yes, as long as the EOR agreement includes a proper IP assignment clause, which any credible EOR provider builds into the underlying employment contract. The engineer is legally employed by the EOR, but confidentiality and invention assignment clauses transfer all work product to the client company, the same way it would under direct employment. Weak IP language is one of the more common gaps to check for.
3.How many India employees can a scaleup have under EOR before needing its own entity?
There is no legal limit. We have run EOR structures for scaleup clients with over 60 India employees. The move to an entity is an economic decision, not a regulatory one, and usually makes sense once headcount sits somewhere between 40 and 60, depending on role seniority, because that is where the EOR fee starts to exceed the cost of running compliance in house.
4.What happens to EOR employed engineers if a scaleup later opens its own India entity?
This is called a Transfer of Undertaking, a standard exit process where employees are re contracted directly under the new entity with tenure, benefits, and gratuity entitlements preserved. It typically takes four to six weeks and is best planned before the entity incorporation is complete, so there is no gap in payroll or benefits for anyone involved.
5.Do Indian engineers hired through EOR get the same equity treatment as US based scaleup employees?
Legally, yes. EOR does not restrict a scaleup's ability to grant equity, since it is usually issued directly by the parent company on its own cap table, separate from the local employment contract. What needs care is the tax side, since India taxes ESOPs at exercise and again at sale, and employees need to understand the foreign exchange reporting rules that apply when holding shares in a foreign company.
6.How does notice period and offboarding work for EOR employees in India compared to the US?
India's notice periods run longer than typical US at will norms, governed by the applicable state Shops and Establishments Act and the individual contract, usually 30 to 90 days depending on seniority. Under EOR, offboarding follows the same statutory process a direct entity would follow, including full and final settlement and any gratuity due, managed by the EOR on the client's behalf.
7.Is scaling an India team up and down easier through EOR compared to owning an entity?
Yes. Scaling up under EOR means adding headcount on the same 10 to 15 day cycle regardless of existing team size, and scaling down means following standard notice period offboarding without the HR and legal overhead of running a reduction through your own registered establishment. For a scaleup whose headcount plan follows funding milestones rather than a fixed annual budget, that flexibility often matters as much as the cost.
8.What is the biggest compliance mistake scaleups make when hiring in India without EOR or an entity?
Paying full time, India based engineers as offshore contractors through a standard international agreement, usually because it is fast and mirrors how the company already pays contractors elsewhere. Indian labour authorities assess the actual working relationship, not the contract label, and a full time, exclusive, company directed engineer is very likely to be reclassified as a statutory employee if audited, with retroactive liability attached.
Comments