@GergelyOrosz: I did my first-ever AMA episode. Your questions, my answers! Timestamps: 00:00 Intro 01:56 From Uber to writing 09:22 A…
Summary
Gergely Orosz hosts his first AMA episode, answering questions on AI-native SDLC, AI in hiring, engineering management, and sharing how the pandemic led to his writing career.
View Cached Full Text
Cached at: 07/11/26, 05:33 PM
I did my first-ever AMA episode. Your questions, my answers! Timestamps:
00:00 Intro 01:56 From Uber to writing 09:22 AI-native SDLC 14:00 AI and hiring 19:06 Engineers currently thriving 22:18 Junior roles 24:44 Meta’s war mode 27:54 AI at Big Tech vs. startups 36:46 Tech debt 41:36 Types of engineering managers 44:40 Measuring AI productivity 48:30 The value of CS degrees 50:53 AI at Pragmatic Engineer 56:09 Future-proofing your career 1:01:36 The EU job market 1:03:55 Making money as a creator 1:08:20 What’s next for The Pragmatic Engineer 1:09:27 Bunq and Pollen 1:13:38 Spotting trends 1:14:33 Book updates 1:15:20 Favorite books & tech products 1:17:13 What won’t change in engineering
Brought to you by @AntithesisHQ: verify your system’s correctness without human review or traditional integration tests – and avoid bugs or outages.
Here’s a fun fact I don’t think I’ve shared before: without the COVID-19 pandemic, The Pragmatic Engineer might not exist. Prior to the global health crisis in 2020, I had no plans to get serious about writing: I enjoyed blogging on The Pragmatic Engineer blog, but intended to remain an engineering manager or software engineer for the foreseeable future.
But then, COVID-19 happened and Uber made layoffs, which led to a quarter of my team being let go, while the rest of us were disbanded into other teams. It was a tough time, and I decided it was a good moment to exit and finish writing a book I had been working on, ‘The Software Engineer’s Guidebook’. After that project was complete, I planned to try and start a VC-funded startup and build something around platform engineering; possibly a system for tracking RFCs at mid-sized and larger companies.
I gave myself around eight months to finish the book, but when that deadline elapsed, it still wasn’t ready. I did write three other books (‘The Tech Resume Inside-Out’, ‘Building Mobile Apps at Scale’, and ‘Growing as a Mobile Engineer’) and still wasn’t convinced by any startup idea. But I did discover that I like to write!
Similar Articles
@PremiumGoblin: Here are the most asked questions from my AMA! First off thanks everyone for the warm welcome. I had a blast doing this…
John Kim, an L7 Senior Staff SWE at Meta, recaps an AMA session discussing topics like the future of software engineering jobs, AI coding workflows, and personal experiences in the tech industry.
@GergelyOrosz: I asked myself "how does OpenAI move so quickly?" back 3 years ago, and did a writeup back then. How OpenAI worked when…
Gergely Orosz shares his earlier deep-dive on how OpenAI's Applied team ships ChatGPT so quickly, based on an exclusive interview with engineering lead Evan Morikawa. The article covers OpenAI's engineering culture, independent startup-like operations, tight research integration, and high talent density.
@GergelyOrosz: From a lead fullstack engineer in Germany, interviewing: "Interviews have changed, a LOT! In the past, interview questi…
A lead fullstack engineer in Germany observes that tech interviews have shifted from discussing frameworks like React vs Angular to requiring candidates to use AI to rapidly generate a product from a spec, calling the trend 'pure insanity'.
@aiDotEngineer: Tokenmaxxing, Productivity, & internal AI Platforms @swyx in conversation with @GergelyOrosz, Editor of The Pragmatic E…
Podcast discussion on "tokenmaxxing," real-world AI productivity gains, and how internal AI platforms are reshaping software engineering roles.
@addyosmani: I had a great conversation in SF with @GergelyOrosz. We talked about engineering roles unbundling, DevTools to AI agent…
Addy Osmani and Gergely Orosz discussed engineering roles, DevTools, and AI agents in a conversation in San Francisco, with timestamps provided for a detailed discussion.