Does your company have a front-end developer over 35?

[Image]

Last Friday during team building, when the department dinner chat turned to age, I suddenly got curious and opened Feishu's org chart, going through our entire front-end department headcount.

Including me, our department has 38 people. I counted one by one. Those over 35, including myself, only 2 😢.

The other one is a senior on our team who switched from testing to front-end. He's 37 and just moved to writing Vue from a testing role last year. As an internal veteran, he survived on his deep familiarity with the business.

The remaining 36 are all post-95s, and several are post-00s. The youngest intern was born in 2004. When I saw his birth year on his badge, I froze for a while.

That meal didn't taste good. I suddenly realized: In this department, I am by any absolute definition an old-timer 🤔.

---

Where do front-end developers over 35 actually go?

I thought about this question seriously afterward and privately asked many peer friends.

The answer isn't that complicated.

Moved into management

This is the most mainstream path. A front-end developer around 35, if still writing code on the front line, is likely to be repeatedly hinted by HR and bosses: isn't it time to lead a team? Whether you're willing or not, the company's promotion system is designed that way—the technical track caps out at a certain level. To keep raising salary, you either switch to management or take the expert route.

But to be honest, the so-called technical expert track in most domestic companies is just a Title change. The actual work stays the same as before, even more awkward—you have neither management power nor decision-making power. You're just a high-level cog stamped with a senior title.

So many people are forced to choose management. After leading a team, you write less and less code, and your technical feel gradually erodes. Three years later, you look back and find you no longer dare to interview for pure technical roles 😖.

Got optimized

This phrase is overused in China's internet industry, but it is indeed one of the most real destinations.

For many companies' HR systems, 35 is an invisible red line. It's not that you get fired the moment you turn 35, but once organizational adjustments, business contraction, or a new leader who wants their own people come along, those over 35 are always the first batch put on the list.

The reason is simple: expensive!

A front-end developer with ten years of experience might earn monthly 30K to 45K. For the same work, you can hire two juniors with three years of experience, both post-95s, each at 18K, totaling 36K—cheaper than you, more obedient, and willing to work overtime. From a pure cost perspective, it's an easy calculation.

You can call it unfair. But the business world doesn't talk fairness; it talks ROI🤷‍♂️.

Changed careers

In recent years, I've observed far more front-end peers switching careers than I expected.

Some became product managers, some moved to operations, some went back home to prepare for civil service exams. One former teammate in our group now runs a milk tea shop in his hometown. Last time I passed by his Moments, he was seriously studying new product recipes, with the same focus he once applied to tweaking CSS animations.

Some also went into technical training. I won't elaborate on that; those who know, know🤔.

"Run" (emigrated)

Some went to Singapore, Japan, Canada, Europe. Not everyone can take this path—it requires language, education, and visa conditions to align. But a certain group chose this, leaving behind China's internet 996 and age anxiety.

Are they doing well? To be honest, each has their own hardships, but at least they don't worry about being optimized because of age.

---

Why is age anxiety especially severe in the front-end role?

If you look at back-end, algorithm, and even operations, the proportion of people over 35 is notably higher. The age gap in the front-end circle is particularly obvious. This is not accidental.

Front-end technology iterates too fast, but its perceived business value is too weak

Over the past decade, front-end has gone through violent changes: jQuery → Angular → React → Vue → Next.js → AI-assisted generation. Every two or three years, there's a new wave of frameworks, tools, and paradigms to learn.

But the problem is, no matter what new thing you learn, in the boss's eyes, all you do is draw pages😖.

When back-end builds a high-availability architecture, the boss directly sees system stability improved and failures reduced. When algorithms optimize a recommendation model, the boss directly sees click-through rates rise by 2 percentage points.

But you use React Server Components to optimize first-screen LCP from 3 seconds to 1.2 seconds? The boss's reaction is likely: "Well, the page is a bit faster, that's nice." Then continue discussing the next requirement.

This severe misalignment between technical investment and business perception naturally gives front-end lower bargaining power within the company. As age rises and cost-effectiveness drops, front-end becomes the first target for optimization.

Front-end's entry barrier is too low

Many old-timers are unwilling to admit this, but it's true.

A zero-foundation graduate can train for three months and build an admin system with Vue + Element Plus. A product manager switching careers can learn React for half a year and compete for the same role.

This is unlikely in back-end or algorithm. You can't train for three months and write distributed transactions, nor can you self-study for half a year and tune large models.

Low barrier means high supply, high supply means high replaceability, high replaceability means no pricing premium when you age. That's the cruel market logic 🤷‍♂️.

---

How do those 35+ front-end developers still writing front-line code survive?

I specifically went out to investigate, finding seven or eight front-end friends over 35 who are still coding on the front line.

They have a few common traits.

All are bound to a sufficiently deep technical direction

Nobody is a jack-of-all-trades. One works on low-code engines, one on cross-end rendering, one on WebGL visualization, and another on front-end infrastructure and tooling.

They aren't all-rounder players, but in their own domain, no one in the company can replace them. This irreplaceability is the real moat.

If you go to an interview and say you can use React, Vue, TypeScript, the interviewer won't think you're valuable. But if you say you built a visual BI system from scratch and handled Canvas rendering performance issues for millions of data points, that's different.

All understand the business deeper than product managers

One friend works in cross-border e-commerce. His understanding of Shopify's Liquid template engine, Checkout Extensibility, and Storefront API is even deeper than their company's product manager. The boss won't cut him because if he's let go, no one can hold up that business.

All aren't that anxious

This was quite unexpected. I thought they'd be anxious, but it turned out that the truly anxious ones are those around 28 or 29, near the 30-year threshold.

Those over 35 who remain on the front line have mostly figured it out: anxiety is useless. The market won't give you an extra Offer because you're anxious. What you can do is to do your current work solidly, keep learning, and accept the rules of the industry.

A friend told me a line I remember deeply: Your anxiety is not about age at its core; it's that at 35, you're still holding the skills you had at 25🫡.

---

What I'm thinking myself

Having talked about others, let me talk about myself.

I'm also approaching this line. It's false to say I'm not anxious.

Sometimes I think, if I got optimized one day, where could I go? If my resume lists a bunch of React, Vue, Webpack, Vite, how is that essentially different from a fresh graduate's resume? Why would an interviewer pay me 40K instead of a young person asking for 18K?

But overthinking doesn't help.

Last year I went deep into Cloudflare Workers and edge computing; this year I'm tackling front-end engineering for AI Agent. I dare not say these will keep me from being optimized, but at least they add something new to my resume each year.

Also, I write articles. Not for traffic, but to force myself to systematize what I've learned. You think you know something, but when you write it out, you discover holes everywhere. Writing is the best self-audit tool.

---

I don't want to serve chicken soup here, saying that as long as you work hard you won't be eliminated. That's a lie.

The reality of this industry is: It is not friendly to age, especially not to front-end. Front-end developers over 35 are rare; most are already thrown out by the industry's screening mechanism at some point between 30 and 35.

What you can do is not fight the rules, but before the rules throw you out, gather more trump cards for yourself.

Whether it's going deep into a niche technical direction, binding to a high-value business domain, building your own technical influence, or simply preparing a Plan B—anything works.

The worst is doing nothing, writing CRUD at work every day, scrolling short videos after work, and then suddenly panicking on your 35th birthday 😢.

How many front-end developers over 35 are there in your department? How are they doing now?

---

If you like my articles, you're also welcome to follow my WeChat public account: 【前端技术官】.

Main topics: Frontend Architecture · AI Programming · Workplace Cognition · Developer Growth

[Image]

Scan with WeChat to follow 👆

Irregular updates, no spam, talk about genuinely useful stuff.