What Front‑End Engineers Must Know About Career Growth and Team Management

Winter is a legendary front‑end engineer known for his JavaScript expertise and the Weex framework; his birthday, October 24, coincides with "Programmer Day" (1024 = 2^10).

He began programming with machine code on punched cards, graduated from Harbin Engineering University, worked at Microsoft Research Asia, and later joined Alibaba as one of the youngest P8 engineers.

The conversation was recorded in 2020 after Winter left a large tech company.

All difficulties are engineering problems

Q: What does front‑end mean in the programmer world? Winter: Front‑end, or Web front‑end engineering, refers to the code that runs in browsers, while the server side runs on the backend. A front‑end engineer writes the client‑side code.

He notes that front‑end work varies by product type: e‑commerce front‑ends have simpler logic (e.g., clicking to navigate), whereas education products involve more complex interactions.

When asked about the hardest part of e‑commerce front‑end, Winter says the challenge lies in the sheer volume of work, which brings quality and efficiency issues, and that engineers must improve key metrics such as conversion rate, transaction volume, and average order value. He also mentions using 3D technology in Taobao to aid purchase decisions.

Winter emphasizes that as teams grow, engineering problems become non‑linear; coordinating many engineers requires new knowledge and processes, and the difficulty of maintaining speed and quality increases dramatically.

Programmer growth ladder

Winter describes the career stages: assistant engineer (good fundamentals but no project experience), entry‑level engineer (can deliver features and communicate with designers, backend, and product), senior engineer (technical backbone, may specialize in business or coordination), domain expert (authoritative in a specific area), and leader (responsible for tooling, hiring, team direction, and strategic decisions).

He stresses that leadership brings pressure, as decisions affect many people and can lead to dead‑ends if mis‑guided.

Managing programmers is about trust

Winter argues that many programmers work best in a "flow" state and that interruptions break productivity. He suggests hiring people you trust not to "water‑down" work, and that management should focus on outcomes rather than micromanaging.

The interview also touches on the controversial "996" work schedule, with Winter expressing opposition to forced overtime and highlighting the difference between voluntary extra work and mandatory long hours.

Personal planning and value

Winter explains that big‑company experience taught him to view work from a team perspective and gave him deep commercial insight. He believes that after gaining skills, one should pursue personal value, experiment, and accept failure as self‑knowledge.

He advises setting a personal goal (e.g., five years) and, if unmet, acknowledging limits while still gaining growth.

How to do what you truly want

What is the thing you truly want to do?

How to confirm it’s what you want?

How to start doing it?

How to balance income and passion?

What mindset should you have?

These questions summarize the core theme of the interview: aligning career choices with personal aspirations.