How to Build a High‑Performing Tech Team: Recruitment, Goals, Communication, and Culture

Introduction

As a technical team leader (TL) at Alibaba, I face not only technical challenges but also many management difficulties. This article summarizes my reflections on recruitment, goal management, team communication, and engineering culture, offering concrete methods and recommending several books that have shaped my thinking.

1. Recruitment

The primary principle is "better not to hire than to hire the wrong person." Short‑term pressure often leads to compromising this rule, which can dramatically increase the TL's management burden and harm team morale.

When interviewing, I focus on five indispensable qualities:

Coding ability

Passion for technology

Clear and concise communication

Positive attitude

Alignment with team goals

Recruiting is a long‑term effort; maintaining contact with promising candidates builds trust and makes the team an attractive option when opportunities arise. A TL should also demonstrate technical influence through open‑source contributions, articles, or conference talks.

2. Goal Setting

Team cohesion depends on shared objectives, which the TL defines and clarifies. I favor the OKR (Objectives and Key Results) framework to align direction and quantify progress, but I caution against using KR numbers as the sole performance metric because they can encourage short‑sighted behavior.

Defining goals requires answering several questions:

Do we fully understand our users' real needs and the problems we solve for them?

What dependencies exist with upstream/downstream partners, and do they share our goals?

Are the team’s objectives consistent with the TL’s personal goals and the department’s targets?

Does the goal consider the team’s technical competitiveness?

Clear goals must be communicated repeatedly so every member knows exactly what to achieve.

3. Communication

When a team member reaches out, respond immediately—whether that means a real‑time chat, an evening conversation, or scheduling a meeting for the next day. Prompt responses build trust; delayed replies erode it and can lead to disengagement.

Regular 1‑on‑1 meetings are essential. In my experience, a monthly cadence works well for a TL who also carries technical responsibilities. During 1‑on‑1s, give specific feedback such as:

“Your design for X solution nicely considers cross‑team collaboration.”

“Your recent code needs better unit‑test coverage.”

“I notice Y project is lagging; what obstacles are you facing and how can I help?”

Equally important is listening—understanding a teammate’s emotional state and challenges, even if you cannot solve the problem immediately.

4. Engineering Culture

A strong engineering culture respects the quality of code, tests, design, and product output. It attracts talented engineers and prevents the team from devolving into a “brick‑moving” operation.

Key practices include encouraging code reviews, writing unit tests, maintaining CI pipelines, and sharing knowledge. Even under heavy project pressure, a TL should allocate time for paying down technical debt and acknowledge its existence.

5. TL Advice to Self

Be authentic – stay true to your personality and values.

Don’t panic – manage stress calmly to avoid spreading anxiety.

Be patient – behavioral change takes time; repeat important messages and give teammates space to grow.

6. Further Reading

“Your problem mainly lies in reading too little while thinking too much.” – Yang Jiang

Recommended books:

《赢》

《如何定义公司》 – “Talent is crucial.”

《驱动力》 – “Beyond money, how to motivate people.”

《门后的秘密》 – “Why 1‑on‑1 communication matters and how to do it well.”

《非暴力沟通》 – “Everyone can speak, but few can speak well and listen actively.”