Product Engineer

What You'll Actually Do

• Imagine and define the UX of managing AI employees: delegation, steering, trust, cost, oversight. These patterns don't exist yet; you set them, then build them.

• Ship user-facing product end to end. Frontend to backend, idea to production, in Slack, Teams, and the web, desktop, and mobile apps as they land. The bar is something real users touch on day one, not a prototype.

• Own onboarding and time-to-value. From install to first real win in minutes, because the alternative is churn.

• Own what happens after you ship. Find where users stall, fix it yourself, and move activation and retention.

• Own land-and-expand: how Viktor spreads from the first user to their team and across the company.

• Do the PM half yourself. Talk to users, shape the problem, decide what to build, write the spec when it helps and skip it when it doesn't.

• Polish like it matters. The details that separate a tool people tolerate from one they recommend.

• Whatever needs building. Small team, large surface.

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 polish win shows up in retention the next week.

• New surfaces to explore. The web app is the start of a bigger chapter, with desktop and mobile apps after it, and you'll help define what Viktor feels like on each.

• We use Viktor to build Viktor. You ship the product using the product, every day.

• Real ownership. Not a task. A surface of the company that customers depend on. When it wins, everyone knows whose work it was.

Who You Are

• 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.

• Range. React component to API to deployment script in an afternoon. The frontend/backend divide was never useful to you.

• Half PM. Product discovery, UX judgment, and prioritization are core skills, not side interests. You use the product, talk to the people who rely on it, and work backwards from the user.

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

• Design sensibility. You can make it look and feel right without a designer holding your hand.

• 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.

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

• 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.

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 moved a real metric, activation, retention, or conversion, and have the before-and-after to show it.

• You've built with the AI tooling we live in and have opinions about it.

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.