Building an Engineer Culture: Values, Infrastructure, and Incentives at Snowball

Values

Snowball believes that a technology company's engineering team must have its own culture, centered on the pursuit of excellence. The key aspects are correct values, solid infrastructure, and appropriate punishment and incentives.

Why Values Matter

Values are shared viewpoints on specific matters; when a team aligns on values, members can understand each other's actions, communicate easily, and resolve minor disagreements quickly. Without unified values, actions can diverge, causing misunderstandings and inefficiencies.

Good Values at Snowball

Snowball practices four core values: Proactiveness , Professionalism , Efficiency , and Empathy .

Proactiveness: Engineers are encouraged to constantly question and improve their code, monitoring, product design, and overall workflow, leading to faster personal growth and higher impact.

Professionalism: Technical competence is essential; writing buggy code or lacking deep knowledge cannot be compensated by attitude alone.

Efficiency: Teams should adopt better tools, languages, and frameworks to accelerate development, deployment, and operations. Snowball early adopted Node.js, Docker, Scala, and Go to maximize efficiency.

Empathy: Engineers should consider the needs of product users, upstream/downstream partners, and fellow developers, ensuring APIs are clear and services are easy to use.

Robust Infrastructure

Why Build Infrastructure

Engineers prefer automation to reduce repetitive work and human error. A good infrastructure is judged by whether engineers miss the tools after leaving the team.

What Infrastructure to Build

The development lifecycle includes documentation, issue tracking, code management, CI, code quality checks, mobile packaging, testing, deployment, and monitoring. Selecting the right tools—commercial, free, or open‑source—is key, and custom tools can be built when needed.

How Snowball Implements Infrastructure

Commercial products: Confluence for documentation, Jira for issue tracking (replacing Redmine), which dramatically increased documentation volume and usability.

Open‑source products: Jenkins for continuous integration, extended with plugins and custom scripts for building, testing, and deployment.

Self‑built products: A unified deployment system that automatically builds Docker images and provides a web UI for selecting deployment environments, handling over 100 daily deployments. A custom monitoring platform combines several open‑source components with proprietary code to standardize log formats, automate collection, and generate dashboards for new services.

Punishment and Rewards

Snowball uses standard performance management (KPI, OKR) and adds specific measures for engineers.

Punishment

When a production incident occurs, the responsible engineer must write a detailed post‑mortem and share it with the team to prevent recurrence. Low‑level mistakes may incur a fine, which is later redistributed as a reward.

Human error (e.g., missing code review, ignoring documentation, not confirming commands).

Repeated identical mistakes.

Insufficient testing before release.

The goal is to remember and avoid repeat errors, not merely to collect money.

Rewards

Engineers are encouraged to share knowledge internally and at conferences; such contributions are recognized with awards, hackathon prizes, and annual technical excellence awards. Although monetary value may be modest, the recognition boosts influence and motivation.

Conclusion

Engineer culture is built through daily actions, not slogans. By fostering the right values, providing effective tools, and balancing punishment with recognition, Snowball creates an environment where engineers enjoy their work and stay long‑term.

Additional Note

Snowball is hiring Java engineers, DevOps engineers, test engineers, and algorithm engineers. Interested candidates can view the original posting for details.