Product Engineer

About the role

THE SHORT VERSION

Half product manager, half engineer. You imagine how people work with an AI employee, and how they'll manage a whole team of them, 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 him like a colleague, and the whole product is a conversation with an AI employee who 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. Viktor acts on his own and sometimes gets it wrong, and your job is to make people trust him 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 employee, 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.

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

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.