Description review
Growth Engineer
getviktor.com · Warsaw or Munich onsite, remote in Europe · back to the listing
HR standards
59/100
needs work
Title ↔ description
74/100
solid
Reads as
Full-Stack Engineer
92% confident
How others title the same work
Large employers
- Software Development Engineer, Influencer Management Adobe
- Senior Software Engineer (EAA) Coinbase
- Senior Software Engineer, Full Stack (Coinbase Advisor - Agentic Trading) Coinbase
- Senior Software Engineer (Typescript), AI Clients: Duo CLI GitLab
- Grafana Labs | Senior/Staff Software Engineer - AI / Agentic apps | 100% Remote (US + Canada) | Grafana Labs
Startups
- Founding Software Engineer Aglide
- Product Engineer (Founding team) Aglide
- AiMi | Full Stack AI Engineer | Remote(Everywhere) | Full-time AiMi
- Staff Software Engineer AiPrise
- ALBERT | REMOTE ALMOST ANYWHERE IN THE WORLD | Hiring principal and distinguished ALBERT
What the listing never says
- 26 bullet points. Long requirement lists deter qualified candidates, who read them as hard gates. Scope clarity
- No section describes what the person would actually do. Scope clarity
- No pay range published. Candidates cannot tell whether applying is worth their time. Pay transparency
The listing, marked up
Nothing in the wording of this listing tripped a check. The scores above still judge how complete and coherent it is.
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.
• Agentic coding is your daily workflow. You build with AI by default and you're faster because of it.
• Genuine drive. You build things because you can't not.
Why This Role Is Different
• No layers. You work directly with both founders, design, and growth, and decisions get made in the room, not in a Linear ticket.
• You own the surface customers actually see. Every win shows up in activation and retention the next week.
• We use Viktor to build Viktor. You ship the product using the product, every day.
• Real ownership: a surface of the company that customers depend on. When it wins, everyone knows whose work it was.
Even Better If
• You've founded something or been an early-stage builder.
• You've shipped something with real traction: users, revenue, downloads, a product people know.
• You've built growth loops (referrals, invites, lifecycle) in a PLG or B2B product.
• You've built with the AI tooling we live in and have opinions about it.
Tech
The product lives in Slack and Teams today, with web, desktop, and mobile apps on the way. TypeScript/React for the web, Python on the backend and agents, Modal for infrastructure. This role leans instrumentation and experimentation. You move across the stack, database included, when an experiment needs it.
How we work
Small team, high trust, low process. Decisions are made by owners, not committees. You will ship your first week. You will talk to users your first day.
We don't do alignment meetings or stakeholder syncs. We build things, see if they work, and iterate.
Why Viktor
We're one of the fastest-growing companies in the world. The product works. The market is pulling.
This is a rare window: everyone here owns a surface of the company that customers depend on. That doesn't last forever. Right now, it's still true.
Compensation
Top-of-the-market salary and the kind of ownership that only exists at this stage.
The best work happens when you're in the room. This role is Munich or Warsaw, or remote in Europe, and we bring the whole team together in person a few times a year.
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.
• Agentic coding is your daily workflow. You build with AI by default and you're faster because of it.
• Genuine drive. You build things because you can't not.
Why This Role Is Different
• No layers. You work directly with both founders, design, and growth, and decisions get made in the room, not in a Linear ticket.
• You own the surface customers actually see. Every win shows up in activation and retention the next week.
• We use Viktor to build Viktor. You ship the product using the product, every day.
• Real ownership: a surface of the company that customers depend on. When it wins, everyone knows whose work it was.
Even Better If
• You've founded something or been an early-stage builder.
• You've shipped something with real traction: users, revenue, downloads, a product people know.
• You've built growth loops (referrals, invites, lifecycle) in a PLG or B2B product.
• You've built with the AI tooling we live in and have opinions about it.
Tech
The product lives in Slack and Teams today, with web, desktop, and mobile apps on the way. TypeScript/React for the web, Python on the backend and agents, Modal for infrastructure. This role leans instrumentation and experimentation. You move across the stack, database included, when an experiment needs it.
How we work
Small team, high trust, low process. Decisions are made by owners, not committees. You will ship your first week. You will talk to users your first day.
We don't do alignment meetings or stakeholder syncs. We build things, see if they work, and iterate.
Why Viktor
We're one of the fastest-growing companies in the world. The product works. The market is pulling.
This is a rare window: everyone here owns a surface of the company that customers depend on. That doesn't last forever. Right now, it's still true.
Compensation
Top-of-the-market salary and the kind of ownership that only exists at this stage.
The best work happens when you're in the room. This role is Munich or Warsaw, or remote in Europe, and we bring the whole team together in person a few times a year.