Product Engineer

Role Description

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. If you've never shipped a product people love, this isn't the role.

What You'll Actually Do

• Ship user-facing product end to end. Frontend to backend, idea to production, in Slack, Teams, and the web app (incoming!).
• Own onboarding and time-to-value. From install to first real win in minutes, because the alternative is churn.
• 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.

The Bar

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

Qualifications

• You've shipped a real product that real people use, and you owned it end to end.
• Range: React component to API to deployment script in an afternoon.
• Product taste: You have opinions about UX, you know what good looks like, and your work shows it without someone handing you a design.
• You talk to users and own outcomes, not tickets.
• 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, 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.
• 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.
• 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 built with the AI tooling we live in and have opinions about it.

Tech

• TypeScript/React on the frontend.
• Python on the backend and agents.
• Modal for infrastructure.
• This role leans frontend and product, but 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.
• This role is remote-first, with hubs in Munich, New York, and Warsaw.
• We bring the whole team together in person a few times a year.