TCS Shed 23,460 Engineers in FY26. Boolean Finds 108.

TCS closed FY26 down 23,460 heads, roughly double the "2% / 12,000" cut CEO K Krithivasan announced in July 2025. The exits skew heavily to mid and senior grades in SAP, ServiceNow, Oracle, Salesforce, and Workday. Western sourcers hunting exactly those skills are still firing the same Boolean strings at LinkedIn Recruiter and missing the largest enterprise-engineering displacement of the decade.

The 23,460 number is the story, not the 12,000

TCS ended FY26 with 584,519 employees, down 23,460 year over year, a 3.85% decline from 607,979 in FY25. The gap between the announced cut (12,261, per Deccan Herald) and the actual net decline is where the sourcing opportunity lives.

The mechanism: the headline restructuring stacked on top of tightened bench policies, forced "voluntary" exits, and attrition that climbed to 13.7%. CHRO Sudeep Kunnumal declared the restructuring complete at FY26 close, but the math says the true displaced cohort is nearly 2x the press-release figure. Sourcers using 12,000 as their TAM estimate are undercounting by half.

23,460

Add the adjacent Indian IT services cuts and the pool gets larger:

• Infosys: 8,000+ role eliminations
• Wipro: 5,500+
• HCLTech: 4,200+
• TCS: 23,460 net

That is roughly 41,000 mid-to-senior enterprise engineers into the Indian market in a single fiscal year, most of them concentrated in the exact skills GCCs and US enterprise buyers claim they cannot fill.

What the exiting cohort actually knows

The exit cohort is dominated by 4-to-12-year enterprise-platform specialists: SAP, Oracle, Salesforce, ServiceNow, and Workday. That is not a guess, it is a direct read from TCS's own March 2026 walk-in drives across 10 cities, which targeted exactly that profile.

Which means Western sourcers should stop chasing generic "Java engineer" or "cloud engineer" strings and mirror TCS's own hiring taxonomy. The skills to prioritize:

1. SAP (S/4HANA migrations, FICO, MM, SD, ABAP, BTP)
2. ServiceNow (ITSM, HRSD, CSM, platform architects)
3. Oracle (EBS, Fusion Cloud, PL/SQL)
4. Salesforce (Sales Cloud, Service Cloud, Vlocity)
5. Workday (HCM, financials, integrations)

Every one of these carries Fortune 500 delivery history. The engineers walking out the door have shipped enterprise projects for TCS's client book for a decade or more.

Why LinkedIn Boolean misses most of them

Boolean search on LinkedIn systematically undercounts ex-TCS engineers because they list the employer under half a dozen name variants and often bury it under client-project company names. Any "ex-TCS" AND SAP string is fishing in a small corner of the actual pond.

In Refolk's index of professional profiles, only 108 senior or manager SAP professionals in India explicitly reference "Tata Consultancy Services" in their profile text. Of those, 22 still list TCS as current employer, meaning about 86 are already ex-TCS or actively transitioning. That is an ~80% exit rate on the cohort you can find with a Boolean, and the real cohort is many multiples larger once you account for name variants:

• Tata Consultancy Services
• Tata Consultancy Services Limited
• TCS
• TCS Ltd
• TCS Digital
• Client-embedded titles ("Senior SAP Consultant at [Bank]") with TCS only in the experience body

This is the exact gap Refolk closes. You describe the person in plain English ("senior SAP FICO consultant, 10 to 15 years, worked at TCS on a Fortune 500 retail account, now in Bengaluru or Hyderabad") and get back a ranked shortlist that ignores whether they wrote "TCS" or "Tata Consultancy Services Ltd." in the employer field.

The index numbers Western sourcers should be working from

The reachable pool is much larger than any Boolean string will show. Refolk's index has 13,678 SAP consultants, architects, and leads in India, and 7,758 ServiceNow developers, consultants, and architects. Those are the working universes, not the 108-profile keyword slice.

Geography matters more than most Western sourcers treat it. Ex-TCS SAP profiles in the index cluster in five cities, not "India" as a blob:

• Bengaluru (6 in the surfaced cohort)
• Hyderabad (3)
• Mumbai (3)
• Ahmedabad (2)
• Thane (2)

Anchor searches on those cities and you get response rates that a country-level search will never match, because you can name the local GCC competitors in your outreach.

The severance changes everything about your outreach

These engineers are cash-cushioned, not desperate, which means boilerplate InMails fail. Employees with 10 to 15 years of TCS tenure are reportedly receiving severance equivalent to about 1.5 years of salary. Those with 15+ years are getting 1.5 to 2 years.

That severance math flips the behavioral model. A mid-senior ex-TCS engineer with 18 months of cash runway does not behave like an active jobseeker. They behave like a passive candidate at Google. They can afford to hold out for a GCC role at Target India or Wells Fargo at a 1.7x niche premium, or a contract-to-hire with a US enterprise at proper rates, rather than take the first body-shop offer that lands.

Severance of 18 months turns a laid-off consultant into a passive candidate. Write the message accordingly.

Which means your outreach template needs to change:

• Do not lead with "I saw you were impacted." They know. They are not embarrassed. But they are also not in a hurry.
• Lead with the client logo and the scope. Name the Fortune 500 account, name the module, name the migration wave. "S/4HANA greenfield for a top-5 US retailer" beats "exciting SAP opportunity."
• Anchor on comp against the GCC benchmark, not against Indian services rates. Their alternative is Walmart Global Tech India at a 1.7x premium on niche skills, not another TCS-style role.
• Offer contract-to-hire or direct-hire clarity in the first message. Ambiguity reads as body-shop.

The GCC absorption clock is 45 days

India now hosts more than 1,800 Global Capability Centers, employing roughly 2 million professionals and generating $64.6 billion in export revenue in FY2024, a 40% year-over-year jump. Between early 2024 and late 2025, about 110 new GCCs launched. Every one of them wants exactly the profile TCS just released.

Demand for mid-to-senior GCC hires is forecast to rise from 63% in 2023 to 77% by 2025, and 58% of GCCs take more than 45 days to fill critical roles. That 45-day window is your competitive clock. Companies visibly absorbing the ex-TCS cohort in the index:

• SAP cohort absorption: Infosys, Bristlecone, UST, Grant Thornton Bharat, Maventic, Cognizant, Accenture India
• ServiceNow cohort absorption: Coforge, Deloitte, Infosys
• GCC buyers scaling aggressively for this profile: Target India, Wells Fargo, Lowe's India, JPMorgan Chase, Walmart Global Tech India

Most of the TCS layoffs and internal adjustments completed between August and September 2025, so the cohort has been in-market for months. The top decile at each skill and city is already gone. The next decile is being interviewed right now. If you are running GCC recruiting in India or staffing US enterprise SAP/ServiceNow rolls, waiting until Q2 2026 to start means paying an agency 25% to backfill from the second tier.

The five sourcing moves that actually work on this cohort

Stop optimizing your LinkedIn Recruiter Boolean. Optimize the workflow around it. The five moves that separate teams landing ex-TCS engineers from teams complaining they cannot find them:

1. Search by client project, not by employer. "Implemented S/4HANA at [named US retailer]" surfaces more relevant profiles than any TCS-string does, because senior consultants headline their client work.
2. Geo-anchor to the five cities, not to India. Bengaluru, Hyderabad, Mumbai, Ahmedabad, Thane. Naming the local competitor GCC in your outreach earns replies.
3. Mirror the TCS walk-in taxonomy exactly. SAP, Oracle, Salesforce, ServiceNow, Workday, 4 to 12 years. That is the exit cohort. Do not chase adjacent skills.
4. Sequence around the severance clock, not the availability date. Reach out at month 3 of severance, not month 1. Month 1 they are decompressing. Month 3 they are comparing offers.
5. Use a tool that reads plain-English descriptions, not keyword strings. Describe the person you want, including the client-account context, and the ranked list includes profiles a Boolean will never surface.

If your Boolean string covers only TCS, you are also ignoring 17,000+ additional displaced engineers from Infosys, Wipro, and HCLTech. A well-written natural-language query can pull the full "Indian IT services displacement class of FY26" in one shot, then let you filter by client history, module, city, and years of experience.

Where the advocacy groups fit in

The All India Organisation of Employers has argued the TCS cuts could potentially fall foul of Indian labor law, and the Forum for IT Employees (FITE) and NITES (Nascent Information Technology Employees Senate) have been vocal on behalf of displaced engineers. That matters for sourcers in two ways.

First, these groups are useful public sources for named engineers willing to speak on the record about their experience, which is a legitimate warm-intro path if you are a US or EU staffing firm trying to build referral loops into the cohort. Second, the legal noise means TCS is under public scrutiny on how it handles the exiting cohort, which lowers the reputational risk of engineers openly comparing offers before their notice period ends.

FAQ

How many ex-TCS engineers are actually available to hire right now?

TCS's net FY26 decline was 23,460 heads, most of them mid to senior grades, and adjacent cuts at Infosys (8,000+), Wipro (5,500+), and HCLTech (4,200+) push the combined Indian IT services displacement past 41,000. Most of the TCS exits completed between August and September 2025, so the cohort has been in-market for months. The top decile at each skill-city combination is either already placed or in final rounds at Indian GCCs, but the working pool remains enormous, particularly in SAP (13,678 profiles in Refolk's Indian index) and ServiceNow (7,758).

Why does LinkedIn Boolean miss so many ex-TCS engineers?

TCS engineers list the employer under at least six name variants (TCS, TCS Ltd, Tata Consultancy Services, Tata Consultancy Services Limited, TCS Digital, and client-embedded titles) and senior consultants often headline their client account rather than TCS itself. A search like "ex-TCS" AND SAP catches only the small slice who used that exact string. Refolk's index shows just 108 senior SAP profiles in India that reference TCS in profile text, versus the many thousands of ex-TCS SAP engineers who actually exist. Natural-language search that understands employer synonyms and client-project context is the only reliable way to surface the full cohort.

What outreach message works on ex-TCS engineers with 18 months of severance?

Skip the "I saw you were impacted" opener. This cohort has 1.5 to 2 years of severance and is behaving like passive candidates, not active jobseekers. Lead with the client logo, module, and scope ("S/4HANA greenfield for a top-5 US retailer"), anchor comp against Indian GCC benchmarks (Target India, Wells Fargo, Lowe's India) rather than services rates, and offer clarity on contract-to-hire versus direct-hire in the first message. Reach out at month 3 of their severance, not month 1.

Which Indian cities should I concentrate on?

Ex-TCS SAP profiles cluster tightly in Bengaluru, Hyderabad, Mumbai, Ahmedabad, and Thane. Geo-anchor your searches to those five cities rather than "India" as a country blob. Naming the local GCC competitors ("we pay above what Wells Fargo Hyderabad offers senior FICO leads") earns replies that a generic pan-India message never will, because senior enterprise engineers in this cohort make relocation decisions on family, school, and cost-of-living lines that map to specific cities.