Growth Engineer

A Growth Engineer is a programmer who works on a specific question: How does a product get more users, and how do those users stick around? The term comes from English and literally means something like “growth engineer.” Classic programmers build a product’s features, for example the video player of a streaming app. A Growth Engineer, on the other hand, builds everything around it: the sign-up page, the invitation email, the flow when the app is first opened. In doing so, they constantly measure whether their changes actually make a difference. The role thus sits between technology and marketing, but clearly belongs to technology, because in the end it produces program code.

Why companies pay people whose sole job is growth

Many digital products are not successful because they are technically superior. They are successful because the path from the first click to actual use runs smoothly. Every additional step during sign-up costs users. Anyone who gains a few percentage points here gains a great deal when there are millions of visitors. These exact percentage points are precisely a Growth Engineer’s job.

For companies, this is also a matter of cost. Buying new users through advertising is expensive, often several euros per person. If existing users invite friends instead, the growth is nearly free. Dropbox is the best-known example: anyone who invited someone received extra storage space as a gift. Someone had to build, test, and continuously improve this invitation system.

On the stock market and in financial news, exactly these numbers matter. How many active users does a service have per month? How many churn away again? A Growth Engineer works directly on the metrics that later appear in quarterly reports. This explains why the role is often paid above average in job postings from tech companies.

Testing instead of guessing: everyday work

The most important tool is the A/B test. In this setup, one half of visitors gets the old version of a page, the other half gets a modified one. After a few days, one compares which group signed up more often. This way, opinions are replaced by measured values. A Growth Engineer builds both the test versions and the technology that counts and evaluates them in the background.

On top of that comes work on data pipelines. Every click must be reliably recorded and written into a database. If this measurement is flawed, all conclusions drawn from it are worthless. A large part of the job therefore consists of unspectacular diligence in capturing and checking data.

Also typical is the high pace. Instead of spending months building one big feature, many small experiments run in parallel. Most of them accomplish nothing or even make the numbers worse. This is not considered a failure but a normal outcome. A common misconception is that growth engineering is a bag of tricks for quick wins. In reality, it is the patient search for the few changes that have a lasting effect.

Where this work reaches you

You encounter the results of this work every day without noticing. The notice “2 more steps until you’re set up” in an app comes from this corner. So does the email meant to bring you back after two weeks of inactivity. The referral link offering a discount for you and a friend belongs here too.

With AI products, this role is currently in particularly high demand. Chatbot providers compete fiercely for users, and many people only try a tool once. Growth Engineers there build things like free entry-level versions or suggestions that make the first chat easier. Increasingly, they also use AI themselves to automatically generate many variants of text for testing.

There are limits, though. Data protection rules such as the European GDPR dictate which data may be collected at all. Some optimizations are technically possible but not legally permitted. And if prompts become too intrusive, users leave. Good Growth Engineers therefore pay attention to long-term satisfaction, not just next week’s numbers.