.png)
How to Hire Across Multiple Indian Cities with Employer of Record (EOR)
- Saransh Garg
- Mar 28
- 12 min read
Updated: 5 days ago
A company that hires five engineers in Bengaluru, three in Hyderabad, and two in Pune through an EOR is technically operating under three separate state Shops and Establishments Acts, three different Professional Tax slabs, and one central EPFO registration that has to reconcile all of it every month. We have run payroll for clients doing exactly this, building 15 to 40 person distributed teams across Indian cities without opening a single entity, and the first thing we tell every HR Manager is that hiring in one Indian city and choosing to hire across multiple Indian cities with Employer of Record (EOR) are not the same project. The compliance stack changes city by city, and the way you structure the arrangement has to account for that from day one, not after the third city gets added.
Why Do Companies End Up Hiring Across Bengaluru, Hyderabad, Chennai, Pune, and Delhi NCR at the Same Time?
Most multi-city hiring in India is not planned that way from the start. A company sets up an initial pod of six engineers in Bengaluru because that is where the first two hires already lived, then discovers three months later that Bengaluru compensation for the specific skill set it needs, say platform engineering or SRE, has moved 18 to 22% ahead of Hyderabad and Pune for comparable experience. At that point the HR team is told to open the next five roles in a second city to protect the budget, and now payroll, leave policy, and statutory compliance have to run in parallel across two states.
This pattern shows up most with GCC builds and mid-size SaaS companies scaling engineering headcount past 20 to 25 people. Bengaluru remains the deepest talent pool for cloud-native and AI/ML roles, but salary inflation for senior and lead-level engineers there has pushed steadily upward. Hyderabad has become the default second city for companies wanting Bengaluru-adjacent skill depth, particularly in data engineering and SAP, at a meaningfully lower cost base.
Chennai and Pune tend to enter the mix when companies need QA, embedded systems, or full-stack capacity without competing for the same Bengaluru talent pool. Delhi NCR gets added when a company needs proximity to enterprise sales or when the mandate includes SAP and ERP consultants, where NCR has a strong bench.
The mistake we see most often when a company decides to hire across multiple Indian cities with Employer of Record (EOR): picking the second and third cities based on cost alone, without checking whether the specific skill actually clusters there. One fintech client opened a Chennai pod expecting to find senior Kafka and event-streaming engineers at Bengaluru-adjacent depth. The talent existed, but at roughly a third of the volume, which stretched a six-week search to eleven weeks. Multi-city planning has to start with a talent-density map for the specific role, not a cost spreadsheet.
Which Indian Cities Actually Have the Talent, Mapped by Role Instead of Assumption?
Indian cities are not interchangeable for engineering talent, and treating them that way is the single most common planning error we correct for clients who hire across multiple Indian cities with Employer of Record (EOR) for the first time.
Bengaluru still carries the deepest bench for cloud infrastructure, DevOps, AI/ML, and product engineering roles above the senior level. This is where the largest concentration of engineers with 8+ years on AWS, GCP, and Kubernetes at scale actually sit, largely because of the density of global product companies headquartered there. Hyderabad has built comparable depth in data engineering, SAP, and increasingly in AI/ML through GCC buildouts from global banks and healthcare firms. Its talent pool skews slightly younger on average than Bengaluru's, which is useful for mid-level hiring but means lead-level candidates take longer to source.
Pune has strong manufacturing-adjacent and embedded-systems talent alongside a growing full-stack and QA automation base, driven by its auto and fintech GCC presence. Chennai's strength is in QA, testing, and enterprise Java, with a smaller but real pocket of fintech engineering talent. Delhi NCR carries the deepest SAP, ERP, and enterprise sales-engineering bench of any Indian city, plus a large pool of developers experienced in working directly with international clients.
What Indian engineers across all five cities consistently bring: strong fundamentals in distributed systems, comfort working with US and European client codebases, and, because so much of Indian IT services work is already client-facing, genuine experience adapting to a foreign company's engineering culture rather than needing it explained from scratch.
What they typically lack, and what we screen for specifically in multi-city mandates, is exposure to a single product's long-term technical debt. Engineers coming from services backgrounds are often excellent at greenfield builds and fast delivery, but weaker on the judgment calls that come from owning one codebase for three-plus years. A structured legacy-code walkthrough exercise during the technical interview surfaces this gap before a client discovers it six months into the engagement.
Contract Hiring vs Full-Time Hiring When You Hire Across Multiple Indian Cities
One decision that shapes almost everything downstream, from onboarding speed to statutory cost, is whether a role is engaged as a contractor or brought on as a full-time employee. Both routes are available under an EOR model, and the right choice usually depends on how certain you are about the role's duration and how much control you need over day-to-day work.
Full-time hiring through an EOR means the provider becomes the legal employer of record in that specific state, issuing an employment contract, running payroll, and handling EPF, gratuity accrual, and, where applicable, ESI on your behalf. This route makes sense for core engineering, product, and long-term operational roles where you want continuity, internal reporting lines, and the retention benefits that come with statutory entitlements like gratuity. It also gives the employee the full protection of the relevant state's Shops and Establishments Act, which matters for notice periods and leave.
Contract hiring, engaged under the Contract Labour (Regulation and Abolition) Act, 1970 where applicable, works better for defined-scope work such as a six-month migration project, a short-term QA sprint, or specialist consulting where you do not want a permanent headcount commitment. Contractors engaged through an EOR are still entitled to EPF and, where wage thresholds apply, ESI coverage, since these protections attach to employment and wage level rather than to contract status.
What differs is flexibility on both sides: contract engagements are easier to scale down without triggering the same notice-period obligations as a full-time termination, but they also do not build the same long-term retention incentive that gratuity and a permanent role provide.
Most clients who hire across multiple Indian cities with Employer of Record (EOR) use a blended approach: full-time hires for the core pod in each city, with contract capacity layered on top for project surges, specialist skills that are hard to justify as permanent headcount, or roles being trialed before conversion to full-time.
Employer of Record (EOR) Compliance Across Indian States: What Nobody Explains Upfront
There is no single India employment law, and this is the part that trips up almost every company hiring across more than one Indian city for the first time. Each state administers its own Shops and Establishments Act, and these govern working hours, leave entitlement, holiday calendars, and termination notice periods differently. The Karnataka Shops and Commercial Establishments Act governs Bengaluru, the Telangana Shops and Establishments Act governs Hyderabad, the Delhi Shops and Establishments Act governs NCR hires, the Tamil Nadu Shops and Establishments Act governs Chennai, and the Maharashtra Shops and Establishments Act governs Pune and Mumbai.
On top of that, every employee is covered centrally by the Employees' Provident Fund and Miscellaneous Provisions Act, 1952 (EPFO) and, for those below the wage threshold, the Employees' State Insurance Act, 1948. The Payment of Gratuity Act, 1972 and the Payment of Bonus Act, 1965 apply nationally but interact with state-specific rules on notice periods and final settlement timelines.
Under an EOR structure, the provider holds the statutory employer relationship in each relevant state, which means it needs active registrations, Professional Tax, Shops and Establishments, EPFO sub-code, in every city you hire in, not just one central registration that covers the whole country.
The mistake corrected most often: assuming that because an EOR provider is compliant in Bengaluru, the same provider is automatically compliant to hire in Chennai or Pune the next month. It is not automatic. It requires the EOR to hold or obtain registrations in that specific state, and gaps here are where PF remittance delays and Professional Tax filing errors happen.
Before adding a second or third city, ask directly which state registrations the provider currently holds active, not which cities they say they can operate in. AnjuSmriti Global maintains standing registrations across the major hiring states clients ask for most, which is what allows a second-city rollout to start without a multi-week registration delay.
Multi-City EOR Compliance Checklist
Check this against your EOR provider before adding a new city.
Requirement | Applies When | What to Verify With Your EOR Provider |
State Shops & Establishments registration | Every new city added | Active registration in that specific state, not just general India coverage |
EPFO sub-code for the new location | Every new city added | Sub-code issued and linked to the central EPFO establishment code |
Professional Tax registration | Karnataka, Maharashtra, Telangana, West Bengal, Tamil Nadu (Delhi has none) | Confirm the state's specific slab and filing cadence |
ESI applicability | Any employee under ₹21,000/month gross | Confirm registration if any hire falls under this threshold |
Leave policy localization | Every new city added | State-specific public holiday calendar and casual/sick leave minimums |
Gratuity provisioning | Any employee likely to cross 4 years 240 days | Confirm the EOR accrues gratuity liability per employee, not just at exit |
Termination notice period | Every new city added | State S&E Act notice requirements differ; confirm before issuing any termination |
Payroll cut-off alignment | Multiple cities running simultaneously | Confirm one consolidated payroll date, not city-by-city drift |
The most common gap found when auditing a client's existing multi-city EOR setup is ESI applicability. Companies hiring mixed-seniority teams sometimes bring on a junior QA or support hire below the ₹21,000 monthly gross threshold and do not realize ESI registration becomes mandatory for that individual, a separate compliance track from EPF alone.
Our Process for Multi-City India Rollouts, and What Almost Went Wrong Once
The standard timeline for a first-city EOR hire runs 3 to 4 weeks from signed mandate to onboarded employee, with sourcing, technical vetting, offer, and EOR onboarding running in parallel rather than sequentially. When a client adds a second or third city to an existing mandate, that clock does not restart. City-specific sourcing runs in parallel while the EOR compliance team pre-registers the new state before the first offer goes out, which typically compresses the second-city timeline to 2 to 3 weeks.
Technical assessment stays consistent across cities so a Bengaluru hire and a Pune hire are held to the same bar, using the same structured interview panel and the same take-home or live-coding exercise regardless of location, adjusted only for the specific role's stack.
Here is a scenario that shows why compliance sequencing matters.
A mid-size US healthcare-technology client, roughly 200 employees globally, had built an 8-person Bengaluru engineering pod over 14 months and asked for a second pod in Hyderabad to add data engineering capacity, targeting 6 hires in 90 days. All 6 candidates were sourced and technically cleared on schedule.
What almost went wrong: the EOR provider's Telangana Shops and Establishments registration had lapsed for renewal three weeks before it was needed, caught only because the compliance lead runs a registration-status check before any offer letter goes out in a new state, a step added specifically after an earlier client ran into this exact issue. Offers were held for eight days while the registration renewed rather than issuing offer letters against an inactive registration, which would have created a compliance gap on day one of employment.
All 6 Hyderabad hires started within the original 90-day window, and the client's only visible impact was a slightly compressed final onboarding week rather than a compliance incident discovered months later.
What Does It Actually Cost to Hire Across Multiple Indian Cities with Employer of Record (EOR)?
Real numbers, three seniority levels, across the two most common city pairings clients run: Bengaluru plus Hyderabad.
For a mid-level engineer (4 to 6 years), Bengaluru CTC typically runs ₹18-24 LPA against ₹14-18 LPA in Hyderabad for a comparable profile. Senior engineers (7 to 10 years) run ₹28-38 LPA in Bengaluru against ₹22-30 LPA in Hyderabad. Lead-level or architect profiles (10+ years) run ₹42-60 LPA in Bengaluru against ₹35-48 LPA in Hyderabad, though at this level the gap narrows because lead-level talent in Hyderabad is scarcer and commands closer-to-Bengaluru pay to retain.
On top of gross CTC, employer-side statutory costs add roughly 12 to 14%: EPF employer contribution at 12% of basic (subject to the wage ceiling structure), gratuity accrual at approximately 4.81% of basic, and, where applicable, ESI employer contribution at 3.25% of gross for employees under the threshold. EOR provider fees typically run 8 to 12% of CTC per employee for volume mandates above 10 hires, scaling down slightly as headcount grows within a city. Recruitment fees are usually separate, structured as a percentage of first-year CTC or a flat per-hire rate for bulk hiring mandates.
Clients who run this math properly typically find the total cost of a senior India-based engineer, fully loaded, still lands at 55 to 65% of an equivalent US or Western European hire even after EOR and statutory costs are added. The savings companies reinvest most often go toward faster hiring velocity itself: adding a third city sooner, or upgrading the seniority mix of the team rather than just banking the margin.
Conclusion
Over the next 12 to 18 months, the multi-city pattern is expected to accelerate specifically toward three-city and four-city GCC builds rather than the traditional single-hub model, driven by companies wanting to de-risk talent concentration in Bengaluru while still keeping access to its senior-level bench. In live mandates right now, more clients are opening Hyderabad and Pune simultaneously as second and third cities rather than sequentially, which puts more pressure on EOR providers to have multi-state registrations ready before the mandate starts rather than reacting city by city.
If your growth plan involves choosing to hire across multiple Indian cities with Employer of Record (EOR) as the structure, the single highest-leverage thing you can do before signing anything is get your EOR provider's current state-by-state registration list in writing.
Ready to scope a multi-city India build? Start here.
Interesting Reads:
FAQs
1.Does the same EOR agreement automatically cover hiring in a new Indian city, or do we need a new setup each time?
The master EOR agreement typically does not need to be re-signed, but the compliance infrastructure behind it does need to extend. The provider must hold or obtain active Shops and Establishments registration, an EPFO sub-code, and Professional Tax registration where applicable in the new state before anyone can legally be onboarded there. Some providers register reactively per mandate, adding 1 to 3 weeks to a second-city timeline, so always ask for the current active-registration list by state first.
2.If we hire in both Bengaluru and Delhi NCR, do our employees get different leave entitlements?
Yes. Leave entitlement, public holidays, and casual or sick leave minimums are set at the state level under each city's Shops and Establishments Act, so a Bengaluru employee's statutory minimum will differ from a Delhi NCR employee's under the same employer. Most companies offer a unified policy above the statutory minimum for consistency, but the underlying statutory floor still varies, and the EOR provider needs to track both correctly.
3.How do we handle Professional Tax when we have employees across Karnataka, Telangana, Maharashtra, and Delhi at the same time?
Professional Tax is a state-level tax with different slabs, and Delhi does not levy it at all, while Karnataka, Telangana, and Maharashtra do, each with its own monthly slab structure. Under an EOR model, the provider deducts and remits it per employee based on their work state, so a payroll report will show it applied inconsistently across the team. That is expected. Confirm the provider's system applies the correct state slab automatically rather than one flat rate.
4.Which Indian city should we open second if our first pod is already in Bengaluru and we are hiring data engineers?
Hyderabad is usually the strongest second-city choice given the density of GCC data teams already established there from global banking and healthcare clients, which has built a genuinely deep bench. Pune is a reasonable alternative if embedded or full-stack capacity is also needed in the same pod. Chennai is worth caution as a first data-engineering expansion city specifically, since the talent exists but at lower volume, which tends to stretch sourcing timelines beyond 2 to 3 hires.
5.Do contract employees under an EOR get the same statutory benefits as permanent employees across different cities?
Contract employees engaged through an EOR are still entitled to EPF and, where applicable, ESI coverage regardless of contract status, since these are tied to employment and wage thresholds rather than employment type. Gratuity eligibility depends on continuous service crossing four years and 240 days, applying the same way to contract staff as to direct employees. What differs by city is the notice period and termination process under the relevant state's Shops and Establishments Act.
6.How does ESI applicability work when some of our team earns above and some below the threshold across different cities?
ESI coverage is determined by individual gross monthly wage, not by city or company policy. Any employee earning up to ₹21,000 per month gross falls under mandatory ESI coverage regardless of which Indian city they work in. In a mixed-seniority multi-city team, this typically affects junior support, QA, or operations hires rather than mid-to-senior engineers, but it needs individual tracking, since a raise that crosses the threshold changes an employee's status mid-year.
7.What happens to statutory compliance if we later want to consolidate our multi-city EOR hires under one entity?
If you eventually set up your own India entity, each city's employees would need to transition from the EOR's statutory registrations to your own, including re-registering EPF, ESI where applicable, and state Shops and Establishments compliance under your entity's name in each relevant state. This is more involved across multiple cities than from a single city, since you are managing parallel registration transfers. Most clients plan this only after a team crosses 40 to 50 people.
8.Is a single consolidated payroll run possible across employees in four different Indian cities under one EOR?
Yes, and this is one of the operational advantages of using a single EOR provider across cities rather than separate local vendors per city. You get one consolidated payroll cut-off date and one combined payroll report, even though the underlying statutory filings for Professional Tax, EPF, and ESI are still submitted separately per state behind the scenes. Confirm this specifically before signing, since not every provider handles multi-city consolidation cleanly.
Comments