.png)
Why Japanese Companies Use Employer of Record (EOR) in India
Updated: Aug 16
Setting up a private limited company in India under the Companies Act, 2013 takes our Japanese clients 8 to 14 weeks once you account for DIN and DSC issuance, RBI reporting for FDI inflow, and opening a corporate bank account that a Tokyo finance team is comfortable wiring into. An Employer of Record gets the same company an engineer onboarded and compliant in 10 to 15 business days, with no entity on the ground. That gap is the main reason Japanese companies use Employer of Record (EOR) in India before they ever file incorporation paperwork.
What Is Driving Japan's Demand for Tech Talent in India Right Now?
Japan's domestic IT and embedded engineering pipeline has been shrinking for years, and it shows up directly in our mandates. Automotive Tier 1 and Tier 2 suppliers feeding Toyota, Honda, and Denso are building software defined vehicle capability while their graduate intake keeps falling. Trading houses are standing up AI and data teams to modernise supply chain systems. Mid sized fintech and SaaS firms are priced out of Tokyo engineering salaries, which have kept climbing as domestic competition for senior talent intensifies.
The current wave of hiring looks different from a few years ago. Clients are no longer asking only for backend engineers. Requests now regularly include AI integration engineers who can wire large language models into existing platforms, cloud cost optimisation specialists, and DevOps engineers who can run infrastructure as code across hybrid cloud setups. Agentic AI tooling has also changed how small teams operate, so a four person India pod today often ships what used to take six or seven engineers. This shift is a big part of why Japanese companies use Employer of Record (EOR) in India as their first move, since it lets them test a smaller, sharper team before committing to scale.
Pune and Chennai come up constantly in Japan facing mandates because of the existing Japanese industrial base there. Pune's Chakan Talegaon corridor and Chennai's Sriperumbudur belt already host Japanese auto component plants, so hiring managers from Aichi and Osaka prefectures are used to doing business in these cities.
Which Indian Cities Offer the Best Talent for Japanese Hiring Needs?
For embedded systems, automotive software, and hardware adjacent roles, Pune and Chennai have the deepest bench. Both cities have decades of industrial engineering education feeding local colleges, and engineers there already work against Japanese quality documentation standards because the OEM supplier ecosystem has trained them for years.
For general software engineering, AI, and cloud roles, Bengaluru and Hyderabad remain the strongest talent pools by volume, though competition for senior engineers is fiercest there.
Indian engineers bring strong fundamentals in Java, C++, Python, and increasingly Rust for automotive and embedded work, along with solid English documentation skills that matter when Japanese teams use English as the bridge language.
What they typically lack is sustained exposure to Japanese work culture, particularly nemawashi, the practice of pre aligning before a formal decision, and a lower tolerance for ambiguous requirements than US or European clients show. We run a dedicated cultural fit interview for every Japan bound candidate, separate from the technical round, and assess whether they acknowledge a client's concern first or jump straight to a technical defence.
What Indian Employment Laws Apply When Japanese Companies Use Employer of Record (EOR) in India?
This is the core reason Japanese companies use Employer of Record (EOR) in India rather than hiring directly. The legal employer of record, not the Japanese entity, carries the statutory obligations. The main one is the Employees' Provident Fund and Miscellaneous Provisions Act, 1952, which requires a 12 percent employer contribution on basic wages. The Payment of Gratuity Act, 1972 creates a gratuity liability for anyone who completes five years of continuous service.
State specific Shops and Establishments Acts govern working hours, leave, and termination notice, and these differ between Maharashtra, Tamil Nadu, Karnataka, and Telangana. India is also consolidating labour laws into four Labour Codes, which are changing how wages are defined for PF and gratuity calculations as they roll out state by state.
This is a good point to clarify contract hiring versus full time hiring, since Japanese finance teams often confuse the two. Contract hiring through an EOR means the engineer works exclusively on your project and can be scaled up or down with a defined notice period, while all statutory contributions are still made on their behalf. Full time hiring implies a longer term commitment, sometimes with a probation period, and suits a company confident about sustained workload. Both run through the same compliant EOR structure, so the real decision is about workload certainty, not legal risk.
The mistake we see most often is assuming that because an engineer is called a contractor, none of this applies. Indian authorities look at the substance of the relationship, not the label, and misclassified contractors expose the paying entity to retroactive claims. There is also a Japan specific point worth knowing.
Under the India Japan tax treaty, a company that issues daily task level instructions to India based staff, rather than agreeing on outcomes, risks creating a taxable presence in India. A properly structured EOR relationship keeps the EOR as the legal employer and the Japanese company as a service recipient, which is why this structure has become the standard way Japanese companies use Employer of Record (EOR) in India while they build local presence.
If your team is comparing EOR against setting up an entity right now, it helps to talk it through with someone who has done this for other Japanese clients. You can share your hiring plan here and we will map out the timeline for your specific roles.
EOR vs Entity vs Contractor: Which Hiring Model Fits Your Needs?
Factor | Employer of Record | Own Entity | Independent Contractor |
Time to first hire | 10 to 15 business days | 8 to 14 weeks | 5 to 7 business days |
Compliance owner | EOR entity | Your own India entity | Contractor self manages |
Tax exposure for Japan parent | Low, if structured correctly | Entity already creates taxable presence | High, misclassification risk |
Ideal headcount | 1 engineer and up | Typically 20 plus | 1, but not scalable |
Gratuity and PF | Carried by EOR, billed transparently | Carried by your own entity | Undefined, legal grey zone |
Best for | First 12 to 18 months in India | Established, growing team | Very short, narrow projects |
Most Japanese companies start in the EOR row and move to their own entity somewhere between 18 and 30 months in, once headcount and delivery confidence both justify the fixed cost of running one. We rarely recommend the contractor route beyond a single short engagement, given the misclassification exposure described above.
How Does the EOR Hiring Process Work, and What Have We Learned From Real Mandates?
Our standard timeline runs like this. Week one is role scoping and a cultural fit briefing with the client's Tokyo or Osaka based hiring lead. Weeks one and two run parallel sourcing and screening. Week three is client interviews, usually a technical round and the culture scenario round. Week four covers the offer, EOR onboarding, and background verification, with the engineer typically starting by week five or six.
A recent mandate shows both the value and the risk we manage for clients working with AnjuSmriti Global. A mid sized Japanese automotive electronics supplier needed a six person embedded software pod in Pune without waiting for board approval on a subsidiary. We placed the pod through EOR in nine weeks. Three weeks in, the client's Japan based engineering lead began issuing daily task instructions directly to the India engineers, bypassing the reporting structure we had set up, which risked the taxable presence issue described earlier.
We restructured the reporting line so instructions flowed through the India team lead, with priorities set from Japan rather than daily tasks. The client's own tax counsel later confirmed this kept them inside a clean service delivery arrangement. That pod has since grown to 14 engineers, and the client is now scoping their own entity registration in Pune.
What Does It Cost to Hire Engineers in India Through EOR?
Level | India CTC per year | Approx JPY equivalent | Comparable Tokyo salary |
Mid, 4 to 6 years | INR 14 to 18 lakh | JPY 25 to 32 lakh | JPY 60 to 75 lakh |
Senior, 7 to 10 years | INR 24 to 32 lakh | JPY 43 to 58 lakh | JPY 85 to 105 lakh |
Lead or Architect, 10 plus years | INR 42 to 55 lakh | JPY 75 to 99 lakh | JPY 120 to 155 lakh |
On top of CTC, budget the EOR service fee, typically 10 to 14 percent of CTC, plus employer PF contribution and gratuity provisioning, both already folded into the EOR's billed cost. Even after fees, an India based mid level engineer typically lands at 35 to 45 percent of the equivalent Tokyo hire's fully loaded cost.
This is also where the contract versus full time decision shows up in the numbers. Contract hires through EOR are billed monthly against actual engagement, which suits pilot teams and AI proof of concept work where scope can shift quickly. Full time EOR hires are budgeted as annual CTC with the same statutory protections, which suits teams building a stable, long running delivery function. Most Japanese clients don't pocket the savings from either model. They reinvest it into a larger pod, or into adding QA and DevOps capacity that domestic budgets would not have allowed.
Conclusion
Over the coming months, we expect the shift from pure cost arbitrage toward capability building to continue, particularly in software defined vehicles, battery management systems, and AI assisted manufacturing quality control, areas where Japan's domestic pipeline cannot supply engineers fast enough. In live mandates right now, more first time Japanese clients are skipping the "should we look at India" conversation entirely and coming to us already asking how Japanese companies use Employer of Record (EOR) in India to get a pilot team running inside a quarter.
If you are evaluating this path for your own team, talk to us about your hiring plan here and we will walk you through real numbers for your specific roles.
Interesting Reads:
FAQs
1.Does Japanese labour law apply to engineers hired in India through an EOR?
No. Once an Indian EOR is the legal employer, the engagement is governed by Indian statutes including the EPF Act, the Payment of Gratuity Act, and the applicable state Shops and Establishments Act. Japanese labour protections apply only to staff directly employed in Japan, not to India based engineers hired through a compliant EOR structure.
2.How does EOR help avoid creating a taxable presence in India?
Under the India Japan tax treaty, direct day to day control over India based staff can create a taxable presence for the Japanese company. An EOR keeps the EOR entity as the legal employer while the Japanese company receives services, with priorities set from Japan rather than daily task instructions, which keeps the arrangement inside a clean service delivery model.
3.Which Japanese industries are hiring most through EOR in India right now?
Automotive Tier 1 and Tier 2 suppliers building software defined vehicle and battery management capability lead current demand, concentrated in Pune and Chennai. Trading houses building AI and data teams for supply chain systems follow closely, typically hiring out of Bengaluru, with mid sized fintech and SaaS firms forming a smaller but fast growing segment.
4.What is the difference between contract hiring and full time hiring under EOR?
Contract hiring through EOR means the engineer works exclusively on your project with a defined notice period and full statutory compliance, suited to pilot teams and shifting scope. Full time hiring implies a longer term commitment, often with a probation period, and suits stable, long running delivery functions. Both run through the same compliant EOR employer.
5.Can an EOR hired team later be converted into direct employees of a Japanese company's own India entity?
Yes, and it is the most common path. Around 18 to 30 months into an EOR arrangement, once headcount and delivery confidence justify it, companies incorporate and transfer employment through a fresh offer that preserves continuity of service for gratuity purposes, since the EOR and the new entity are legally distinct employers.
6.Which Indian cities are best for Japanese automotive and embedded engineering hiring?
Pune and Chennai consistently outperform other cities for this talent profile, because both already host dense Japanese automotive supplier ecosystems. The local engineering colleges and mid career talent pool in these cities already have exposure to Japanese OEM quality documentation standards, which shortens ramp up time significantly.
7.How is payroll handled when a Japanese company hires through EOR in India?
The EOR runs India payroll in INR, handling PF, gratuity provisioning, TDS, and statutory filings directly with Indian authorities. The Japanese client is invoiced separately, usually in JPY or USD, covering salary, EOR service fee, and statutory contributions as one consolidated monthly bill, removing the need to run a parallel INR payroll process from Japan.
8.Is there a minimum team size needed before EOR makes sense for a Japanese company?
No. Single engineer pilots are common through EOR. Entity setup only becomes financially sensible once fixed compliance and administrative overhead can be spread across enough headcount to beat the EOR's per employee fee, which in most cases sits around 20 to 25 engineers, though it varies by how fast the client wants to scale.
Comments