Growth Engineer

Why this role exists

Most commerce growth hides in retention. The flows, the segments, the timing, the experiments that turn a first order into a second and a second into a habit. That's a system someone has to own end to end, and it's technical enough that a marketer can't own it alone.

The system you'll model

The customer's life after checkout. What actually predicts a second order, where the flows leak, what a segment is worth, and what the data underneath Klaviyo and the rest is really saying. You need to see lifecycle as one system, not a folder of automations.

What you'll own

Retention, as a number. The flows, the segments, and the experiments across the lifecycle stack, built and shipped by you. You're technical, but the job is growth-led: the question is never how many messages went out, it's whether more customers came back.

Who you are

You've built lifecycle or CRM systems and got hooked on the experiment results more than the tooling. You write real automation, you read your own data, and you'd rather move a retention curve than launch a campaign.

Who this isn't for

If you measure the job in sends, campaigns, or how elaborate the flow diagram looks, we'll disagree about what done means. Volume isn't the point here.

How we evaluate

Retention moved, against a baseline. Not messages sent.