What Google Taught Me: Differentiation, Tech Mindset, and Management Insights

I joined Google in March 2006 and left in September 2016 as a Staff Software Engineer/Manager, spending ten and a half years there in three main phases: early work on Linux desktop search and open‑source projects, middle years on Google China products such as input methods and Google Music, and later years focused on Knowledge Graph, which drove major changes in Google Search and Google Now.

1. Differentiation

Working at Google immersed me in a culture that celebrates individuality. Unlike the uniform expectations of Chinese education, Google (along with Apple, Facebook, Twitter) encourages diverse personalities, hobbies, and backgrounds, allowing engineers to meet fascinating people and experience a vibrant, non‑monotonous workplace.

Examples of diverse interests among colleagues include building custom bicycles, campaigning for political candidates, traveling to unknown places, studying ancient phonology, marine biology research, second‑hand camera trading, writing sci‑fi, and even attempting high‑altitude skydiving.

Google’s support for LGBT employees, visible through public events and internal communications, reinforced the idea that diversity is a natural part of humanity rather than a political statement.

2. Changing the Technical Mindset

Before Google, I developed banking software for large Chinese banks, viewing technology as a tool to solve user needs. At Google, I shifted from being a technology “user” to a technology “owner,” collaborating directly with leading engineers and contributing to groundbreaking projects like MapReduce, Bigtable, and TensorFlow.

Inside Google, code review, static analysis, and automated style checks are enforced by tools, making compliance seamless and reducing bureaucratic overhead. This tool‑driven enforcement allows engineers to focus on innovation rather than paperwork.

3. The Meaning of “Management”

Managing engineers at Google differs from traditional companies: the emphasis is on empowering teams to deliver world‑class quality without heavy supervision. Processes are lightweight, relying on effective tools such as Code Style, Code Review, and automated checks rather than rigid ISO‑style procedures.

Technical managers often split their time between leadership duties and hands‑on coding, reflecting Google’s belief that smart engineers need motivation more than micromanagement.

4. Attitude Toward One’s Career

Beyond salary, the most rewarding aspect of Google was the freedom to pursue joy‑driven projects, especially the Google Doodles team, where I could blend art, animation, and code to create playful experiences for users.

This “slow‑life” philosophy—working for happiness and diversity—became my guiding principle, shaping how I view career fulfillment and personal growth.