Why Google Engineers Write Only 100‑150 Lines a Day: Myths, Metrics, and Real Work

Recently a Quora comment by Google engineer Raymond Farias sparked debate: a survey suggested an efficient Google engineer writes about 100‑150 lines of code daily, a figure the author believes underestimates reality. To verify, the author tallied his own peak daily output and found it matched the 150‑line claim.

The comment ignited discussion about whether such a low line count implies easy or inefficient work at Google. Earlier, Business Insider highlighted a group dubbed “The Coasters” who allegedly follow a “rest and vest” philosophy, earning money with minimal work.

In response, a Google colleague who earned Top Performer for three consecutive years, Yan, shared his perspective:

Q1. What do you think about Google employees writing only 100‑150 lines a day?

Yan: Evaluating programmers by line count is unfair. In a large company like Google, each line often represents substantial effort because engineers must understand massive codebases, consult extensive references, and grasp complex requirements before writing.

Additionally, Google’s culture emphasizes meticulous detail, so developers invest significant time before any code is written. A seemingly small change may involve 6‑7 hours of work, reflecting the true value of top engineers.

Thus, line count is not a reliable metric, and Google does not use it internally to assess quality.

Q2. If not lines, how should programmer work be measured?

Yan: Impact is the real yardstick. Beyond quantity, code quality and the business impact of one’s work matter—whether the feature adds value, improves user experience, or creates new products that help people.

Q3. What does a typical workday look like for you at Google?

Yan: More than half the day is spent on thinking and design, not coding. As engineers advance, they engage more in design and management, reducing coding time. At senior or director levels, coding becomes a minor responsibility; the focus shifts to guiding teams, defining product direction, and coordinating cross‑team collaboration.

Q4. Does the “Coaster” phenomenon exist at Google?

Yan: Google has a “hard‑to‑fire, easy‑to‑let‑go” reputation, but the notion of employees doing nothing while getting paid is a myth. Silicon Valley competition is fierce, and such behavior is unsustainable. While Google offers good work‑life balance and careful layoff practices, it still expects high performance, using softer approaches when adjustments are needed.

Overall, becoming a solid engineer requires dedication, continuous learning, and realistic expectations about workload and impact.