Culture & Ideas7/10
Gergely Orosz Interviews Kelsey Hightower on Path From DSL Technician to Google and Microsoft
▶
Gergely Orosz promotes a podcast episode with Kelsey Hightower covering his non-traditional path into tech, rise of Kubernetes, DevRel at Google and his move to Microsoft, plus lessons on AI. The post includes a timestamped outline and sponsor mentions.
Original post · 3 min read
Kelsey Hightower has one of the most inspiring stories in tech: he went from a technician installing DSL modems, through self-directed study and very hard work, to one of the very few Distinguished Engineer at Google whom Satya Nadella personally persuaded to join Microsoft.
Timestamps:
00:00 Intro
03:34 Kelsey’s first job at McDonald’s
05:04 His non-traditional path into tech
11:45 Landing his first tech job with an A+ certification
15:33 His entrepreneurial years
19:45 Joining Google as a data center technician
27:48 Learning automation at a Rackspace spinoff
33:26 Moving into financial services
50:00 Building a reputation through open source
53:55 From configuration management to containers
1:08:20 The rise of Kubernetes
1:25:05 Why he almost joined NASA instead of Google
1:29:20 Defining DevRel at Google
1:38:20 Demonstrating impact at Google
1:41:20 Microsoft's offer
1:55:20 Learning how to slow down
2:06:39 Advising and investing
2:15:03 A people-first view of GenAI
2:24:27 Using AI with guardrails
2:28:26 Matching AI to the task
2:36:06 Staying relevant in the AI era
Brought to you by outstanding teams building products I love:
• @AntithesisHQ: verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. antithesis.com/pragmatic
• @sentry: application monitoring software considered “not bad” by millions of developers sentry.io/pragmatic
• @buildkite: CI software built to absorb whatever your coding agents throw at the build queue. OpenAI, Anthropic, Uber and others are customers: buildkite.com/pragmatic
Three interesting learnings from Kelsey:
1. Side hustles and doing your own thing teach you business like no IC job can.
Before becoming a software engineer at Google, Kelsey was a manager for his comedian friend, operated a computer store, and did IT contracting. These gigs taught him logistics, planning, and about money. All this helped him be far more effective at talking with executives and acting as an executive sponsor inside Google.
2. Can you explain what your startup does without mentioning AI?
When Kelsey researches startups seeking his advice, he challenges founders to not say “AI” once. This means that they must explain the actual value their company creates. One unexpected benefit of this is that it often reveals there are easier, cheaper ways to achieve a goal than with AI.
3. It’s very rare to get an extra zero put on your compensation figure – but it happened.
Kelsey was a successful, well-paid Google engineer when Microsoft made him an offer that 10x’d his salary (!!). When Kelsey told Google he was planning to take the offer, it matched the offer, proving that his market value had massively increased. It shows that being well paid doesn’t necessarily mean you’re being paid at the correct market rate.
Timestamps:
00:00 Intro
03:34 Kelsey’s first job at McDonald’s
05:04 His non-traditional path into tech
11:45 Landing his first tech job with an A+ certification
15:33 His entrepreneurial years
19:45 Joining Google as a data center technician
27:48 Learning automation at a Rackspace spinoff
33:26 Moving into financial services
50:00 Building a reputation through open source
53:55 From configuration management to containers
1:08:20 The rise of Kubernetes
1:25:05 Why he almost joined NASA instead of Google
1:29:20 Defining DevRel at Google
1:38:20 Demonstrating impact at Google
1:41:20 Microsoft's offer
1:55:20 Learning how to slow down
2:06:39 Advising and investing
2:15:03 A people-first view of GenAI
2:24:27 Using AI with guardrails
2:28:26 Matching AI to the task
2:36:06 Staying relevant in the AI era
Brought to you by outstanding teams building products I love:
• @AntithesisHQ: verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages. antithesis.com/pragmatic
• @sentry: application monitoring software considered “not bad” by millions of developers sentry.io/pragmatic
• @buildkite: CI software built to absorb whatever your coding agents throw at the build queue. OpenAI, Anthropic, Uber and others are customers: buildkite.com/pragmatic
Three interesting learnings from Kelsey:
1. Side hustles and doing your own thing teach you business like no IC job can.
Before becoming a software engineer at Google, Kelsey was a manager for his comedian friend, operated a computer store, and did IT contracting. These gigs taught him logistics, planning, and about money. All this helped him be far more effective at talking with executives and acting as an executive sponsor inside Google.
2. Can you explain what your startup does without mentioning AI?
When Kelsey researches startups seeking his advice, he challenges founders to not say “AI” once. This means that they must explain the actual value their company creates. One unexpected benefit of this is that it often reveals there are easier, cheaper ways to achieve a goal than with AI.
3. It’s very rare to get an extra zero put on your compensation figure – but it happened.
Kelsey was a successful, well-paid Google engineer when Microsoft made him an offer that 10x’d his salary (!!). When Kelsey told Google he was planning to take the offer, it matched the offer, proving that his market value had massively increased. It shows that being well paid doesn’t necessarily mean you’re being paid at the correct market rate.
♥ 622 · ⟲ 51 · 👁 61.8KView on X ↗
