Remote Lazy Person Jobs (NOW HIRING)

About Viktor
Viktor is the AI teammate. 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.
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 have opinions about what makes them work. You ship the day you write the code and reach for AI-assisted development by default. If you've never built an agent, this isn't the role.
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, and your job is to make it happen more often, more reliably.
Viktor handles 600K+ tool calls a day and the curve is steep. We connect to thousands of tools: Salesforce, Notion, Stripe, QuickBooks, HubSpot, Shopify, whatever's next. You'll work next to both founders, own a real surface of the product, and ship to production the same day you write the code.
What You'll Actually Do

• Build the agent runtime: sandboxed execution, tool orchestration, memory, and the loop where the agent checks its own work.
• Ship integrations. OAuth, webhooks, schema mapping, error handling. The bar is that it works on the customer's real data on day one, not a fixture.
• Run the infrastructure. Container orchestration, autoscaling, cost per task.
• Ship product. Features that reach users through Slack and Teams within hours.
• Whatever needs building. Small team, large surface.

The Bar
You ship to production every day, and the changelog has your name on it. When Viktor breaks at 3am, you can fix it because you understand the system end to end. This role doesn't work without agentic coding fluency: if AI-assisted development isn't already how you work, you'll be behind on day one.
Day-1 Reality
Week 1: ship something to production and take ownership of a live surface.
Who You Are

• You've personally built or significantly modified an AI agent harness, and can describe the trade-offs you made.
• You've made an agent reliably close the loop: tests, linters, typecheckers, browser verification, whatever stops it hallucinating success.
• You've built custom skills, commands, CLIs, or MCP servers to make your own agentic coding faster.
• Agentic coding is your daily workflow, and you've stress-tested models and harnesses across the frontier.
• Systems thinking. You make hard technical trade-offs and design for how things break at scale.
• Speed, with the bar up. You ship today, not Thursday.
• Range. Agent runtime to React component to deployment script in an afternoon.
• Genuine interest in how AI works. You've read the papers and have opinions about evals.
• Remote. Work from wherever you're sharpest; we default to async and gather in person a few times a year.

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.
• The agent is the product. Every reliability win shows up in retention the next week.
• Volume that forces you to be good. 600K+ tool calls a day means the lazy answer breaks in production immediately.

Even Better If

• Previous AI engineering experience: agents, harnesses, eval infrastructure.
• Previous founder or early-stage builder.
• Open source contributions to the AI tooling we live in.

Tech
TypeScript/React on the frontend. Python on the backend and agents. Modal for infrastructure. 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.
Everyone here owns something real. Not a task. A surface of the company that customers depend on. When it breaks, you fix it. When it wins, everyone knows whose work it was.
We use Viktor to build Viktor. You'll see what you're working on in action every day.
Why Viktor
This is a rare window. The product works. The market is pulling. The team is small enough that what you do next week will be live in production next week. That doesn't last forever. Right now, it's still true.
Compensation
Competitive 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.