How do Google engineers work?

How do Google engineers work? Often times I, as an ex-Googler, need to recall the way how Googlers worked. That's because, when I encounter a problem, I usually try to imagine "What would XXXXX do?", where XXXXX is usually a great Googler or ex-Googler.

Thankfully Google published lots of helpful information. The following materials are good starters for those who want to take a quick look at Google engineering.

• Software Engineering at Google : A concise and easy-to-read paper.
• Software Engineering at Google : A thick (but still easy to read) book. It even explains the roles of TLs, TLMs, and eng managers. Free PDF available.
• The Production Environment at Google, from the Viewpoint of an SRE : A book chapter. Describes basic Google infrastructure and development environment.
• Google Style Guides : Coding style guides. Google engineers must follow these guides (Or else code reviewers won't approve their CLs).
• Code search at Google Open Source : Shows what their actual code look like.
• SRE Books : Books written by Google's site reliability engineers. Especially the 3rd one ("Site Reliability Engineering ") is a good starting point.
• Design Docs at Google : The article linked here "tries" to describe what a Google design doc looks like. I think it's quite close to actual Google design docs, except that they mostly use Google Docs at Google. Google has templates for various types of design docs.
• Google's public design docs for Golang and Chromium : Great examples.

And here's a comment I wrote on a Quora post about Google :

"Re: #2, after leaving Google, I realized how valuable Google’s internal engineering for source code management was. Their highly scalable source repository (including integration with cloud/local filesystem that allows fetching only the required parts) and distributed and fine-grained build system made monorepo possible with such a gigantic codebase. And monorepo, with very simple branching scheme (everybody looks at the mainline only, basically), seems to bring very good advantages. Now with super powerful code search and the web based IDE, it is fantastic. I truly miss many of them. Oh I forgot to mention the unrealistically good code review system, originated from Guido van Rossum’s Mondrian. And their culture that pursues high quality engineering."

EDITED Nov. 14, 2021: If you're curious about how Agile/Scrum are used at Google: link1 , link2 , link3 , link4 , link5 , and ... link6 (This article by Steve Yegge is kinda extreme and militant, but I guess there are many Googlers who would agree with it.)