About the role
Viktor is the AI coworker. It lives in Slack and Microsoft Teams, connects to thousands of tools, and does real work for real companies: finance, marketing, ops, engineering. We're building the product that replaces half the SaaS stack with a single teammate.
The team is small. The scope is not.
The Short Version
You're the person who makes Viktor do more things, for more customers, more reliably. You've built agents before — runtime, tools, memory, evals — and you have opinions about what makes them work. You ship to production the day you wrote the code, you're fluent in agentic coding workflows, and you reach for AI-assisted development by default because that's how you're fastest.
If you've never built an agent, this isn't the role. We're hiring people who already have the muscle and want to build the agent everyone else will try to copy.
What's Actually Going On Here
Someone in Slack asks Viktor to reconcile their Stripe payouts against their books. Viktor does it, live, in under a minute. The customer tells their network. Two more teams sign up that week. That's the loop. Your job is to make it happen more often, across more surfaces, more reliably.
Viktor handles 600K+ tool calls a day and the volume curve is steep. We connect to thousands of tools — Salesforce, Notion, Stripe, QuickBooks, HubSpot, Shopify, whatever customers ask for next. Each new integration unlocks a new shape of customer. Each reliability win compounds.
What You'll Actually Do
- Build the agent runtime. Sandboxed execution, tool orchestration, memory, the closed loop where the agent checks its own work. The part of Viktor that turns a sentence in Slack into a real action against a real API — and verifies it landed.
- Ship integrations. OAuth, webhooks, schema mapping, error handling. Each new integration unlocks a new shape of customer. The bar is that it works on the customer's actual data on day one, not on a fixture.