How to Build a Thriving Engineer Culture: Practical Steps from Alibaba’s Hema Team

Preface

Many companies claim to value engineer culture, yet most teams struggle to define or experience it. The author, a senior technical expert from Hema, shares practical insights to help readers understand and build a healthy engineer culture.

Engineer Culture vs KPI Culture

Engineer culture emerges from within and happens naturally, while KPI culture is imposed from outside .

Engineer culture looks to the future; KPI culture focuses on short‑term metrics.

Engineer culture pursues what engineers love; KPI culture forces work regardless of passion.

Key Prerequisites for Engineer Culture

Trust : Leaders and product teams must fully trust engineers’ technical decisions, even if they require more time.

Technical Leadership : Leaders who value technology as more than a tool foster a culture that appreciates elegant code and long‑term impact.

Technology as a KPI : When technical quality is not a KPI, it is often deprioritized; making it a KPI ensures it receives proper attention.

Characteristics of Engineer Culture

Small teams (7‑12 people) enable fast iteration and high impact.

Principles such as “Move Fast and Break Things”, “Huge Impact with Small Teams”, and “Be Bold and Innovative”.

Technical innovation is encouraged; engineers are expected to challenge product assumptions with better solutions.

Decision‑making power is given to engineers for architecture and prioritization.

Technical data (complexity, coverage, duplication) is visualized and celebrated, though not monetized.

Meetings are minimized in favor of knowledge sharing and deep technical discussions.

Agile Perspective

Agile is presented as a metaphor for tall‑girl stories, emphasizing the importance of belief and continuous improvement rather than strict methodology.

Practical Practices from Hema’s Basic Technology Team

Design

Good code reflects thoughtful design; the team uses a custom domain‑model design pattern that encourages deliberate architectural decisions, supported by comprehensive automated tests.

Automated Testing

All tests must pass before code submission; each test corresponds to at least one assertion.

Use given/when/then style for unit tests.

Separate business logic from database access to simplify testing.

Apply mock/stub techniques effectively.

Avoid sleep in asynchronous tests.

Testing is the primary debugging tool.

Prefer fast unit tests over costly integration tests.

Static code analysis should run on every CI build.

Continuous Integration / Continuous Delivery

CI continuously compiles, packages, deploys, and runs tests, providing immediate feedback on code quality.

Short‑duration tests run on every push; longer tests run less frequently.

Compile once, deploy multiple times during CD.

“Check in and play” vs. “Check in and pray”: frequent commits with feedback enable rapid iteration.

Fix CI failures immediately; keep the dashboard green.

Goal: achieve continuous delivery.

Keep branch count low to maintain CI effectiveness.

Branch Strategy

The team uses a single large repository with minimal branches; excessive branching increases merge cost and reduces CI value.

Pair Programming

Two developers share one workstation.

Pairing accelerates onboarding of new engineers.

It spreads best coding practices and creates a unified team style.

Occasional pairing boosts learning enthusiasm without hurting productivity.

Code Review

Team code reviews last about an hour.

Daily code reviews are encouraged.

Every engineer’s code is reviewed and explained.

Issues are fixed on the same day.

Stand‑up Meetings

Limit to 15 minutes.

One person speaks at a time.

Cover yesterday’s work, today’s plan, and needed help.

Technical Sessions

Technical sessions focus on deepening engineers’ knowledge, even when not directly tied to business features.

Retrospective

Review the past iteration’s successes and failures, then plan improvements for the next cycle.

IPM Iteration Planning

Teams use IPM meetings to align on upcoming two‑week goals, responsibilities, and timelines.

IDE Practices

Choosing the right IDE (e.g., IntelliJ) and sharing shortcuts across the team significantly improves coding efficiency.

What unique experiences do you have with engineer culture? Share your thoughts in the comments.