Viktor - Product Engineer (On-site)
Requirements
• 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.
Benefits
• 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 • Even Better If • 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. 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 • 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. • 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. • 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, Dublin, and Warsaw. Remote for some roles.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT