Google’s Engineering Culture The Pragmatic Engineer podcast

Content provided by Gergely Orosz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Gergely Orosz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

The Pragmatic Engineer »
Google’s engineering culture

9d ago 2:46:20

MP3•Episode home

Brought to You By:

•⁠ Statsig ⁠ — ⁠ The unified platform for flags, analytics, experiments, and more. Something interesting is happening with the latest generation of tech giants. Rather than building advanced experimentation tools themselves, companies like Anthropic, Figma, Notion and a bunch of others… are just using Statsig. Statsig has rebuilt this entire suite of data tools that was available at maybe 10 or 15 giants until now. Check out Statsig.

•⁠ Linear – The system for modern product development. Linear is just so fast to use – and it enables velocity in product workflows. Companies like Perplexity and OpenAI have already switched over, because simplicity scales. Go ahead and check out Linear and see why it feels like a breeze to use.

—

What is it really like to be an engineer at Google?

In this special deep dive episode, we unpack how engineering at Google actually works. We spent months researching the engineering culture of the search giant, and talked with 20+ current and former Googlers to bring you this deepdive with Elin Nilsson, tech industry researcher for The Pragmatic Engineer and a former Google intern.

Google has always been an engineering-driven organization. We talk about its custom stack and tools, the design-doc culture, and the performance and promotion systems that define career growth. We also explore the culture that feels built for engineers: generous perks, a surprisingly light on-call setup often considered the best in the industry, and a deep focus on solving technical problems at scale.

If you are thinking about applying to Google or are curious about how the company’s engineering culture has evolved, this episode takes a clear look at what it was like to work at Google in the past versus today, and who is a good fit for today’s Google.

Jump to interesting parts:

(13:50) Tech stack

(1:05:08) Performance reviews (GRAD)

(2:07:03) The culture of continuously rewriting things

—

Timestamps

(00:00) Intro

(01:44) Stats about Google

(11:41) The shared culture across Google

(13:50) Tech stack

(34:33) Internal developer tools and monorepo

(43:17) The downsides of having so many internal tools at Google

(45:29) Perks

(55:37) Engineering roles

(1:02:32) Levels at Google

(1:05:08) Performance reviews (GRAD)

(1:13:05) Readability

(1:16:18) Promotions

(1:25:46) Design docs

(1:32:30) OKRs

(1:44:43) Googlers, Nooglers, ReGooglers

(1:57:27) Google Cloud

(2:03:49) Internal transfers

(2:07:03) Rewrites

(2:10:19) Open source

(2:14:57) Culture shift

(2:31:10) Making the most of Google, as an engineer

(2:39:25) Landing a job at Google

—

The Pragmatic Engineer deepdives relevant for this episode:

•⁠ Inside Google’s engineering culture

•⁠ Oncall at Google

•⁠ Performance calibrations at tech companies

•⁠ Promotions and tooling at Google

•⁠ How Kubernetes is built

•⁠ The man behind the Big Tech comics: Google cartoonist Manu Cornet

—

Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email [email protected].

Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe

41 episodes

#Tech #News #Tech News #Gergely Orosz