Ageism in Indian Tech After 35: The Honest Truth for 2026

Ageism in Indian tech is one of the most talked-about, least-analyzed anxieties in our industry. Every senior engineer in India I know — myself included — has had at least one late-night moment of *”is this really over for me at 40?”* Every Quora thread and Blind post feeds the fear. Almost nothing you read online tells you what’s actually happening in the market.

I’ve spent the last several months watching this pattern from close range. Reading the research. Talking to friends and colleagues in their late 30s and 40s. Sitting in interviews myself. And what I’ve come to believe — the sharp claim this whole post is built around — is uncomfortable but honest:

That single sentence, if it’s right, changes almost everything about how you should think about your career after 35 in Indian tech. It shifts the conversation from *”how do I survive ageism”* to *”am I in the right tier of the market, and if not, how do I move.”* That’s a completely different problem — and a much more solvable one.

The rest of this guide is my honest working-through of that claim: where the evidence supports it, where the exceptions live, what the tier breakdown actually looks like in 2026, and what you can do — starting this quarter — to make sure the 35-cliff conversation is never about you.

This is a longer guide on ageism in Indian tech — about 25 minutes end-to-end. If you’re pressed for time, read the tier breakdown section first, then the 5 factors. Those two sections carry most of the practical value. The rest is context and evidence.

Why the Ageism in Indian Tech Conversation Gets Distorted

Before the sharp claim, one important calibration. Ageism in Indian tech gets discussed in a really specific way online — and the shape of that discussion distorts the actual signal. Three patterns show up in almost every conversation.

1. The Quora/Blind amplification loop

Most of what you read about ageism in Indian tech comes from Quora threads, Blind posts, and Reddit discussions. These platforms select heavily for the worst outcomes — the engineers who lost their jobs, couldn’t find another one, and are angry enough to post about it. That’s a legitimate voice to hear. But it’s not a representative sample.

The engineers who navigated 35+ successfully aren’t writing 800-word laments about ageism on Blind. They’re at work. The signal you see online is skewed toward crisis. The actual industry-wide pattern is more nuanced.

2. The “just upskill” reflex

Every mainstream article on ageism in Indian tech resolves into the same advice: *”stay relevant, keep learning, upskill in AI/cloud/whatever’s hot.”* This isn’t wrong. But it’s dramatically insufficient — because it treats age discrimination as a personal-development problem when the pattern is often structural. Even McKinsey’s own workforce research consistently distinguishes between skill-adjacency problems (fixable individually) and structural labor market shifts (which require repositioning, not just upskilling) — and ageism in Indian tech sits mostly in the second category.

“Upskill more” is what you tell someone who is failing on their own merits. That’s often not what’s happening. What’s happening is that a specific tier of the Indian tech market has structural incentives that push out senior engineers, and no amount of individual upskilling changes that structural pressure. Naming the structure first, individual response second, is the only honest sequence.

3. The comparison to the West and China

You’ll see comparisons to the US (where ageism is real but different) and China (where the 35-cliff is famously more severe than India’s). These comparisons are used mostly to make readers feel better — “at least it’s not as bad as X.” They don’t actually help you understand what’s happening in Bangalore or Hyderabad or Pune. The Indian tech market has its own specific pathologies, and the solution has to be Indian-specific.

The Tier Breakdown — Where Ageism Actually Lives

Here’s the argument the whole post rests on: ageism in Indian tech is not evenly distributed across the industry. It’s heavily concentrated in one tier of the market, present but manageable in another, and largely absent in a third. Once you see the tiers clearly, the fear stops feeling like a career-ending force and starts looking like a positioning problem you can solve.

What “Ageism” Often Actually Is

Now the uncomfortable second layer. Even inside the tiers where ageism in Indian tech is genuinely real, a significant portion of what gets called “ageism” is actually one of three other problems in disguise. Naming them separately matters because they have completely different fixes.

1. Skill obsolescence disguised as age discrimination

The most common one. A 40-year-old engineer who last learned something new in 2018 is not being discriminated against for age — they’re being passed over for skill relevance. The signal reads as “he’s too old for us” but the underlying pattern is “his skills haven’t kept up with what we hire for.”

Here’s the honest test: what did you learn in the last 12 months that you didn’t know before? If the answer is “nothing substantive,” the ageism you’re worried about might actually be skill drift. That’s a much more fixable problem — but only if you diagnose it correctly.

2. Cost anchoring — “we can hire two juniors for what you cost”

This one is real, and it hurts. If your compensation has grown 8-10% annually for 12-15 years, you might now cost 3-4x what a fresh mid-level engineer costs. In roles where a 40-year-old adds 4x the value of a mid-level engineer, this doesn’t matter. In roles where the value ratio is closer to 1:1 or 2:1, cost anchoring becomes the real conversation — even if it never gets said out loud.

This is one of the reasons the tier breakdown matters. In IT services, the value ratio is often 1:1 or worse (juniors can be trained to close tickets almost as well as seniors). In product companies, the value ratio is often 4:1 or better (senior ICs can architect systems juniors can’t).

3. Positioning mismatch — the résumé doesn’t tell a specialist story

The generic senior engineer résumé is easy to reject at 40 in a way it isn’t at 30. When you’re 30, “8 years of full-stack development across three companies” reads as promising generalist experience. When you’re 40, the same résumé structure reads as “hasn’t specialized enough to be worth senior compensation.”

The fix isn’t to become more junior. It’s to become more specific. A résumé that clearly signals “10 years of Kubernetes-at-scale specialization with three named production migrations” reads completely differently from “senior engineer with cloud experience.” Positioning at 40 has to be sharper than at 30. That’s not ageism — that’s the market working correctly.

The 5 Factors That Correlate With Staying Employed Past 40

Now the constructive half of the post. If ageism in Indian tech is largely a tier-and-positioning problem, then the engineers who navigate it well should show consistent patterns. And they do. Watching peers in their late 30s and 40s across the Indian tech industry for a decade, five factors show up repeatedly in the careers that keep compounding — and their absence shows up repeatedly in the careers that stall. Not scientific. Pattern-recognition from close range.

The Specialist Premium vs the Generalist Squeeze

Of the five factors above, Factor 1 — specialization — deserves its own extended treatment because it’s the single most misunderstood dynamic in the Indian tech senior career market.

The received wisdom for the first 8-10 years of an engineering career is be a generalist, take varied experiences, stay flexible. That’s mostly good advice for the first decade. It becomes actively harmful advice in the second decade.

Here’s why. When a company is hiring a senior engineer at 15+ years experience, they are not hiring for potential — they’re hiring for specific value. And specific value comes from depth in a domain, not breadth across many. A 15-year full-stack generalist competes against 5-year full-stack engineers who cost half as much and have almost as much breadth. A 15-year Kubernetes specialist competes against 8-year Kubernetes engineers who lack the specific scars of running production Kubernetes at scale — and there’s no substitute for those scars. This dynamic is the single biggest reason ageism in Indian tech hits generalists hardest.

The uncomfortable implication: if you’re 12+ years in and you can’t answer the question “what am I specifically known for?” in one crisp sentence, you have a specialization problem, not an age problem. And the fix — deliberately specializing over the next 24 months — is entirely within your control.

What specialization looks like practically:

• Depth over breadth in your next role change. When you switch jobs next, prioritize roles that let you go deeper in your strongest domain over roles that expose you to new domains. Depth compounds. Breadth stops paying dividends after ~10 years.
• External signal of the specialization. GitHub reference implementations, LinkedIn posts, a blog, a conference talk — public evidence that you own a specific domain. This is what makes the specialization discoverable.
• Refuse the “senior generalist” trap. Managers love handing senior generalists whatever work needs doing. It feels flattering. It’s slowly killing your specialist positioning. Learn to say “that’s outside my area — I can help scope it, but you’d get better work from someone in that domain.”

The Tier-Switch Playbook

If the tier breakdown is right, then the highest-leverage move for many senior engineers stuck in IT services is not to fight ageism in Indian tech from inside services — it’s to move tiers. Here’s what that actually takes at 12-18 years experience.

The realistic timeline

Moving from IT services to a product company or greenfield GCC at 12-15 years experience typically takes 6-12 months of deliberate work, not 6-12 weeks. Anyone telling you it takes a couple of months hasn’t done it recently. The work compounds — but it’s real work, sustained.

The four moves that make it possible

When it’s worth doing — and when it isn’t

The tier switch isn’t the right move for everyone. Three questions to be honest with yourself about:

• Do you have 6-12 months of runway (either employed at your current job or with savings) to do the work properly?
• Are you willing to accept a 6-12 month period of lower income and higher stress for a step-change in trajectory?
• Is your current situation actually bad enough to warrant the disruption, or are you catastrophizing based on Blind posts?

If yes on all three, the tier switch is probably the highest-leverage career move you can make. If no on any of them — especially the third — sometimes the honest answer is to stay in your current tier, do the work of specialization in place, and revisit the tier switch decision in 18 months from a stronger position.

My Story — What I’ve Watched Across a Decade

A Word Directly to You

If you’re 35+ in Indian tech and this post has raised your anxiety more than it’s calmed it, take a breath. The situation isn’t as dire as Blind threads suggest. It’s also not as fine as the “just upskill” advice suggests. It’s in the middle — a real, structural, addressable challenge that responds well to deliberate work and badly to panic.

Here’s the honest short version of everything above:

One: Identify which tier you’re currently in. Be honest — services, operational GCC, greenfield GCC, or product. That’s the single biggest factor in your ageism exposure. If you’re in the wrong tier for your career stage, that’s the highest-leverage thing to work on.

Two: Diagnose whether what you’re calling “ageism” might partly be skill obsolescence, cost anchoring, or positioning mismatch. Those are individually more fixable than the giant undifferentiated fear.

Three: Pick one specialization to lean into over the next 24 months. Not five. One. Depth compounds. Breadth stops paying past year 10.

Four: Build public evidence — GitHub, LinkedIn, maybe a blog — that lets a hiring manager verify your specific work exists outside your employer’s walls.

Five: Cultivate a network of 20-30 people in the tier you want to be in. Not networking events. Real relationships, sustained over years.

Do these five things starting this quarter and the ageism conversation stops being about you three years from now. It doesn’t mean ageism in Indian tech disappears from the industry — it doesn’t. It means you become the engineer that ageism doesn’t apply to, because you’ve done the specific work that makes age irrelevant to your value.

That’s the honest answer. And it’s the one I’m working on in my own career, right now, at exactly the age this post is about.

This Post Is Not the End of the Discussion

One last thing, and I want to say this clearly. This post is not the last word on ageism in Indian tech. It’s my current best working theory, built from a few months of research and a decade of watching peers. It’s meant to start a discussion, not close one.

I’m openly rooting for two kinds of conversations from this piece.

From peers — engineers in their late 30s and 40s who are living this pattern in real time. Does the tier breakdown match what you’ve seen? Where would you push back? What have I missed? The comments and DMs from readers like you are the fastest way this framework gets sharper.

From seniors — engineers with 20+ years in Indian tech who’ve watched multiple cycles of this. You’ve seen the pattern longer than I have. Your corrections and additions matter more than mine. If you disagree with the tier framework, tell me why. If you’d add a factor I missed, share it. If your career has taken a shape my framework doesn’t explain, I want to hear about it — because that’s exactly the signal I’m calibrating against.

This is an open topic. I’m not the expert on it — I’m a peer trying to figure it out out loud, hoping the figuring-out is more useful shared than kept private. If this post helps someone in your network navigate their own next five years better, share it. If you have a sharper reading than mine, publish yours — the industry needs more honest writing on ageism in Indian tech, from more voices, not less.

Rooting for all of you.

— Arvind