Product Engineer; On-site

The Short Version

You're the person who makes Viktor a product people love, not just a powerful one.

You've shipped real products that real users depend on, end to end, and you have taste: you know what good looks like and you won't ship less.

Viktor lives where work already happens, in Slack and Teams, with a web app on the way. People talk to it like a teammate, and the whole product is a conversation with an agent that 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  agent acts on its own and sometimes gets it wrong, and your job is to make people trust it with their real work anyway.

• Ship user-facing product end to end. Frontend to backend, idea to production, in Slack, Teams, and the web app (incoming!). 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.

• Design how people stay in control: a propose-and-approve flow that stops a bad action without burying people in confirmations, and surfaces that make the agent's actions legible and easy to steer.

• Talk to users and shape the problem. You don't wait for a spec. You find the rough edge, decide what to build, and build it.

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

• Whatever needs building. Small team, large surface.

You ship to production every day, and the changelog has your name on it. You have product taste and you defend it: you know when "it works" isn't done. You work backwards from the user, not forwards from the tech.

This role doesn't work without agentic coding fluency: if agentic engineering isn't already how you work, you'll be behind on day one.

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

• Product instinct. You use the product, talk to the people who rely on it, and have UX opinions your work shows without someone handing you a design.

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

• You've founded something or been an early-stage builder.

• Design sensibility. You can make it look and feel right, not just function.

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

The product lives in Slack and Teams today, with a web app on the way. Type Script/React for the web, Python on the backend and agents, Modal for infrastructure. This role leans product, and you move across the whole stack. You don't need all of it coming in, but you need to learn fast.

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. Munich, New York, and Warsaw. Remote for some roles.