Placement Planning When IT-Services Mass Hiring Keeps Shrinking

Seven thousand three hundred eighty-nine. That is how many more people TCS, Infosys, HCLTech, Wipro, and Tech Mahindra collectively lost than they hired in FY2026, according to Moneycontrol’s analysis of the five firms’ quarterly disclosures. A year earlier, the same five firms had added 12,718 employees between them. That swing, from net addition to net reduction, happened inside twelve months, at companies that have been the largest single destination for engineering graduates from Indian campuses for two decades.

I have run partnerships across more than 2,000 institutions over 18 years, and the placement cells navigating this well are not the ones hoping the old volume returns. They are the ones who read the swing correctly: not as a hiring freeze, but as a redistribution. The graduates these firms are not absorbing in bulk have not vanished from the job market. They are being hired by a wider set of employers, on different terms, and a placement cell has to go find that demand rather than wait for it to arrive at the old address.

A slower-growing workforce inside a faster-growing industry

The gap shows up clearly in NASSCOM’s own numbers. The Strategic Review 2026, launched at the NASSCOM Technology and Leadership Forum in February, projects the industry reaching 315 billion dollars in FY26 revenue, up 6.1 percent year on year. Direct tech-sector employment, over the same period, is projected to grow 2.3 percent, reaching 5.95 million. Revenue growing nearly three times faster than headcount is the structural story behind every individual company’s cautious fresher guidance this year.

This is not evidence that the industry has stopped needing people. It is evidence that the industry has stopped needing the same number of people per unit of revenue. AI-assisted delivery, tighter bench management after the over-hiring years of 2022 and 2023, and a shift toward skill-matched recruitment over generic-pool recruitment are all doing the same thing at once: reducing how many freshers a rupee of new business requires. HCLTech’s own investor disclosures put its FY2026 fresher hiring at 11,744, a figure management has said will look similar in FY2027 rather than expand, and that pattern, hold steady rather than scale up, is close to what most of the large listed firms are now signalling.

For a placement cell, the useful reading of this data is not despair about IT services. It is a clear signal about where to look next. More on why fewer companies are visiting campuses at the volumes they used to and how the shift from bulk to selective recruitment is reshaping what a drive looks like fills in the mechanics of that same shift from the recruiter’s side.

Where the growth is

Three segments are hiring in ways that do not show up if a placement cell is only counting IT-services drive numbers.

Global Capability Centres are the most visible of the three, building engineering-track fresher pipelines in AI, data, cloud, platform, and cybersecurity roles. The segment’s shape, screening pattern, and expansion into non-metro campuses are covered in detail separately; the point for this article is simpler: GCCs are recruiting on a genuinely different calendar and a genuinely different rubric from an IT-services drive, and a placement cell that treats them as an occasional bonus rather than a planned segment is leaving real offers on the table.

Core-engineering and manufacturing employers are the segment placement cells most often underweight, because the last decade trained everyone, cells included, to think of campus recruitment as primarily a software story. That is changing on the ground. Government data on the Production Linked Incentive schemes shows cumulative investment of over 2.40 lakh crore rupees and more than 14.15 lakh direct and indirect jobs generated as of March 2026, concentrated in electronics, automotive, and industrial manufacturing. Jobs generated by that investment are not all engineering roles, but a meaningful share are, and they draw specifically on the branches, mechanical, electrical, electronics, that an IT-services-only placement strategy has always underserved.

Product companies and technology startups are the third segment, smaller and more selective per visit than either of the other two. A product company drive typically makes a handful of offers rather than dozens, and it screens for depth in a specific area, a shipped project, ownership of a real system, rather than broad aptitude. The volume from this segment alone will not replace what IT-services used to offer, but combined with GCCs and core-engineering employers, it adds a third source that draws on a different part of the student pool.

Regional firms, SMEs, and structured apprenticeship pathways are a fourth, quieter stream. They rarely run a formal campus drive; a placement cell reaches them through alumni working locally, faculty industry contacts, and direct applications rather than an invitation letter. National apprenticeship engagement has grown sharply over the past few years and now touches automotive, electronics, and IT-enabled roles alongside the traditional trades. This stream will not carry a placement cell’s headline number, but it absorbs students the four larger segments do not reach, particularly outside the metro belt.

Segment	Typical offers per campus visit	What is screened	Best-fit branches
IT services	Large batches, fewer per visit than in past cycles	Aptitude, coding fundamentals, communication	CSE, IT, ECE
GCCs	Smaller, role-specific batches	Domain projects (AI, cloud, data, embedded), systems thinking	CSE, IT, ECE, EEE
Core engineering / manufacturing	Batches tied to plant or project need	Lab and design work, domain fundamentals, PLC or CAD exposure	Mech, EEE, ECE, civil
Product / startups	Small, highly selective	DSA depth, shipped projects, ownership	CSE, IT, some ECE
Regional firms / alumni channel	Ongoing, not drive-based	Practical skills, communication, availability	All branches

A core-branch placement reversed in one Chennai admissions cycle

The clearest evidence that non-IT segments are absorbing real demand is not a national estimate. It is what happened inside one city’s placement season. At College of Engineering, Guindy, 91 of 97 mechanical engineering graduates and 45 of 46 electrical and electronics engineering graduates were placed in the 2025-26 cycle, Times of India reported in May 2026. K. K. Sivagnana Prabhu, the placement official at RMK Group of Engineering Colleges, put the group’s overall figure at 81 percent, five percentage points above the previous year. A later report found six core-engineering programmes across Anna University’s four campuses reached full placement for the same batch, with EEE recording the highest average package among them.

Mechanical and EEE placements had been visibly weaker in the years before this. What changed was not the students. It was the pool of employers actively recruiting core branches, expanding as manufacturing and electronics investment scaled up in the region.

A placement cell in Nagaland, working with a smaller engineering college whose intake is heavily mechanical and electrical rather than CSE-heavy, used this same signal to rework its approach in 2025. Its historical placement rate had trailed comparable colleges for years, mostly because its branch mix did not match what the visiting IT-services firms wanted. Rather than compete for a shrinking share of software drives its students were poorly matched for, the cell built a list of manufacturing and power-sector employers active in the northeast and in the industrial corridors its alumni had already found work in informally. It reached out directly, offered a shortlist of final-year students with documented lab and project work, and secured its first formal recruiter visits from two electronics-manufacturing firms within a single term. The total offer count was modest, twenty-two students across both firms, but it was the first time in the cell’s history that a recruiter had come to campus specifically because of the college’s branch strength rather than despite it.

Training by destination, not by calendar slot

Once a placement cell accepts that its recruiter base now spans genuinely different segments, the training implications follow directly. A single aptitude-and-coding programme run in the months before the season, then applied uniformly to every drive that shows up, prepares students reasonably well for IT-services screening and poorly for everything else.

GCC recruiters weigh depth in a specific technical domain more heavily than a general aptitude score. A student who can walk a panel through a deployed cloud project is a different candidate from one who cleared an aptitude test with no domain artefact to show. Core-engineering employers want to see lab work and design documentation, the kind of evidence a college can prepare and present systematically rather than leave to chance. Product-company interviews go deep on a small number of technical questions rather than wide across many topics.

None of this means running three separate curricula from day one. It means organising the final-year training calendar around destination rather than around a single generic track, so that students heading toward a GCC shortlist, a core-engineering interview, and an IT-services drive each get preparation matched to what they will face.

Take a CSE batch of 200 students as a working example. A cell that runs one common aptitude-and-coding programme, then sends the whole batch to every visiting recruiter regardless of type, will place its strongest quartile reasonably well and leave the middle and lower bands underprepared for anyone but the least selective IT-services drive. A cell that segments the same batch early, a project-and-systems track for the fifty or sixty students with the strongest technical depth aimed at GCC and product-company shortlists, a broader aptitude-and-communication track for the rest aimed primarily at IT-services and regional firms, gives every student a preparation path matched to a realistic outcome rather than one path calibrated to the strongest recruiter in the room. The same logic applies branch by branch for a mixed CSE-ECE-EEE-mechanical cohort: the segmentation variable is not academic performance, it is which recruiter type a student’s skills and interests actually fit.

A ninety-day plan for the placement cell

For a cell starting this work now, the most useful frame is a three-month build before the next season opens.

In the first thirty days, pull the last three years of offer data and sort it by recruiter type: IT services, GCC, core engineering, product and startup, and regional. This single exercise usually reveals the dependency clearly, whether two or three firms account for more than half of all offers, and which segments the cell has effectively never worked. It also surfaces which branches have consistently thin placement outcomes relative to their peers, a signal worth cross-checking against the segment table above.

In the next thirty days, re-establish contact. Reach out to every recruiter across every segment that has visited in the past three years but not recently, starting with GCCs and core-engineering employers, both of which typically need longer lead times than an IT-services drive. A short note on this year’s cohort, its branch composition, and the specific project or lab work students have completed is usually enough to reopen a relationship that has gone quiet. For core-engineering and manufacturing employers in particular, a college’s regional industry contacts, alumni working locally, faculty with industry ties, are often faster than a formal placement-office letter.

In the final thirty days, align the training calendar to what has come back from those conversations. By this point the cell should have early signals on which segments are likely to visit and what they are hiring for. Route students accordingly, run a baseline assessment against each segment’s likely screen, and use the six to eight weeks before drives begin to close specific, identifiable gaps rather than run a generic revision pass across the whole batch.

Recruitment has looked like a portfolio, not a single dominant channel, everywhere else in the Indian job market for years. Engineering placement is only now catching up to that shape. A placement cell that builds its map before the season, rather than discovering the gap when the usual firms send smaller teams, is the one that walks into drive season already knowing where its offers are coming from.