u/suzan_james

Something that keeps getting buried in real estate headlines is worth a closer look. India tends to come up as a talent decision, Alphabet's Whitefield lease reads more like an organizational architecture decision.

Roughly 2.4 million sq ft with capacity for 20,000 employees is not a support office footprint. It sits in the same order of magnitude as Google's Mountain View campus. AI infrastructure, Gemini engineering, and applied research are being distributed into India, not outsourced there. And once hyperscalers anchor core engineering in a geography, their implementation ecosystems tend to follow quickly.

For those tracking where global AI engineering capacity is actually being built, does this kind of signal change how you think about your own hiring geography?

A conversation last week got me thinking about how the enterprise AI implementation layer is taking shape, and India keeps appearing at the center of it. Anthropic partnered with Infosys in early 2026 to roll out Claude across telecom, finance, and manufacturing at scale.

The pattern worth paying attention to is structural. Frontier AI labs build models but lack enterprise integration, legacy system expertise, and large-scale delivery operations. Indian IT firms already sit inside Fortune 500 stacks and have spent decades building exactly those capabilities.

What many teams seem to be underestimating is how fast the value chain is shifting, from outsourced coding toward AI orchestration and enterprise governance. Anthropic, OpenAI, and Google are all building the same dependency on Indian system integrators to close the gap between model capability and production deployment.

For those running enterprise AI rollouts, is the implementation partner question becoming as important as the model selection, or does model choice still dominate internally?

Been thinking about this since the OpenAI-Tata announcement dropped, and the detail that stands out is not the headline size but what it changes about inference geography. India tends to come up as a talent market in global hiring conversations, but the compute layer now seems to be catching up faster than most companies anticipated.

Before local inference capacity, Indian AI requests likely routed through Singapore, Europe, or US Azure regions, adding meaningful latency at every hop.

For coding copilots, voice agents, and agentic workflows, that overhead compounds fast. What many teams seem to be realizing is that latency is not cosmetic, it affects retention, conversational cadence, and how intelligent a model actually feels in production. The Tata deployment also includes data residency, which unlocks enterprise and regulated-sector workloads that previously could not use frontier models at all.

For those building AI products with significant Indian user bases, is inference latency already showing up as a real constraint, or has it stayed theoretical so far?

A ruling that keeps coming up in global hiring conversations is the Delhi High Court's clarification on virtual service delivery and permanent establishment risk. India tends to be where this anxiety surfaces most, given how many US companies quietly wonder whether their remote employees there have already triggered tax liability.

The court drew a cleaner line than most companies were working with. Virtual service delivery alone does not create PE, what matters is control and business presence, not location.

A developer logging in from Bengaluru is legally different from someone negotiating contracts or operating as a dependent agent on the company's behalf. What many teams realize is that PE risk comes from operational sloppiness, contractors who start representing the company, engagements that drift from defined projects into open-ended dependencies, not from hiring remotely itself.

For those who have structured India remote teams with PE risk in mind, did this ruling change how you think about the boundary, or were you already drawing it that way?

Something that keeps coming up in founder conversations is how many US companies price India contractor arrangements without accounting for what happens if those structures get scrutinized. India tends to be where this surfaces most sharply, given how quickly project-based engagements drift into effectively full-time ones.

The number that catches founders off guard is not the base tax rate but the penalty stack on top. PE exposure triggers corporate tax at around 38% on attributed Indian profits, plus backdated PF contributions, TDS shortfalls, interest at 12 to 18% annually, and penalties running 100 to 300% of unpaid liability. A single misclassified contractor over two years can quietly build ₹3 to 4 lakh in backdated exposure, and that compounds fast across a team.

What often comes up when companies hit this is that moving to an Employer of Record structure, platforms like Deel, Multiplier, or India-native options like Wisemonk, breaks the PE chain entirely, with the EOR holding the entity, payroll, and statutory liability locally.

For those who have dealt with contractor reclassification in India, did the exposure surface during an audit, a fundraise, or somewhere else?

I have been following how often foreign companies treat Indian contractor engagements as a clean workaround, only to run into permanent establishment exposure a year or two later.

A foreign company triggering PE in India faces a roughly 38.22% effective corporate tax on profits attributable to Indian operations, versus around 25.17% for a domestic subsidiary on the concessional regime. That 13-point gap is where founders start paying attention, but the buried costs often turn out worse. What tends to trigger PE with contractors:

• Dependent agent behavior: signing or committing on the company's behalf
• Exclusivity: the contractor works only for you
• Control markers: company email, fixed hours, dictated tools
• Duration drift: a "3-month project" still running 18 months later

If misclassification stacks on top, backdated PF, ESI, gratuity, TDS arrears, and penalties of 100 to 300% compound quickly. The real damage usually surfaces during fundraise or acquisition diligence, not an audit.

The Employer of Record route often comes up here because the worker becomes the EOR's employee on paper, with the EOR holding the entity, payroll, and local compliance, which tends to break the agency PE chain under treaty.

For those who have navigated a PE assessment or contractor reclassification dispute in India, what surfaced it, and how long did resolution take?

I have been following more companies expanding hiring into India, especially for remote engineering and support teams. What often gets underestimated is how much state-level compliance changes the actual cost of employment.

Many founders assume India has one standard hiring framework, but payroll and compliance seem to vary heavily by state. Professional tax, labour welfare fund rules, Shops & Establishments requirements, and even workweek regulations can differ depending on where employees sit.

A few examples that often come up:

• Maharashtra professional tax vs none in Haryana
• Different labour welfare fund deductions
• 5-day vs 6-day workweek rules
• State-specific registrations and filings

Once teams hire across Bangalore, Gurgaon, Chennai, and Pune at the same time, the operational math tends to become messy pretty quickly.

That also seems to be why India-native Employer of Record providers like Wisemonk come up more often in conversations now. Many global teams realize they need localized payroll, contracts, and compliance handling before scaling across multiple states.

For those who have hired across India, what compliance or payroll difference caught your team off guard first?

More global companies expanding into India seem to be realizing that setting up a subsidiary does not automatically remove Permanent Establishment risk. The India talent market still attracts long-term investment, but cross-border tax exposure often comes up much later than hiring plans do.

What stood out in the Caterpillar-related case was not the final verdict, but the timeline. Indian tax authorities alleged the US parent had a PE through its local entity using multiple arguments around fixed place, service activity, and dependent agent relationships. The company eventually won, but the dispute still stretched from 2019 to 2025 across multiple court levels.

Many founders seem to underestimate how expensive “winning” can become once years of litigation, reassessment notices, and compliance reviews enter the picture.

That also appears to be why structures like EORs increasingly come up in early-stage expansion conversations. Companies often discover they would rather keep payroll, contracts, and local compliance ring-fenced before committing to full entities.

Curious what other operators learned while navigating PE concerns or India expansion structures.

I have been following India's infrastructure buildout closely, and the Adani commitment seems to be the piece that shifts the conversation from talent market to compute market. India tends to come up in global hiring discussions, but what is happening at the infrastructure layer now suggests the frame needs to expand beyond headcount.

The pattern that keeps coming up is that AI is no longer purely a software race, it is a power and compute race. Adani's $100B commitment toward energy, hyperscale data centers, fiber, and AI-ready industrial capacity signals that India is building both sides of that equation simultaneously. What many companies seem to be underestimating is the stack movement this enables.

A few years ago, India was where support teams lived. Increasingly it is where engineering, AI ops, platform teams, and cloud modernization work runs, and soon where the underlying infrastructure that powers those workloads physically sits. Many founders mention that the "back office" mental model is the last thing holding their India strategy back from being a genuine architectural decision.

For those evaluating where to run AI infrastructure or engineering workloads over the next few years, is physical compute geography entering that conversation yet or does it still feel premature?

I have been following the infrastructure argument against building in India for a while, and the Reliance commitment seems to be the data point that makes it hardest to sustain. India tends to be where this conversation surfaces most often, given how many global companies still evaluate it using a mental model that is several years out of date.

The "great talent, weak infrastructure" objection seems to be collapsing faster than most founders have updated their thinking. India already solved population-scale digital infrastructure with UPI, Aadhaar, cheap mobile data, and real-time payments at a scale very few countries have matched. What Ambani's $110B commitment signals is that the next layer, AI compute, hyperscale data centers, enterprise AI infrastructure, and local model ecosystems, is now being built with the same seriousness. What many teams realize when they look at the full picture is that the bottleneck is no longer infrastructure at all. It is whether companies can attract and retain AI-native talent before competition for that profile intensifies further.

For those who have evaluated or revisited India expansion recently, is the infrastructure concern still coming up internally, or has that objection quietly disappeared from the conversation?

I have been following Dario Amodei's comments on India closely, and the framing he used seems to matter more than the headline number. India tends to come up in global hiring conversations as a cost or scale decision, but Anthropic's positioning suggests something structurally different is happening.

The detail that keeps standing out is how India is actually using AI. Nearly half of Claude usage there is technical work, coding, debugging, system modernization, building AI workflows, not consumer experimentation. Revenue from India reportedly doubled in four months, and Claude Code adoption grew even faster. What many founders seem to be underestimating is the second-order implication: when AI compresses execution advantage, talent density becomes the actual moat. The companies that win over the next five years may not be the ones with the most engineers, but the ones with the highest concentration of AI-native engineers. India is quietly becoming the deepest market for exactly that profile.

For those who have been building or hiring engineering teams in India over the last year, are you seeing AI tool adoption move faster there than in your US or European teams, or does the gap feel less pronounced on the ground?

I have been noticing more companies quietly expanding teams outside the US after the recent H-1B restrictions. India keeps coming up in those conversations, especially Bengaluru, because the engineering and AI talent base was already mature.

What seems to be happening is that the jobs did not necessarily stay local. Many companies appear to have shifted software engineering, AI, and product hiring directly to India instead of waiting through uncertain visa processes. Founders often mention that once relocation became harder, distributed hiring became the easier operational path.

A few patterns that keep coming up:

• Bengaluru absorbing engineering growth
• Remote-first product teams increasing
• US HQ with India execution models
• Faster offshore hiring after visa delays

Many teams also realized the infrastructure for this already existed. Employer of Record setups and local compliance support seem to have made international hiring easier than opening new entities.

For those who have managed hiring recently, did visa restrictions push your company toward building teams abroad?

I have been following the debate around H-1B numbers and how different political figures are framing the data. At the same time, India keeps showing up in hiring discussions because many global companies already had mature engineering and product teams there.

What seems to matter less now is whether the exact decline was 90% or something lower. Founders often mention that once visa policy starts feeling unpredictable, companies begin building alternatives instead of waiting for clarity. Bengaluru, Hyderabad, and Pune seem to be absorbing a growing share of engineering, AI, and product hiring that previously depended on US relocation.

A few patterns that often come up:

• Less reliance on visa pipelines
• Faster India team expansion
• Distributed engineering becoming normal
• Hiring decisions driven by predictability

Many teams also realize this shift became easier because the operational layer already existed. Employer of Record models and local compliance infrastructure seem to have reduced the friction of hiring internationally without opening entities first.

For those who have managed cross-border hiring recently, did visa uncertainty change how your company planned team growth?

I have been noticing more founders treating global hiring as a simple nearshore vs offshore debate lately. India keeps coming up because companies scaling international teams seem to care more about ecosystem depth than geography labels.

A country with 1,800+ GCCs operates very differently from one with 600. Many teams realize this only after trying to scale beyond the first few hires.

India usually comes up for:

• large engineering scale
• deep management layers
• 24/7 operations
• specialized talent clusters

Mexico often fits better for:

• real-time collaboration
• faster HQ access
• tighter product cycles

What seems to be changing now is that companies are no longer optimizing only for labor cost. Execution speed, resilience, and diversification matter just as much.

Curious what other founders have seen after scaling teams across different regions.

I have been noticing more companies comparing India and Vietnam while building remote teams. India usually comes up for engineering scale and international team experience, while Vietnam seems to be getting attention for manufacturing growth and newer outsourcing hubs.

The “22x bigger” comparison seems directionally true, but many founders realize the ecosystems are built very differently. India’s tech industry has compounded for decades through IT services, GCCs, SaaS, and outsourcing. Vietnam’s rise seems more tied to electronics manufacturing and fast-growing software outsourcing from a smaller base.

A few things that often come up:

• Hiring scale
• English-speaking workforce
• Software vs manufacturing focus
• Ecosystem maturity

Many teams seem to find that productivity, retention, and ability to scale matter more than headline market size.

Curious what other founders or hiring teams have experienced comparing India and Vietnam for remote hiring?

I have been noticing more global companies treating India less like a secondary outsourcing destination and more like a strategic operational hedge. Apple’s recent manufacturing shift seems to be one of the clearest signals that this transition is becoming structural.

What stands out is that this no longer looks like a temporary tariff response. Many founders and operators mention that “China + 1” now feels like a permanent supply-chain strategy rather than a diversification experiment. India keeps coming up because of manufacturing scale, engineering talent, and relatively lower geopolitical exposure for U.S.-bound production.

What also seems important is that the trade war did not really bring electronics manufacturing back to the U.S. at scale. Instead, it appears to have accelerated regional supply-chain redesign around countries like India. Foxconn and Tata expanding manufacturing capacity in Tamil Nadu feels less like cost arbitrage and more like long-term resilience planning.

Curious what other founders and operators think. For those managing global supply chains, does India now feel strategically unavoidable for manufacturing diversification?

I have been noticing more founders caught between investor pressure to hire locally and economics that increasingly point elsewhere. India tends to be where this tension surfaces most directly.

The US-first hiring case made sense when global teams meant timezone chaos and unreliable vendors. That version is fading fast. A senior US engineer now runs $220K to $350K fully loaded, while founders are building core engineering and AI teams in India at a fraction of that. The top tier of India's technical talent is competing at a genuinely global level.

What many founders realize too late is that runway is strategy, and where you hire determines how much of it you have. A high-output India team delivers more product iterations and more survival time on the same budget. The new model is distributed ownership from day one, not US headquarters with India execution.

I have been noticing more early-stage founders treat entity setup in India as the default "serious company" move, often before validating whether their India team structure will hold long term. India tends to be the first market where this surfaces, given how fast headcount there can grow from one hire to ten.

The problem seems to be that founders conflate wanting to hire in India with needing an Indian entity. Entity setup brings PF, gratuity, TDS, professional tax registrations, local directors, and annual audits before the team has even confirmed what functions they are building there. What many realize after setup is that the hard part was never incorporation, it was ongoing compliance, payroll operations, and clean exits across two jurisdictions.

Companies that start with an Employer of Record model instead tend to stay compliant and operationally flexible while the India hiring motion is still being tested, handling local payroll, contracts, and statutory benefits without locking in entity overhead too early.

For those who have been through this decision, did you start with an entity or an EOR first, and would you sequence it differently in hindsight?

Been thinking about this after seeing India and Vietnam come up repeatedly in the same breath when founders talk about where to build next. India dominates for engineering talent, but Vietnam keeps entering the frame for manufacturing and operations teams.

The number that catches people off guard is export intensity. Vietnam's exports run at roughly 80 to 85 percent of GDP versus India's 20 to 25 percent, a 4x gap that reflects something structural. What many founders realize when they sit with that comparison is that the two countries are not competing for the same role. Vietnam tends to win for hardware, electronics, and export-oriented operations. India tends to win for engineering depth, AI talent, and knowledge work at scale. Treating them as interchangeable options rather than complementary ones seems to be where the confusion starts.

For those who have evaluated both markets, did you end up splitting functions across countries or consolidate into one?

More US startups seem to be building international engineering teams earlier than they used to. India keeps becoming a default choice because the talent pool is large and many engineers already have experience working inside global product companies.

What founders often underestimate though is how much the market has changed over the last few years.

A lot of hiring processes still seem built around an old outsourcing mindset. Long interview cycles, vague ownership, low-context contractor arrangements, and generic job descriptions tend to push strong candidates away pretty fast now. Many teams appear to realize this only after struggling with retention or hiring quality.

The companies that seem to hire better in India usually operate differently:

• smaller high-trust teams
• founder-led hiring conversations
• faster offer decisions
• product ownership early on

Another thing that often comes up is compliance complexity once the team grows beyond a handful of people. Some founders eventually move toward an Employer of Record setup because local payroll, contracts, benefits, and statutory compliance can become difficult to manage informally.

For those who have built teams in India recently, what part of the hiring process turned out to be most different from your expectations?