Supported by Our Partners

• Formation — Level up your career and compensation with Formation. 

• WorkOS — The modern identity platform for B2B SaaS

• Vanta — Automate compliance and simplify security with Vanta.

—

In today’s episode of The Pragmatic Engineer, I’m joined by Jonas Tyroller, one of the developers behind Thronefall, a minimalist indie strategy game that blends tower defense and kingdom-building, now available on Steam.

Jonas takes us through the journey of creating Thronefall from start to finish, offering insights into the world of indie game development. We explore:

• Why indie developers often skip traditional testing and how they find bugs

• The developer workflow using Unity, C# and Blender

• The two types of prototypes game developers build 

• Why Jonas spent months building game prototypes in 1-2 days

• How Jonas uses ChatGPT to build games

• Jonas’s tips on making games that sell

• And more!

—

Timestamps

(00:00) Intro

(02:07) Building in Unity

(04:05) What the shader tool is used for 

(08:44) How a Unity build is structured

(11:01) How game developers write and debug code 

(16:21) Jonas’s Unity workflow

(18:13) Importing assets from Blender

(21:06) The size of Thronefall and how it can be so small

(24:04) Jonas’s thoughts on code review

(26:42) Why practices like code review and source control might not be relevant for all contexts

(30:40) How Jonas and Paul ensure the game is fun 

(32:25) How Jonas and Paul used beta testing feedback to improve their game

(35:14) The mini-games in Thronefall and why they are so difficult

(38:14) The struggle to find the right level of difficulty for the game

(41:43) Porting to Nintendo Switch

(45:11) The prototypes Jonas and Paul made to get to Thronefall

(46:59) The challenge of finding something you want to build that will sell

(47:20) Jonas’s ideation process and how they figure out what to build 

(49:35) How Thronefall evolved from a mini-game prototype

(51:50) How long you spend on prototyping 

(52:30) A lesson in failing fast

(53:50) The gameplay prototype vs. the art prototype

(55:53) How Jonas and Paul distribute work 

(57:35) Next steps after having the play prototype and art prototype

(59:36) How a launch on Steam works 

(1:01:18) Why pathfinding was the most challenging part of building Thronefall

(1:08:40) Gen AI tools for building indie games 

(1:09:50) How Jonas uses ChatGPT for editing code and as a translator 

(1:13:25) The pros and cons of being an indie developer 

(1:15:32) Jonas’s advice for software engineers looking to get into indie game development

(1:19:32) What to look for in a game design school

(1:22:46) How luck figures into success and Jonas’s tips for building a game that sells

(1:26:32) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

• Game development basics https://newsletter.pragmaticengineer.com/p/game-development-basics 

• Building a simple game using Unity https://newsletter.pragmaticengineer.com/p/building-a-simple-game

—

See the transcript and other references from the episode at ⁠⁠https://newsletter.pragmaticengineer.com/podcast⁠⁠

—

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

Supported by Our Partners

• Sonar —  Trust your developers – verify your AI-generated code.

• Vanta —Automate compliance and simplify security with Vanta.

—

In today's episode of The Pragmatic Engineer, I'm joined by Charity Majors, a well-known observability expert – as well as someone with strong and grounded opinions. Charity is the co-author of "Observability Engineering" and brings extensive experience as an operations and database engineer and an engineering manager. She is the cofounder and CTO of observability scaleup Honeycomb.

Our conversation explores the ever-changing world of observability, covering these topics:

• What is observability? Charity’s take

• What is “Observability 2.0?”

• Why Charity is a fan of platform teams

• Why DevOps is an overloaded term: and probably no longer relevant

• What is cardinality? And why does it impact the cost of observability so much?

• How OpenTelemetry solves for vendor lock-in 

• Why Honeycomb wrote its own database

• Why having good observability should be a prerequisite to adding AI code or using AI agents

• And more!

—

Timestamps

(00:00) Intro 

(04:20) Charity’s inspiration for writing Observability Engineering

(08:20) An overview of Scuba at Facebook

(09:16) A software engineer’s definition of observability 

(13:15) Observability basics

(15:10) The three pillars model

(17:09) Observability 2.0 and the shift to unified storage

(22:50) Who owns observability and the advantage of platform teams 

(25:05) Why DevOps is becoming unnecessary 

(27:01) The difficulty of observability 

(29:01) Why observability is so expensive 

(30:49) An explanation of cardinality and its impact on cost

(34:26) How to manage cost with tools that use structured data 

(38:35) The common worry of vendor lock-in

(40:01) An explanation of OpenTelemetry

(43:45) What developers get wrong about observability 

(45:40) A case for using SLOs and how they help you avoid micromanagement 

(48:25) Why Honeycomb had to write their database 

(51:56) Companies who have thrived despite ignoring conventional wisdom

(53:35) Observability and AI 

(59:20) Vendors vs. open source

(1:00:45) What metrics are good for 

(1:02:31) RUM (Real User Monitoring) 

(1:03:40) The challenges of mobile observability 

(1:05:51) When to implement observability at your startup 

(1:07:49) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

• How Uber Built its Observability Platform https://newsletter.pragmaticengineer.com/p/how-uber-built-its-observability-platform 

• Building an Observability Startup https://newsletter.pragmaticengineer.com/p/chronosphere 

• How to debug large distributed systems https://newsletter.pragmaticengineer.com/p/antithesis 

• Shipping to production https://newsletter.pragmaticengineer.com/p/shipping-to-production 

—

See the transcript and other references from the episode at ⁠⁠https://newsletter.pragmaticengineer.com/podcast⁠⁠

—

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

Supported by Our Partners

• Vanta — Automate compliance and simplify security with Vanta.

• WorkOS — The modern identity platform for B2B SaaS.

—

In today’s episode of The Pragmatic Engineer, I’m joined by Michael Novati, Co-founder and CTO of Formation. Before launching Formation, Michael spent eight years at Meta, where he was recognized as the top code committer company-wide for several years. The “Coding Machine” archetype was modeled after Michael at the company.

In our conversation, we talk about what it was like working at Meta and dive into its engineering culture. Michael shares his journey of quickly climbing the ranks from intern to principal-level and gives level-headed advice on leveling up your career. Plus, we discuss his work at Formation, where he helps engineers grow and land roles at top tech companies.

In this episode, we cover:

• An overview of software architect archetypes at Meta, including “the coding machine”

• Meta’s org structure, levels of engineers, and career trajectories

• The importance of maintaining a ‘brag list’ to showcase your achievements and impact

• Meta’s engineering culture and focus on building internal tools

• How beating Mark Zuckerberg in a game of Risk led to him accepting Michael’s friend request

• An inside look at Meta’s hiring process

• Tips for software engineers on the job market on how to do better in technical interviews

• And more!

—

Timestamps

(00:00) Intro

(01:45) An explanation of archetypes at Meta, including “the coding machine”

(09:14) The organizational structure and levels of software engineers at Meta

(10:05) Michael’s first project re-writing the org chart as an intern at Meta

(12:42) A brief overview of Michael’s work at Meta 

(15:29) Meta’s engineering first culture and how Michael pushed for even more for ICs

(20:03) How tenure at Meta correlated with impact 

(23:47) How Michael rose through the ranks at Meta so quickly

(29:30) The engineering culture at Meta, including how they value internal tools

(34:00) Companies that began at Meta or founded by former employees

(36:11) Facebook’s internal tool for scheduling meetings 

(37:45) The product problems that came with scaling Facebook

(39:25) How Michael became Facebook friends with Mark Zuckerberg 

(42:05) The “Zuck review” process

(44:30) How the French attacks crashed Michael’s photo inlay prototype

(51:15) How the photo inlay bug was fixed 

(52:58) Meta’s hiring process 

(1:03:40) Insights from Michael’s work at Formation

(1:09:08) Michael’s advice for experienced engineers currently searching for a job

(1:11:15) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

• Inside Meta’s engineering culture: https://newsletter.pragmaticengineer.com/p/facebook

• Stacked diffs (and why you should know about them) https://newsletter.pragmaticengineer.com/p/stacked-diffs 

• Engineering career paths at Big Tech and scaleups: https://newsletter.pragmaticengineer.com/p/engineering-career-paths 

• Inside the story of how Meta built the Threads app: https://newsletter.pragmaticengineer.com/p/building-the-threads-app

—

See the transcript and other references from the episode at ⁠⁠https://newsletter.pragmaticengineer.com/podcast⁠⁠

—

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

Supported by Our Partners

• DX — DX is an engineering intelligence platform designed by leading researchers. 

• Vanta — Automate compliance and simplify security with Vanta.

—

In today’s episode of The Pragmatic Engineer, I catch up with one of the best tech recruiters I’ve had the opportunity to work with: Blake Stockman, a former colleague of mine from Uber. Blake built a strong reputation in the recruiting world, working at tech giants like Google, Meta, and Uber. He also spent time with Y Combinator and founded his agency, where he helped both large tech companies and early-stage startups find and secure top talent. A few months ago, Blake did a career pivot: he is now studying to become a lawyer. I pounced on this perfect opportunity to have him share all that he’s seen behind-the-scenes in tech recruitment: sharing his observations unfiltered.

In our conversation, Blake shares recruitment insights from his time at Facebook, Google, and Uber and his experience running his own tech recruitment agency. We discuss topics such as:

• A step-by-step breakdown of hiring processes at Big Tech and startups• How to get the most out of your tech recruiter, as a candidate• Best practices for hiring managers to work with their recruiter• Why you shouldn’t disclose salary expectations upfront, plus tips for negotiating• Where to find the best startup opportunities and how to evaluate them—including understanding startup compensation• And much more!

—

Timestamps

(00:00) Intro

(01:40) Tips for working with recruiters

(06:11) Why hiring managers should have more conversations with recruiters

(09:48) A behind-the-scenes look at the hiring process at big tech companies 

(13:38) How hiring worked at Uber when Gergely and Blake were there

(16:46) An explanation of calibration in the recruitment process

(18:11) A case for partnering with recruitment 

(20:49) The different approaches to recruitment Blake experienced at different organizations

(25:30) How hiring decisions are made 

(31:34) The differences between hiring at startups vs. large, established companies

(33:21) Reasons desperate decisions are made and problems that may arise

(36:30) The problem of hiring solely to fill a seat

(38:55) The process of the closing call

(40:24) The importance of understanding equity 

(43:27) Tips for negotiating 

(48:38) How to find the best startup opportunities, and how to evaluate if it’s a good fit

(53:58) What to include on your LinkedIn profile

(55:48) A story from Uber and why you should remember to thank your recruiter

(1:00:09) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

• How GenAI is reshaping tech hiring https://newsletter.pragmaticengineer.com/p/how-genai-changes-tech-hiring

• Hiring software engineers https://newsletter.pragmaticengineer.com/p/hiring-software-engineers 

• Hiring an Engineering Manager https://newsletter.pragmaticengineer.com/p/hiring-engineering-managers

• Hiring Junior Software Engineers https://newsletter.pragmaticengineer.com/p/hiring-junior-engineers

—

See the transcript and other references from the episode at ⁠⁠https://newsletter.pragmaticengineer.com/podcast⁠⁠

—

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

Supported by Our Partner

DX⁠ → DX is an engineering intelligence platform designed by leading researchers

—

In today’s episode of The Pragmatic Engineer, I’m joined by Sean Goedecke, Staff Software Engineer at GitHub. Sean is widely known for his viral blog post, “How I ship projects at big tech companies.” In our conversation, he shares how to successfully deliver projects in large tech companies.

Drawing from his experiences at GitHub and Zendesk, Sean reflects on key lessons learned, and we discuss the following topics: 

• Why shipping cannot exclude keeping management happy

• How to work on stuff the company actually values

• Why you should take on extra responsibility to get projects done

• Why technical skills are still more important than soft skills

• Soft skills you should learn: including learning the “management lingo”

• First-hand remote work learnings: advantages, disadvantages, and how to thrive in this setup

• … and much more!

—

Timestamps

(00:00) Intro

(01:50) An explanation of shipping

(05:35) Reasons management may choose to ship something customers don’t love

(09:20) A humbling learning from Sean’s time at Zendesk

(13:27) The importance of learning which rules need to be broken for good business outcomes

(15:28) Common obstacles to shipping

(18:13) DRI: Directly responsible individual

(23:06) The value of strong technical skills and why moving fast is imperative

(28:44) How to leverage your technical skills the right way

(32:16) Advice on earning the trust of leadership

(36:10) A time Gergely shipped a product for a political reason 

(38:30) What GenAI helps software engineers do more easily 

(41:08) Sean’s thoughts on GenAI making engineers more ambitious 

(43:20) The difficulty of building AI tools

(46:10) Advantages of working remotely and strategies for making it work

(52:34) Who is best suited to remote work

(54:48) How the pandemic provided a remote work trial for Sean

(56:45) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

• Software Engineers Leading Projects ⁠https://newsletter.pragmaticengineer.com/p/engineers-leading-projects⁠

• Shipping to production ⁠https://newsletter.pragmaticengineer.com/p/shipping-to-production⁠

• Paying down tech debt ⁠https://newsletter.pragmaticengineer.com/p/paying-down-tech-debt⁠

—

See the transcript and other references from the episode at ⁠⁠https://newsletter.pragmaticengineer.com/podcast⁠⁠

—

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

Supported by Our Partner

DX⁠ → DX is an engineering intelligence platform designed by leading researchers

—

In today’s exciting episode of The Pragmatic Engineer, I am joined by two members of the Notion mobile apps team, Austin Louden and Karn Saheb. Austin and Karn joined Notion in 2019 when Notion was revamping its mobile apps. 

Notion is a versatile productivity and collaboration platform that combines note-taking, task management, and knowledge organization into a single workspace. It is available as a web app, as well as iOS and Android apps for mobile use.

In our conversation today, we take a deep dive into how the Notion mobile team operates and discuss the following: 

• What the engineering culture is like at Notion 

• Why the mobile team focuses so much on app performance

• The incremental shift from Cordova to Native 

• Notion’s tech stack and frameworks they rely on 

• How the mobile team maintains consistency across iOS and Android

• Unique features of the development process, including a public beta, using modules, and practices around feature flags

• … and much more!

—

Timestamps

(00:00) Intro

(02:03) The RFC process at Notion 

(06:00) How Notion uses internal channels to share RFCs

(07:57) Some of the unique ways the mobile team works

(11:07) Why they don’t do sprint planning at Notion—and what they do instead

(12:57) An overview of the size of Notion and teams at Notion

(13:15) The beginning of mobile at Notion

(14:40) A simple explanation of Cordova

(15:40) Why Notion decided to revamp mobile in 2019 and shift to Native

(18:30) How the mobile team evaluated performance as they made the shift to Native

(22:00) Scaling mobile and iterations of moving to Native 

(26:04) Why the home tab project was so complex

(30:59) Why the mobile team saved the editor for last and other future problems

(34:35) How mobile works with other teams 

(36:50) How iOS and Android teams work together 

(38:28) The tech stack at Notion

(39:30) How frameworks are used

(41:57) Pros and cons of different frameworks and why Swift was the right choice

(45:16) How code reviews work at Notion

(48:23) Notion’s mobile team’s testing philosophy

(50:18) How the mobile team keeps compile time so fast

(52:36) Modules in the iOS app

(54:50) Modules in the Android app

(56:44) Behind the scenes of an app release and the public beta

(1:00:34) Practices around feature flags

(1:03:00) The four dev environments at Notion

(1:04:48) How development apps work 

(1:07:40) How and why you can work offline in Notion mobile 

(1:10:24) Austin and Karn’s thoughts on the future of mobile engineering 

(1:12:47) Advice for junior engineers

(1:16:29) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

—

Where to find Austin Louden:

• GitHub: https://github.com/austinlouden

• LinkedIn: https://www.linkedin.com/in/austinlouden

• Website: https://austinlouden.com/

Where to find Karn Saheb:

• GitHub: https://github.com/Karn

• LinkedIn: https://github.com/Karn

• Website: https://karn.io

Where to find Gergely:

• Newsletter: https://www.pragmaticengineer.com/

• YouTube: https://www.youtube.com/c/mrgergelyorosz

• LinkedIn: https://www.linkedin.com/in/gergelyorosz/

• X: https://x.com/GergelyOrosz

—

References and Transcripts:

See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast

—

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

Brought to you by:

• WorkOS — The modern identity platform for B2B SaaS.

• Sevalla — Deploy anything from preview environments to Docker images.

• Chronosphere — The observability platform built for control.

—

Welcome to The Pragmatic Engineer! Today, I’m thrilled to be joined by Grady Booch, a true legend in software development. Grady is the Chief Scientist for Software Engineering at IBM, where he leads groundbreaking research in embodied cognition.

He’s the mind behind several object-oriented design concepts, a co-author of the Unified Modeling Language, and a founding member of the Agile Alliance and the Hillside Group.

Grady has authored six books, hundreds of articles, and holds prestigious titles as an IBM, ACM, and IEEE Fellow, as well as a recipient of the Lovelace Medal (an award for those with outstanding contributions to the advancement of computing). In this episode, we discuss:

• What it means to be an IBM Fellow

• The evolution of the field of software development

• How UML was created, what its goals were, and why Grady disagrees with the direction of later versions of UML

• Pivotal moments in software development history

• How the software architect role changed over the last 50 years

• Why Grady declined to be the Chief Architect of Microsoft – saying no to Bill Gates!

• Grady’s take on large language models (LLMs)

• Advice to less experienced software engineers

• … and much more!

—

Timestamps

(00:00) Intro

(01:56) What it means to be a Fellow at IBM

(03:27) Grady’s work with legacy systems

(09:25) Some examples of domains Grady has contributed to

(11:27) The evolution of the field of software development

(16:23) An overview of the Booch method

(20:00) Software development prior to the Booch method

(22:40) Forming Rational Machines with Paul and Mike

(25:35) Grady’s work with Bjarne Stroustrup

(26:41) ROSE and working with the commercial sector

(30:19) How Grady built UML with Ibar Jacobson and James Rumbaugh

(36:08) An explanation of UML and why it was a mistake to turn it into a programming language

(40:25) The IBM acquisition and why Grady declined Bill Gates’s job offer 

(43:38) Why UML is no longer used in industry 

(52:04) Grady’s thoughts on formal methods

(53:33) How the software architect role changed over time

(1:01:46) Disruptive changes and major leaps in software development

(1:07:26) Grady’s early work in AI

(1:12:47) Grady’s work with Johnson Space Center

(1:16:41) Grady’s thoughts on LLMs 

(1:19:47) Why Grady thinks we are a long way off from sentient AI 

(1:25:18) Grady’s advice to less experienced software engineers

(1:27:20) What’s next for Grady

(1:29:39) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

• The Past and Future of Modern Backend Practices https://newsletter.pragmaticengineer.com/p/the-past-and-future-of-backend-practices 

• What Changed in 50 Years of Computing https://newsletter.pragmaticengineer.com/p/what-changed-in-50-years-of-computing 

• AI Tooling for Software Engineers: Reality Check https://newsletter.pragmaticengineer.com/p/ai-tooling-2024

—

Where to find Grady Booch:

• X: https://x.com/grady_booch

• LinkedIn: https://www.linkedin.com/in/gradybooch

• Website: https://computingthehumanexperience.com

Where to find Gergely:

• Newsletter: https://www.pragmaticengineer.com/

• YouTube: https://www.youtube.com/c/mrgergelyorosz

• LinkedIn: https://www.linkedin.com/in/gergelyorosz/

• X: https://x.com/GergelyOrosz

—

References and Transcripts:

See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast

—

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

Brought to you by:

• Launch Darkly — a platform for high-velocity engineering teams to release, monitor, and optimize great software. 

• Sevalla — Deploy anything from preview environments to Docker images.

• WorkOS — The modern identity platform for B2B SaaS.

—

On today’s episode of The Pragmatic Engineer, I’m joined by fellow Uber alum, Sabin Roman, now the first Engineering Manager at Linear. Linear, known for its powerful project and issue-tracking system, streamlines workflows throughout the product development process.

In our conversation today, Sabin and I compare building projects at Linear versus our experiences at Uber. He shares insights into Linear’s unique approaches, including:

• How Linear handles internal communications

• The “goalie” program to address customer concerns and Linear’s zero bug policy

• How Linear keeps teams connected despite working entirely remotely

• An in-depth, step-by-step walkthrough of a project at Linear

• Linear’s focus on quality and creativity over fash shipping 

• Titles at Linear, Sabin’s learnings from Uber, and much more!

Timestamps

(00:00) Intro

(01:41) Sabin’s background

(02:45) Why Linear rarely uses e-mail internally

(07:32) An overview of Linear's company profile

(08:03) Linear’s tech stack

(08:20) How Linear operated without product people

(09:40) How Linear stays close to customers

(11:27) The shortcomings of Support Engineers at Uber and why Linear’s “goalies” work better

(16:35) Focusing on bugs vs. new features

(18:55) Linear’s hiring process

(21:57) An overview of a typical call with a hiring manager at Linear

(24:13) The pros and cons of Linear’s remote work culture

(29:30) The challenge of managing teams remotely

(31:44) A step-by-step walkthrough of how Sabin built a project at Linear 

(45:47) Why Linear’s unique working process works 

(49:57) The Helix project at Uber and differences in operations working at a large company

(57:47) How senior engineers operate at Linear vs. at a large company

(1:01:30) Why Linear has no levels for engineers 

(1:07:13) Less experienced engineers at Linear

(1:08:56) Sabin’s big learnings from Uber

(1:09:47) Rapid fire round

—

The Pragmatic Engineer deepdives relevant for this episode:

• The story of Linear, as told by its CTO

• An update on Linear, after their $35M fundraise

• Software engineers leading projects

• Netflix’s historic introduction of levels for software engineers

—

Where to find Sabin Roman:

• X: https://x.com/sabin_roman

• LinkedIn: https://www.linkedin.com/in/sabinroman/

Where to find Gergely:

• Newsletter: https://www.pragmaticengineer.com/

• YouTube: https://www.youtube.com/c/mrgergelyorosz

• LinkedIn: https://www.linkedin.com/in/gergelyorosz/

• X: https://x.com/GergelyOrosz

—

References and Transcripts:

See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast

—

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

Brought to you by:

• WorkOS — The modern identity platform for B2B SaaS.

• Sonar —  Trust your developers – verify your AI-generated code.

—

In today’s episode of The Pragmatic Engineer, I’m joined by Irina Stanescu, a seasoned engineer with over 14 years in software engineering and engineering leadership roles at tech companies like Google and Uber. Now an engineering leadership coach, Irina helps tech professionals build impactful careers, teaches a course on influence, and shares insights through her newsletter, The Caring Techie. In our conversation today, Irina shares her journey of rising through the ranks at Google and Uber. We dive into the following topics: 

• An inside look at Google’s unique working processes

• How to build credibility as a new engineer

• Tactical tips for getting promoted 

• The importance of having a career plan and guidance in designing one

• Having influence vs. influencing—and how to become more influential 

• Essential leadership skills to develop

• And so much more

—

In this episode, we cover:

(01:34) Irina’s time at Google

(03:10) An overview of ‘design docs’ at Google

(08:27) The readiness review at Google

(10:40) Why Irina uses spreadsheets

(11:44) Irina’s favorite tools and how she uses them

(13:46) How Google certifies readability

(15:40) Google’s meme generator 

(17:36) Advice for engineers thinking about working for an organization like Google

(20:14) How promotions work at Google

(23:15) How Irina worked towards getting promoted 

(27:50) How Irina got her first mentor 

(30:44) Organizational shifts at Uber while Irina and Gergely were there

(35:50) Why you should prioritize growth over promotion

(36:50) What a career plan is and how to build one

(40:40) Irina’s current role coaching engineers 

(42:23) A simple explanation of influence and influencing 

(51:54) Why saying no is necessary at times

(54:30) The importance of building leadership skills

—

The Pragmatic Engineer deepdives relevant for this episode:

• Preparing for promotions ahead of time: https://newsletter.pragmaticengineer.com/p/preparing-for-promotions 

• Engineering career paths at Big Tech and scaleups: https://newsletter.pragmaticengineer.com/p/engineering-career-paths 

• Getting an Engineering Executive Job: https://newsletter.pragmaticengineer.com/p/getting-an-engineering-executive 

• The Seniority Rollercoaster: https://newsletter.pragmaticengineer.com/p/the-seniority-rollercoaster

—

Where to find Irina Stanescu:

• X: https://x.com/thecaringtechie

• LinkedIn: https://www.linkedin.com/in/irinastanescu/

• Website: https://www.thecaringtechie.com/

• Maven course: Impact through Influence in Engineering Teams: https://maven.com/irina-stanescu/influence-swe

Where to find Gergely:

• Newsletter: https://www.pragmaticengineer.com/

• YouTube: https://www.youtube.com/c/mrgergelyorosz

• LinkedIn: https://www.linkedin.com/in/gergelyorosz/

• X: https://x.com/GergelyOrosz

—

References and Transcripts:

See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast

—

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

Brought to you by:

• The Enterprise Ready Conference on October 30th — For B2B leaders building enterprise SaaS.

• DX — DX is an engineering intelligence platform designed by leading researchers. 

• ByteByteGo — Ace your next system design interview.

—

You may not be familiar with Bending Spoons, but I guarantee you’ve encountered some of their well-known products, like Evernote and Meetup. In today’s episode of The Pragmatic Engineer, we sit down with three key figures from the Italy-based startup: cofounder and CEO Luca Ferrari, CTO Francesco Mancone, and Evernote product lead Federico Simionato. Bending Spoons has been profitable from day one, and there's plenty we can learn from their unique culture, organizational structure, engineering processes, and hiring practices. In today’s conversation, we cover the following topics:

• The controversial acquisitions approach of Bending Spoons

• How Bending Spoons spent more than $1 billion in buying tech companies

• How the Evernote acquisition happened

• How Bending Spoons operates and how it organizes product and platform teams

• Why engineering processes are different across different products

• How ‘radical simplicity’ is baked into everything from engineering processes to pay structure.

• And much more!

—

The Pragmatic Engineer deepdives relevant for this episode:

• Good attrition, bad attrition for software engineers: https://newsletter.pragmaticengineer.com/p/attrition 

• Healthy oncall practices: https://newsletter.pragmaticengineer.com/p/healthy-oncall-practices • Shipping to production: https://newsletter.pragmaticengineer.com/p/shipping-to-production

• QA across the tech industry: https://newsletter.pragmaticengineer.com/p/qa-across-tech

—

In this episode, we cover:

(2:09) Welcome, Luca, Francesco, and Federico from Bending Spoons

(03:15) An overview of the well-known apps and products owned by Bending Spoons

(06:38) The elephant in the room: how Bending Spoons really acquires companies

(09:46) Layoffs: Bending Spoons’ philosophy on this

(14:10) Controversial principles

(17:16) Revenue, team size, and products

(19:35) How Bending Spoons runs AI products and allocates GPUs

(23:05) History of the company

(27:04) The Evernote acquisition

(29:50) Modernizing Evernote’s infrastructure

(32:44) “Radical simplicity” and why they try for zero on calls

(36:13) More on changes made to the Evernote systems

(41:13) How Bending Spoons prioritizes and ships fast 

(49:40) What’s new and what’s coming for Bending Spoons

(51:08) Organizational structure at the company

(54:07) Engineering practices

(57:03) Testing approaches

(58:53) Platform teams

(1:01:52) Bending Spoons tech stack and popular frameworks

(1:05:55) Why Bending Spoons hires new grads and less experienced engineers

(1:08:09) The structure of careers and titles at Bending Spoons

(1:09:50) Traits they look for when hiring 

(1:12:50) Why there aren’t many companies doing what Bending Spoons does 

—

Where to find Luca Ferrari:

• X: https://x.com/luke10ferrari

• LinkedIn: https://www.linkedin.com/in/luca-ferrari-12418318

Where to find  Francesco Mancone:

• LinkedIn: https://www.linkedin.com/in/francesco-mancone

Where to find Federico Simionato:

• X: https://x.com/fedesimio

• LinkedIn: https://www.linkedin.com/in/federicosimionato

Where to find Gergely:

• Newsletter: https://www.pragmaticengineer.com/

• YouTube: https://www.youtube.com/c/mrgergelyorosz

• LinkedIn: https://www.linkedin.com/in/gergelyorosz/

• X: https://x.com/GergelyOrosz

—

References and Transcripts:

See the transcript and other references from the episode at https://newsletter.pragmaticengineer.com/podcast

—

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