Are AI-driven cuts and a 2,000-person hiring plan really contradictory?
Companies in finance and technology are using AI to automate work, slow hiring and redesign teams. Yet Reuters reported on August 19, 2026 that Charles Schwab plans to expand its new Hyderabad GCC to roughly 2,000 employees by the end of 2027, starting with about 500 hires in the first year and bringing some contractor technology work in-house.
The 2,000 figure is not formal long-term guidance from Schwab; Reuters attributed the plan to a source. But Schwab’s own India careers site and current Hyderabad listings show active hiring across software development, data engineering, systems, platform and business systems roles. The signal is real even if the final headcount can change.
Schwab is not simply building a cheaper back office
Schwab describes Hyderabad as central to its growth, combining people and technology to drive innovation, scale and efficiency for solutions used by millions of U.S. clients. Reuters similarly describes the GCC’s focus as technology development, engineering and operational support.
Roles such as data platform engineering, software engineering management, systems engineering and SRE platform support carry more responsibility for system design, operations and reliability than a traditional transaction-processing center. Cost still matters, but it is no longer the whole operating model.
India’s GCCs are becoming global organizations, not just outsourced delivery centers
Zinnov–Nasscom reports 2,117 GCCs in India in FY2026, with 2.36 million employees and $98.4 billion in revenue. The report describes the structural shift as moving from a delivery engine to an enterprise nerve centre.
Its maturity model classifies 39% of GCCs as Portfolio Hubs with end-to-end product, platform and IP ownership, and another 5% as Transformation Hubs with AI-led operations and CXO mandates. Not every center has reached that level, but the direction is clear: more enterprise authority is moving into India-based teams.
AI may not eliminate outsourcing so much as recalculate what can stay outsourced
Work that is rule-based, repeatable and low in context dependence is easier to automate. As those tasks shrink, the economics of large offshore teams built mainly for low-cost execution become less compelling.
Work tied closely to core data, security, platform architecture, customer experience and regulation is different. Using AI safely often requires integrated data, clear decision rights and teams accountable for outcomes. Schwab’s reported move to bring some contractor technology work in-house is one example of how AI-era operating models can redraw the boundary between vendor and internal teams.
Hiring is starting to look more like a capability-density problem than a headcount problem
Zinnov’s 2026 GCC talent research describes strong competition for AI, cybersecurity, cloud and data capabilities while legacy IT and routine engineering face automation-led redesign pressure.
The important shift is not simply that India is adding people. A 100-person organization dominated by execution roles is very different from a 100-person organization that owns data, platforms, security and product outcomes. In an AI-heavy operating model, the capability and decision rights concentrated in each role matter more than raw headcount.
For companies, ownership strategy should come before location strategy
A simple comparison of expensive U.S. labor versus cheaper Indian labor misses the central question. Companies first need to decide which work should be automated, which can remain with vendors and which capabilities must sit inside a controlled strategic hub.
Only then does location strategy become useful. The boundary between headquarters, GCCs and vendors should increasingly be designed around data access, decision rights, customer and regulatory context, and the cost of operational failure—not just wage tables.
For workers, what you owned matters more than the fact that you worked offshore
Two engineers in Hyderabad can have very different career value. One may mainly process tickets; another may own architecture, reliability or data pipelines for a global platform. Employer name and geography matter less when the scope of ownership is different.
As AI accelerates routine implementation, career evidence should increasingly show who defined requirements, controlled data quality, handled outages, made security trade-offs and remained accountable for a system’s outcome. Those responsibilities travel across markets better than a generic job title.
The lesson for Korea and Japan is not India’s wage level, but the movement of organizational authority
India’s GCC growth can look like a distant labor-market story. It is more relevant when viewed as a map of where global companies are moving product, data, AI and platform ownership. The same decision affects headquarters teams, captive development centers and outsourcing providers in Korea and Japan.
As AI reduces repetitive work, companies will increasingly decide not only where people should sit, but where judgment and ownership should sit. Firms and workers that track that migration early will understand the next labor market better than those watching headcount alone.
BANSEOG VIEW
AI-era global employment is better read as a shift in ownership than a simple story of job cuts
The claim that AI reduces jobs and the fact that India’s GCC ecosystem is expanding can both be true. Repetitive execution and high-ownership product, data, platform and security work are not the same labor market.
Banseog Search reads global hiring through the movement of role ownership, not only wage differences between countries. For companies, that means redesigning the boundary between vendors, GCCs and headquarters. For professionals, it means proving what systems and outcomes they actually owned rather than relying on title or location alone.
SOURCES
Primary sources and references
- Reuters · Charles Schwab to scale India centre workforce to 2,000 by 2027
2026년 8월 19일 보도. 취재원을 인용해 Schwab이 Hyderabad GCC 인력을 2027년 말까지 약 2,000명으로 확대할 계획이며, 첫해 약 500명 채용과 일부 인도 contractor 기술업무의 내부화를 추진한다고 전함.
- Charles Schwab Careers · Schwab India
Hyderabad가 Schwab 성장의 중심 역할을 하며 기술과 인재를 결합해 innovation, scale, efficiency를 지원한다고 설명하는 공식 채용 페이지.
- Charles Schwab Careers · India jobs
2026년 8월 확인 시 Software Development, Data Engineering, Systems, Platform, Business Systems 등 Hyderabad의 실제 기술 직무가 게시되어 있었음.
- Zinnov–Nasscom · India GCC Landscape 2026
2026년 3월 기준 인도 2,117개 GCC, 236만 명 인력, 984억달러 매출을 제시하고 GCC가 delivery engine에서 enterprise nerve centre로 이동한다고 분석.
- Zinnov · Salary, Attrition & Hiring Trends in GCCs 2026
AI·사이버보안·클라우드·데이터 등 핵심 역량은 경쟁이 강한 반면 routine engineering/legacy IT는 자동화와 재설계 압력을 받는다고 분석. 95개 이상 GCC, 150개 이상 센터 기반 조사라고 밝힘.
The roughly 2,000-person end-2027 figure is not formal long-term headcount guidance from Schwab; Reuters reported it citing a source. Schwab’s official careers pages and current Hyderabad roles are used separately to verify the center’s stated role and current hiring mix. GCC scale and maturity come from Zinnov–Nasscom; role-level AI pressures come from Zinnov’s 2026 GCC talent research. The framing around a shift in ownership of work is Banseog HR Intelligence’s synthesis of these sources.