Viktor is the AI employee that lives in Slack and Microsoft Teams. It takes on the repetitive work so people do the work only people can. We’re growing fast. The bar doesn’t move.
See the open roles
We hire exceptional people and give them room to do exceptional work. We’re kind but direct, we challenge each other without ego, and we care more about getting to the right answer than being right. Everyone owns the outcome.
27 roles
Engineering · Warsaw / Munich
Engineering · Remote
Engineering · Warsaw / Munich
Engineering · Warsaw / Munich
Engineering · Warsaw / Munich
Product · Warsaw / Munich
Product · Warsaw / Munich
Product · Warsaw / Munich
Product · Warsaw / Munich
Growth · Warsaw / Dublin / New York
Growth · Warsaw
Growth · Warsaw / Dublin / New York
Growth · Warsaw
Growth · Warsaw
Growth · Warsaw / Dublin / New York
Growth · Warsaw
Growth · Warsaw / Dublin / New York
GTM · Warsaw / Dublin
GTM · Warsaw / Dublin
GTM · New York
Ops & People · Warsaw
GTM · Warsaw
Ops & People · Warsaw
Ops & People · Warsaw
GTM · Warsaw / Dublin
Ops & People · Warsaw
Ops & People · Warsaw
Scroll to explore all matching roles.
Roles come directly from our job board and refresh every 10 minutes. Applications are submitted securely through Ashby, not this page.
Join the Viktor talent community. Tell us which team you’d want to join and you’ll hear first when a role opens there, before it goes on the board. In between, we’ll send you what that team shipped and who joined it.
Engineering at Viktor means the thing you ship on Tuesday is doing someone's job on Wednesday, inside a company you have never heard of.
Engineering builds the employee itself: the harness, memory, evals and integrations that let one agent do real work for thousands of teams. It is model-agnostic by design, so the engineering is in the machinery around the model. Reliability is the product.
There is no reference architecture to copy. An agent doing real work fails in ways no textbook covers, and you debug failures that happen inside a model's judgement, not just in your code.
Week one you have a PR in production. Week two you own a surface: a workstream lead hands you a whole system. Week four a customer's Slack is running code you wrote, and when it breaks at 11pm you can see exactly why in the logs.
→ Around 350 pull requests merge to production every week. A product engineer who joined in August had 63 of them in his first four weeks.
→ The Viktor that posts in our own Slack, asking engineers to record their demos, was built at the July hackathon. It's still running.
→ A product you can use today went from company dogfooding to public launch in three days.
The whole process, published. Later steps vary a little by role.
Apply on the role’s page. Send a CV, links to work you have shipped, or both.
Twenty minutes with our recruiter. A high-level check that the role, the timing and the ambition line up on both sides. Honest both ways: if it’s not a fit, we say so now rather than three rounds in.
Engineers write code live, without an agent, on a problem we set in the session. Commercial and ops roles walk us through real work you’ve built or run and the decisions that were yours. Either way, you show us rather than tell us.
Someone senior in your discipline, a senior engineer for engineering roles, a lead for sales, tests the depth of your craft and how you think about the system around it. No LeetCode, no trivia. We’re looking for where your expertise runs out, because that tells us more than where it doesn’t.
For roles where it’s part of the process: a session on real work with the team you’d join. It’s for both of us. You find out what the job is actually like; we find out what it’s like to work with you.
A person makes the call, and you hear back either way with real feedback.
One route, kept simple: apply on the role’s application page. What you send with it is up to you.
The traditional route works. We read it for the things you built, and how far you took them.
Links beat bullet points: a repo, a shipped product, a campaign, a channel you grew. Tell us which decisions were yours.
A short note on why this role, plus the work that backs it up, is the strongest application you can send.
People read applications and people make the hiring calls, whether you apply on day one of a posting or later.
View all open roles
No stock photos here. This is the actual team, in the actual office, plus the offsites and detours that come with working somewhere this small and this fast.
One mission: give every company an AI employee that lives in Slack and Microsoft Teams, connects to their tools, and does the work. And yes, it’s Viktor with a k, even if you searched for Victor AI.
4.9 on G2We are hiring across engineering, product, growth, sales and operations. If you want to work on the AI employee itself, start with the open roles.
