The tier-2 city is something else entirely

Every few quarters a tier-2 city gets crowned the next Bengaluru, and the label misleads every time. They’re winning something the metros structurally can no longer offer: stable, loyal, specialised talent that hasn’t been bid up by 10 neighbours on the same floor.

A centre that opens in Coimbatore expecting a discounted Bengaluru gets neither the depth nor the discount. What it gets, if it reads the city right, is a pool that stays, owns a charter end-to-end, and isn’t rehearsing its next move before probation ends. That’s a genuinely valuable thing. It’s also a different thing from what a metro delivers, and the whole location decision turns on not confusing the two.

The context makes the mistake expensive. GCC hiring is expanding hard, India’s global capability centres are projected to cross 2,400 centres and employ well over two million people by the late 2020s, and a growing share of new sites are landing outside the top metros. When the pipeline is that hot, the pressure is to reuse the metro template because it’s the one you already have. Reusing it is precisely how a tier-2 bet goes wrong.

The cities aren’t interchangeable, and neither should the plans be. One draws engineering talent anchored to a strong local institution and a manufacturing base. Another has a quietly deep pool of returners: people who trained in the metros and came home for the life. A third is winning on a specific vertical the region has real density in. Same “tier-2” label; three completely different hiring plans.

Reading which is which is the actual work. Coimbatore sits on an engineering and textile-manufacturing base with a strong institutional feeder, so it holds product and platform engineering well and struggles to staff, say, a deep data-science charter locally. Indore has built a services and analytics bench off its IT-park build-out and a cost structure the metros can’t match. Kochi runs on returners and a design-and-product sensibility, with the caveat that its senior pool is thinner and more mobile than the volume numbers suggest.

Get the read right and the charter fits the city; retention then takes care of itself. Get it wrong, drop a data-platform charter where the pool is really engineering-services, and you spend 2 years importing the exact talent the location strategy was meant to avoid, at a relocation premium that erases the cost case you opened the site to capture.

The strongest case for a tier-2 centre is that people stay. In the metros, a mid-level engineer sits within walking distance of a dozen employers who will out-bid you, and attrition runs at levels that make any charter with a long learning curve expensive to maintain. In a tier-2 city with a genuine feeder pool, the competitive set is thinner and the workforce is often there by choice: returners who moved home, engineers anchored to family and a lower cost of living. Attrition falls, tenure lengthens, and the charter compounds.

That compounding is the real asset. Delivery work, platform ownership, long-cycle operations, anything where the value comes from people who have held the same system for years, is exactly what a low-attrition site does better than a metro branch ever will. You’re buying institutional memory that doesn’t walk out the door every 18 months, and in a market where replacing a mid-level engineer can cost most of a year’s salary once ramp and lost context are counted, that memory pays for itself quietly.

So the first design question for a tier-2 site is which charters reward tenure. Point those charters at the city and staff them deep. The mistake is to treat the low attrition as a happy accident when it’s the whole reason the site exists.

The same thinness that makes a tier-2 pool loyal makes it hard to grow leadership inside. A strong director-level pool in Coimbatore or Kochi is small, and the few people in it are mobile, courted back to the metros the moment the title or the scope stops growing. When a delivery lead is ready for a VP charter that the site can’t offer, they leave, and they leave for the exact hub the location strategy was built to step around.

This is a structural feature of a shallow senior market that trying harder won’t fix, and the centres that do well name it early. They run the tier-2 site as the place where delivery leadership is deep and reliable, and they locate the layer above, the P&L owners, the function heads, the principal specialists, where a dense senior market and a peer network actually exist. Sometimes that means a metro anchor with tier-2 delivery spokes. Sometimes it means importing a small senior layer and being clear it’s imported.

The failure mode is the site that quietly promises a leadership path it can’t honour. Staff grow into the ceiling, hit it, and read the gap before you do, and the loyalty that was the site’s whole advantage turns into a stream of your best people leaving at exactly the seniority you most needed to keep.

The test is whether the role can be hired and grown from a local feeder pool, or whether it needs a dense external market to exist at all. Ask it charter by charter. Does the city’s institutional and industry base actually produce this skill, or would you be importing every hire? Does the work grow inside the site, or does the person need a peer layer and an external market to be promoted into? And is the value of the role tied to tenure, which the city rewards, or to scarce specialism, which it can’t supply?

Where the answers point to charter-bound delivery, platform and operations work with a real local feeder, relocate it and staff it deep, that’s where the retention advantage does its work. Where they point to scarce specialists or senior leadership that a thin local market can neither supply nor promote, keep the role in a hub and stop pretending the tier-2 site can hold it. Two roles that look equally “relocatable” on a headcount plan can belong to completely different location decisions, and the feeder-pool read, not the title, is where you find out which.