April 2026
Intermediate
208 pages
5h 47m
English
Content preview from Growth Engineering
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
CHAPTER 8Building a Growth Engineering Team
In previous chapters, we explored the technical foundations of growth engineering and its critical role in driving product success. But many readers now ask the practical question: How do I build this? In other words, how can growth engineering be embedded into an organization, and what kind of people are needed to make it work?
This chapter focuses on those questions. It examines how to build a growth engineering team—from defining its purpose and structure to identifying the skills, culture, and rituals that make it thrive.
What Makes a Growth Engineering Team Unique
A growth engineering team is not just another group of developers who build features. It is a team built around experimentation, measurement, and iteration. Its success is not defined by how many features it ships but by how much measurable impact those features create.
Traditional engineering teams are often optimized for stability, performance, and reliability. Growth engineering teams share those values but combine them with a scientific mindset. They design systems that make it easy to test, learn, and improve continuously. In a mature organization, growth engineers are not only writing code; they are designing experiments, instrumenting data, and working closely with product managers and analysts to interpret results.
The difference lies in intent. A typical feature engineer builds what the roadmap dictates. A growth engineer tests whether what is being built ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.