Growth Engineer

About the role

THE SHORT VERSION

An engineer who owns the numbers. You find where people drop off between signup and their first real win with Viktor, design the experiment that fixes it, build it end to end and ship it the same week.

THE HARD PART

Viktor lives where work already happens, in Slack and Teams, with web, desktop, and mobile apps on the way. People talk to him like a colleague, and the whole product is a conversation with an AI employee who writes code, runs it, and ships real work back.

We want people to hand Viktor the work they'd give a great hire, and earning that is as hard as making the thing work at all. Viktor acts on his own and sometimes gets it wrong, and your job is to make people trust him with their real work anyway.

Most growth playbooks assume a product people click through. Viktor is a conversation with an AI employee, so activation means a first task that goes well. The levers are onboarding conversations, defaults and nudges as much as screens.

WHAT YOU'LL ACTUALLY DO

- Find where users stall, from install to first win to team-wide use, and fix it yourself.

- Run experiments: a clear hypothesis, shipped behind a flag, a result you act on. You design measurement with our Growth Data Scientist.

- Own activation for Viktor in Slack and Viktor projects: first run, first task, time-to-value.

- Make features discoverable and move retention through in-product prompts, lifecycle nudges and better defaults.

- Own land-and-expand loops: invites, sharing, referrals.

- Instrument everything you ship so every change has a number behind it.

- Whatever needs building. Small team, large surface.

WHO YOU ARE

- Customer-first, and you get excited about what data and user feedback reveal about how to grow usage. Then you have the product intuition to ship the fix.

- You think in metrics. You can define an activated user from the data, take a metric apart, and say which funnel stage is leaking and why.

- You've moved activation, retention or conversion, and you can show the before-and-after.

- You run experiments: A/B tests with a clear hypothesis and a result you act on.

- You've shipped a real product that real people use, and you owned it end to end. A product with real users is the point, not a side project that never left localhost.

- Real engineering strength. You ship your own PRs, including ones that touch the database and user data, without anyone else gating them. Depth in your own area matters more than full-stack breadth.

- Detail oriented. Empty states, microcopy, edge cases: you notice, and you won't ship until it's right.

- You talk to users and own outcomes, not tickets. You shape the problem, cut scope when you should, and ship the thing that moves the metric.

- Speed, with the bar up. You ship today, not Thursday, and it's still good.