In the Plex
Source: https://www.simonandschuster.com/books/In-the-Plex/Steven-Levy/9781416596585 ↗
Levy had unprecedented access to Google's inner workings — its engineers, its executives, its internal culture — and produced the definitive account of how the company actually operated during its formative decade.
The book covers the development of search, the creation of AdWords, the launch of Gmail and Google Maps, the Android acquisition, and the company's confrontation with China, all told through the decisions and debates of the people involved.
Levy is especially strong on Google's engineering culture: the reliance on data over intuition, the 20% time experiments, the hiring process designed to select for raw intelligence.
Where other accounts traffic in myths, Levy provides mechanisms — how decisions were actually made, what was debated, what was ignored.
For product leaders, it is an organizational case study of a company that scaled engineering-driven product development further than anyone before it.
A natural complement to Levy's Hackers, which is already in this library.
Central argument
Levy's central argument is that Google's dominance was not accidental but the product of a specific and replicable organizational logic: engineering culture elevated above all other functions, decisions driven by data rather than intuition, and hiring optimized relentlessly for raw intelligence over domain experience. The book contends that this logic — visible in the architecture of AdWords, the 20% time policy, and the internal debates behind products like Gmail and Android — explains both Google's speed and its blind spots. Google succeeded not despite its unusual operating principles but precisely because of them, and those principles were deliberate from the beginning.
Critique
Because Levy was granted exceptional internal access, the account risks reproducing the self-understanding of Google's leadership rather than subjecting it to genuine scrutiny — a structural problem with authorized journalism. The engineering-culture thesis is compelling but underexamines what was systematically lost or damaged by that same culture: the devaluation of design, the repeated failures in social products, and the ethical shortcuts that accompanied data-driven rationalism. A reader looking for a critical account of the costs of Google's model will find Levy more chronicler than interrogator.
Why it matters for product
For a CPO, the book functions as a high-resolution case study in what it actually takes to scale engineering-driven product development — not the values statement, but the mechanisms: how hiring shapes product instincts, how internal data infrastructure enables decision-making, and how culture compounds over time into organizational capability. The tension Levy surfaces between Google's data-over-intuition doctrine and the products that actually broke through — Gmail originated from a single engineer's side project, not a roadmap — is directly relevant to any leader trying to design discovery processes that don't accidentally exclude the non-measurable. It also sharpens the organizational design question: what you optimize hiring for determines what problems your product teams are even capable of seeing.