US-Headquartered. Operating Across India.
Choose the city based on role mix, talent depth, client access, operating risk and cost, not a generic best-city ranking. Every city below says what it is genuinely strong for and what it is a poor fit for.
Headquartered in New York, United States, with India operations in Pune, Noida, Hyderabad, Mumbai, Vadodara and Bengaluru, also written Bangalore.
A US company since 1971, operating in India since 1995and building India operations for clients since 2005.
Six Cities, Side by Side
The five dimensions that actually decide a location: what the city is strongest for, whether it can absorb scale hiring, relative cost, how easily a US team can get there, and the main operating risk you would be taking on.
| Strongest for | Scale hiring | Relative cost | US travel access | Main operating risk | |
|---|---|---|---|---|---|
| Pune | Engineering, QA, pharmacovigilance | Good | Moderate | Via Mumbai, three hours by road | Engineering competition from established captives |
| Noida | Analytics, finance operations, scale back office | Best of the six | Moderate | Delhi, direct US flights | Commute variability across the NCR |
| Hyderabad | Life sciences, revenue cycle, product engineering | Good | Moderate | Hyderabad, one stop from most US cities | Large employers competing for senior product talent |
| Mumbai | Banking, insurance, client-facing roles | Moderate | Highest | Best direct access from the US | Cost base, and real-estate constraints on expansion |
| Vadodara | Manufacturing operations, process work, back office | Moderate | Lowest | Via Ahmedabad, two hours by road | Thin senior technology layer |
| Bengaluru (Bangalore) | Software engineering, AI and ML, product | Good | High | Bengaluru, direct US flights | Highest technology attrition of the six |
Relative cost is relative to each other, not to a US baseline. The cost difference between the cheapest and most expensive of these six is smaller than the cost of putting a function in a city that cannot hire its senior layer.
What Each City Is Actually Good For
Three role families per city with the reason each has depth there, plus what the city is not the right answer for. The second part is the part worth reading.
Pune
- Office type
- Leased office floor, Reliable-managed
- Area
- Western Pune IT corridor
- Operating hours
- Operating window covers a US morning overlap of roughly four hours on the East Coast
- Travel access
- Nearest major airport is Mumbai, roughly a three-hour drive, or Pune for domestic connections.
Real depth here, and why
- Software and platform engineering. Deep senior engineering layer built by two decades of captive centers in the city, so the people who have run a team before are actually available rather than theoretically present.
- QA and test automation. One of the strongest test-automation markets in India, and the discipline is treated as a career track here rather than a stepping stone, which shows up in retention.
- Pharmacovigilance and regulatory. Established life-sciences services presence in the city means candidates arrive already familiar with safety database work and regulatory timelines.
Less suited for
Not the first choice for high-volume voice operations, where the cost base and the competitive set both work against you.
Noida(Delhi NCR)
- Office type
- Leased office floor, Reliable-managed
- Area
- Noida, within the Delhi National Capital Region
- Operating hours
- Operating window covers a US morning overlap of roughly four hours on the East Coast, with a second shift available
- Travel access
- Delhi airport, typically 45 to 90 minutes depending on the time of day.
Real depth here, and why
- Data science and analytics. The NCR analytics market is genuinely deep at the senior end, which is the layer that constrains most analytics builds.
- Finance and accounting operations. Large existing shared-services base in the region, so candidates have worked in a controls environment before and do not need it explained.
- High-volume back office. The largest available talent pool of the six for scale hiring, which matters when a function needs forty people rather than eight.
Less suited for
Commute patterns across the NCR are the most variable of our six cities, which affects shift design more than it affects hiring.
Hyderabad
- Office type
- Leased office floor, Reliable-managed
- Area
- HITEC City area
- Operating hours
- Operating window covers a US morning overlap of roughly four hours on the East Coast
- Travel access
- Hyderabad airport, roughly 45 minutes from the office area.
Real depth here, and why
- Life sciences and clinical operations. The densest pharma and clinical-research employer base of our six cities, which means clinical data management and regulatory affairs candidates exist at senior levels rather than only at entry.
- Healthcare revenue cycle. A large established RCM employer base, so coding and denial-management experience is available with payer-specific familiarity already in place.
- Product engineering. Strong and growing product-company presence, useful when the work is building rather than maintaining.
Less suited for
The competitive set for senior product engineers includes several very large employers, so offers need to be positioned deliberately.
Mumbai
- Office type
- Leased office, Reliable-managed
- Area
- Central Mumbai business district
- Operating hours
- Operating window covers a US morning overlap of roughly four hours on the East Coast
- Travel access
- Mumbai international airport, and the easiest direct-flight access from the US of any of our cities.
Real depth here, and why
- Banking and capital markets operations. India’s financial centre, so trade reconciliation, KYC, AML and fund-operations experience comes with genuine domain familiarity rather than trained-from-scratch.
- Insurance operations. Concentrated insurance employer base, which means underwriting-support and claims candidates have seen the actual work.
- Client-facing and executive roles. The easiest of the six for a US executive to reach directly, which matters more than it sounds for the roles that carry relationships.
Less suited for
Highest cost base of the six. For volume back-office work the economics are better elsewhere, and we will say so.
Vadodara
- Office type
- Reliable-operated office
- Area
- Vadodara, Gujarat
- Operating hours
- Operating window covers a US morning overlap of roughly four hours on the East Coast
- Travel access
- Ahmedabad airport, roughly two hours, or Vadodara for domestic connections.
Real depth here, and why
- Manufacturing and engineering operations. Long-standing industrial base in the region, so engineering-operations and quality candidates come from an environment where process discipline is normal.
- Business process operations. Lower attrition than the metro markets, which is the single biggest lever on total cost for a process function over three years.
- Finance and back office. Solid mid-level accounting availability at a materially lower cost base than Mumbai or the NCR.
Less suited for
Thinner senior technology layer than the metros. For a function that needs a senior architect on site, another city is usually the better answer.
Bengaluru(Bangalore)
- Office type
- Leased office, Reliable-managed
- Area
- Outer Ring Road technology corridor
- Operating hours
- Operating window covers a US morning overlap of roughly four hours on the East Coast
- Travel access
- Bengaluru airport, 60 to 90 minutes from the technology corridor.
Real depth here, and why
- Software engineering and AI or ML. The deepest senior engineering market in India, and effectively the only one of our six where a specialised machine-learning hire is a normal search rather than a project.
- Platform and infrastructure. Large pool of engineers who have operated production infrastructure at scale, which is not the same skill as building it.
- Product management. The strongest product-management market of the six, useful when the offshore team owns outcomes rather than tickets.
Less suited for
The most competitive hiring market and the highest technology attrition of the six. Bengaluru, also written Bangalore, is the right answer when you need depth and the wrong one when you need stability at a modest cost.
Current capacity per city is confirmed during scoping rather than published, because a seat number is only meaningful alongside the shift pattern and the role mix it is supporting. Each of these offices can absorb an initial team and expand within the same building.
Four Questions, in This Order
Cost is the input operators lead with and the one that matters least to whether the build works. These are the four that decide it.
Can this city hire your senior layer?
Not the size of the talent pool, the depth of it at the seniority you need. A city with a large entry-level pool and a thin layer of people who have run the function before is a city where you fill the team and struggle to lead it. The senior layer is the constraint in almost every build.
Who else is hiring that profile here?
Competing with global captives is a different problem from competing with domestic services firms. It changes the offer, the pitch and the retention plan, and it is knowable before you commit.
How much live overlap does the work need?
All six cities give roughly four hours of US East Coast morning overlap on a standard shift. If the function needs more, that is a shift-design decision with a real cost and a real retention consequence, and it is easier to design for at the start.
What operating risk are you accepting?
Attrition in that role family, commute patterns, infrastructure reliability, and how concentrated your exposure becomes with the whole function in one location. Then decide whether that concentration is acceptable for this particular function.
When a Second City Is Worth the Overhead
A multi-city posture costs more to run. Whether that is worth paying depends on what the function does, not on a general preference for resilience.
A second city earns its cost when
- The function has a hard service level that a single-site outage would breach.
- A regulator or a client contract requires demonstrated continuity, in which case this is a requirement rather than a judgment.
- The role mix genuinely splits, for example senior engineering in Bengaluru and volume processing in Noida. Two cities for two different reasons is easier to run than two cities doing the same thing.
- You are past roughly 80 people and single-site attrition risk is concentrated.
It does not, when
- The team is under about 30 people. Splitting it produces two teams too small to cover each other, at twice the management overhead.
- The work needs constant collaboration and has no natural seam. A split down the middle of a single workflow creates a handoff nobody asked for.
- The real risk is knowledge concentration rather than site risk. That is fixed by documentation, not by geography, and it is cheaper.
We do not publish facility access controls, network topology or physical security arrangements. Those are reviewable by your security team under NDA, which is the appropriate place for them.
How a Client Visit Works
Most clients visit before committing to a city, and we think they should.
Tell us which cities and what you want to see
Usually the floor, the team doing work comparable to yours, and the operating cadence. Two cities in a trip is comfortable; three is not.
We confirm dates and handle the logistics on the ground
Airport transfers, hotel recommendations near the office, and a schedule that accounts for real travel times rather than map estimates.
Visitor access is arranged in advance
We need names and identification details ahead of the visit for building access. Where you would be seeing an operation handling another client’s regulated data, some areas will not be accessible, and we will tell you which before you travel rather than at the door.
You meet the people who would run your function
Not an account team assembled for the visit. If the person who would lead your operation is not available that week, we would rather move the date.
For the structural case, including why India operations began here in 1995 and what has changed in the talent market since, read Why India.
Both jurisdictions. Both levers. Start with the Blueprint.
The Blueprint scopes the operating design and the offshore team plan together, including which city fits the function and the compliance posture. Move-in ready offices, IT infrastructure and facilities management included.