Is ageism really a problem in Indian tech, or is it overstated?

It's real and measurable, though it manifests differently than in some other industries. Indian IT services companies have historically favored younger, lower-cost talent pyramids, and layoffs during downturns have disproportionately affected engineers in their late 30s and 40s who sit at higher salary bands without commensurately higher seniority or scarce skills. The risk is highest for engineers who stayed in narrow, individual-contributor roles without growing into scarce technical depth, leadership, or business-facing skills over a long tenure.

What's the biggest mistake engineers make that makes them vulnerable to ageism in their late 30s?

Staying technically stagnant while salary keeps climbing — i.e., still working with the same stack and at the same scope of ownership as 5–10 years ago, but now expensive relative to a fresher who can do the same narrow task. The fix is continuously growing scope (system design, mentoring, cross-team ownership) or depth (genuine expertise in a scarce area) so your value clearly outpaces your cost, not just your tenure.

What career paths are safest for software engineers over 40 in India?

Staff/Principal IC roles with genuinely scarce technical depth, engineering management (where experience is a direct asset, not a liability), solutions architecture and consulting (where domain experience and client trust matter more than raw coding speed), and specialized niches with high learning curves (security, distributed systems, ML infra) where fewer engineers compete for the scarce expertise. The common thread: roles where your years of experience are the differentiator, not a cost line.

Ageism in Tech India: 35+ Engineer Survival Guide 2026

Why "Ageism" in Tech Is Really a Value-vs-Cost Problem

Globally, tech workers report facing age-related hiring friction starting as early as their late 20s, a decade earlier than most other industries — and India's IT services-heavy market amplifies this because of its historical preference for large, young, lower-cost engineering pyramids. Layoffs during downturns disproportionately hit engineers in their late 30s and 40s sitting at higher salary bands.

The uncomfortable truth: this usually isn't pure prejudice against age — it's a cost-vs-value calculation. An engineer who's been doing the same scope of work for a decade, at a salary that's climbed with tenure but whose actual value (scarce skills, leadership, ownership) hasn't grown proportionally, becomes an easy line item to cut. The fix is making your value visibly outpace your cost, every year, not just hoping tenure protects you.

Age tech workers report ageism starting (global data)

52% / 30%

Women / men reporting workplace ageism in India

2 paths

Depth or scope — pick one and grow it

⚠️

The trap: Staying technically stagnant — same stack, same scope of ownership as 5–10 years ago — while your CTC keeps climbing with annual hikes. You become expensive relative to a fresher who can do the same narrow task, which is exactly the profile most vulnerable in a layoff.

The Four Defensible Career Positions After 35

Position 1

Genuine Technical Depth

Become the go-to expert in something scarce and hard to replace fast — distributed systems internals, a critical legacy system only you understand deeply, security, or ML infrastructure. Depth that takes years to build is depth that takes years to replace.

Position 2

Engineering Management

People leadership, hiring judgment, and organizational navigation are skills where experience is a direct asset, not a cost. EM roles value tenure in a way pure IC roles increasingly don't at the mid-level.

Position 3

Architecture & Client-Facing Roles

Solutions architecture, technical consulting, and pre-sales roles value domain experience and stakeholder trust over raw coding speed — exactly the strengths a 15-year career builds.

Position 4

Staff/Principal IC With Visible Scope

If you stay IC, your scope must visibly grow — owning system-wide architecture decisions, mentoring, and cross-team technical direction — not just "still writing the same kind of code, but for longer."

Concrete Actions to Take Starting Now

Audit your last 2 years honestly: Did your scope of ownership or technical depth meaningfully grow, or did your salary simply climb on autopilot? If it's the latter, that's the gap to close immediately.
Build one scarce, hard-to-replace skill deliberately: Pick a domain (security, infra, a specific scale problem) and go deep enough that you're the person people seek out — not just competent, but the reference point.
Stay visibly current: Ship something with modern tooling (even a side project) every year. The fastest way to look "outdated" is to stop publicly demonstrating you can learn new things.
Build a network beyond your current company: Referrals are the fastest path back into work after a layoff at any age, but especially past 35 when cold applications get filtered harder by automated screens. Stay active in your professional network continuously, not just when job-hunting.
Know your real market value: Benchmark your CTC against current market rates for your actual scope (not just your title) every year — if you're significantly above market for your demonstrated scope, that's a risk signal worth addressing proactively.

If You're Already Laid Off at 35+

Reframe Your Pitch Around Judgment, Not Just Code Speed

Lead interview narratives with decisions you made under ambiguity, trade-offs you navigated, and mistakes you caught early because of experience — this is the differentiator a 25-year-old candidate genuinely can't match, and it's what should anchor your pitch instead of competing on raw LeetCode speed.

Target Roles That Explicitly Value Tenure

Solutions architecture, engineering management, technical consulting/pre-sales, and Staff+ IC roles at companies with mature leveling. Avoid roles explicitly seeking "early-career, high energy" framing in the JD — that's often a soft signal about expected profile.

Use Your Network Before Job Boards

Reach out directly to former colleagues, managers, and your professional network for referrals and warm introductions — this consistently outperforms cold applications, and is even more critical when competing against larger applicant pools at your experience level.

Frequently Asked Questions

Should I hide my age or years of experience on my resume?▾

Don't hide your total experience, but you can de-emphasize it strategically: lead with your most recent and most relevant 10–12 years of experience in detail, and summarize earlier roles briefly rather than listing decades of granular history. Drop graduation years if they're decades old and not relevant to the role. The goal is to keep the resume focused on current relevance, not to misrepresent your background.

Is switching to management the only safe path after 40 in Indian tech?▾

No — it's one strong option, but Staff/Principal IC roles, solutions architecture, and specialized technical consulting are equally defensible if you build genuine, hard-to-replace depth. Management isn't a universal safety net either: poor people-management skills or disinterest in the work will show up quickly and create its own risk. Choose based on genuine strength and interest, not just as a panic move away from coding.

How do I compete with cheaper, younger candidates in interviews?▾

Don't try to win on the same axis (raw coding speed, willingness to work the same hours for less pay) — reframe the comparison entirely around judgment, system-level thinking, and the cost of mistakes you'd prevent that a less experienced hire wouldn't catch. In system design and behavioral rounds, this is your structural advantage; make sure your answers actively demonstrate it rather than just answering the question asked.

Pranjal Jain

Ex-Microsoft SDE · IIT Kanpur · Founder of Prepflix. Helps engineers crack startup and product company interviews across India.