Product Engineer

Job description

THE SHORT VERSION Half product manager, half engineer. You imagine how people work with an AI teammate, and how they'll manage a whole team of AI employees, then decide what to build and build it yourself. You've shipped real products end to end, you have taste, and you sweat the details. 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 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 at all. The agent acts on its own and sometimes gets it wrong, and your job is to make people trust it with their real work anyway. Nobody has settled what the UX of working with AI employees looks like. You'll have to imagine it: how a person delegates, steers, corrects, and trusts an AI teammate, and how they run a whole team of them. 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. - 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. 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. - 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 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. 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. 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 product, and you move across the whole stack. You don't need all of it coming in, but you need to learn fast. 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 something real. Not a task. 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.