From Rookie to Front‑End Leader: Lessons from 9 Years at Alibaba

Introduction

Technical life is a continuous practice; the author shares his nine‑year journey at Alibaba, highlighting lessons learned.

Early career and first front‑end exposure

Born in a culturally rich family, he discovered computers and the internet, graduated in 2004, joined COSCO, encountered front‑end work, and quickly built a professional value system.

Second wave and startup

In 2007 he joined a Web 2.0 startup, gaining knowledge in technology, design, product and user experience.

Joining Alibaba and four stations

In 2008 he entered Alibaba as a front‑end engineer. Over nine years he worked in four key stages:

UED team front‑end engineer – focus on performance and experience optimization.

UED front‑end team leader – built the AliExpress startup team and integrated front‑end into the technical team.

Front‑end leader of Alibaba B2B enterprise group – integrated multiple front‑end teams and defined architecture.

Leader of B‑class e‑commerce experience technology platform – built a middle‑platform, emphasizing convergence, flexibility and scalability.

Front‑end architecture evolution in B‑class e‑commerce

The evolution is described in three stages:

“Information exposure, meeting” – keywords: inheritance‑based code reuse, load‑time performance governance.

“Online transaction” – keywords: modular management, front‑back separation, execution‑time performance governance.

Platformization – keywords: design deconstruction, logical scheduling, application model, layered standardization.

Layered architecture principles

Purpose of layering: decouple front‑end and back‑end development and reduce complexity per layer, yielding parallel development, flexibility, stability, and performance monitoring.

General principles: each layer provides independent functionality, can evolve and be tested independently; dependencies only on the same or lower layers; interface definition separated from implementation.

Internationalization challenges

Front‑end must handle global deployment, content internationalization, and localization, including CDN pre‑heating, cache versioning, multi‑language resource management, and right‑to‑left scripts.

Team management insights

Discusses pros and cons of consolidating front‑end into a single team versus dispersing across business units, considering professional development, perspective, and organizational flexibility.

Future directions: “Cloud” and “End”

Explains “end” as delivering UI across devices, and “cloud” as providing foundational development capabilities and services for front‑end developers.

Advice for front‑end engineers

Recommends cultivating critical thinking, openness, and curiosity; staying aware of language and tool evolution; focusing on problem‑solving rather than tool obsession; and maintaining continuous self‑reflection.