跪拜 Guibai
← All articles
Front-end · Full-stack · AI Programming

Full-Stack Squeeze: Front-End Isn't Dying, But the Pure Page-Writer Role Is

By 挖掘狂人 ·
Read original on juejin.cn ↗ Google Translate ↗ Alt translation

The choice for front-end developers is no longer front-end versus full-stack but whether to deepen judgment in a niche like accessibility or performance, or to become an AI-assisted generalist. Either way, the page-writing executor version of the job is being automated out.

Summary

Front-end hiring has changed: senior role descriptions routinely ask for Node.js, Serverless, or full-stack experience, and organizations are merging the two disciplines. AI tools now produce components, layouts, and styles in minutes, compressing what used to take three or four people into one person plus a toolset. The squeeze lands hardest on junior developers whose work is exactly what AI automates best.

The response to this pressure reorders what a front-end developer should learn. Syntax, framework APIs, ORMs, and routine CRUD are things AI delivers instantly, so they are lower priority. The valuable skills are data modeling, API design, authentication, SQL and migrations, then concurrency and idempotency, deployment, observability, and security. The argument is that judgment, not code volume, is what survives both AI and role consolidation. A veteran front-end's warning makes the same point from the other side: full-stack generalists often deliver 'just works' products at the cost of accessibility, performance, and user experience, and that cost is paid by users.

Takeaways
— Meituan CLC merged front-end and back-end teams, JD Retail cut independent front-end headcount on one business line, ByteDance is hiring AI full-stack engineers, and Tencent shifted front-end roles toward agent engineering platforms.
— AI tools generate components, layouts, and styles down to minute-level speed, so one developer plus AI can support a page layer that previously took three or four people.
— Four front-end directions gain value under full-stack pressure: deep interaction and a11y, AI-native front-end (Agentic UI, multimodal, on-device), front-end infrastructure, and server-first mastery of frameworks like Next.js or Remix.
— A full-stack veteran's account warns that full-stack thinking turns a 90-point front-end expert into a passing both-ends implementer who drops virtual scrolling, lazy loading, skeleton screens, and aria attributes.
— Learning priority has three tiers: skip syntax/framework/CRUD (AI provides it), own data modeling/API design/auth/SQL/migrations (AI will make mistakes where constraints are unspecified), and carry concurrency/idempotency/deployment/observability/security (AI writes it but won't take the fall).
— The recommended timeline is 3-6 months to gain fluency with Cursor or Claude Code, 6-18 months to fill full-stack gaps focused on the second and third tiers, and long-term to pick 1-2 moat directions like edge AI, complex interaction, or WebGPU.
Conclusions

The article reframes the front-end crisis as a shift from output to judgment: what cannot be automated is the accumulated expertise in a11y, performance, and design-system decisions.

The full-stack generalist's warning exposes a real trade-off: merging roles can degrade user experience because the 'good enough' mindset skips the polish that domain experts would insist on.

The recommendation to avoid learning backend languages first is counterintuitive but consistent with the AI reality, yet it assumes a developer can articulate the constraints AI doesn't know to ask for.

The framing that 'the job isn't dying, only the execution layer is' implies a confident bet that org structures will keep rewarding depth; that may hold in the short term, but the article itself shows companies merging roles regardless.

Concepts & terms
Agentic UI
Interfaces that are driven by AI agents, often generated or adapted from prompts in real time, rather than being hand-coded page by page. Includes multi-modal interaction and on-device intelligence.
Server-first
An architecture pattern where front-end frameworks like Next.js or Remix handle data fetching, caching, and authorization on the server, pulling backend concerns into the front-end developer's remit.
BFF (Backend for Frontend)
A dedicated backend layer that serves a specific front-end client, shaping APIs for that client's needs rather than exposing a general-purpose backend.
Source: juejin.cn ↗ Google Translate ↗ Backup ↗