viktor - Agent Harness Engineer
Requirements
• Agentic coding. You're fully bought into AI-assisted development. Agents, parallelized workflows, whatever tools make you fastest. If that isn't already how you work, you'll be behind on day one. • Systems thinking. You make hard technical trade-offs and own them. You understand how things break at scale and design for it. Good judgment about what's worth doing well and what's worth doing fast. • Speed, with the bar up. You ship today, not Thursday. No enterprise engineering. No three-week review cycles. • Range. You can go from the agent runtime to a React component to a deployment script in an afternoon. Viktor's surface area is too big for specialists. • Genuine interest in how AI actually works. You've read papers. You've read other people's prompts. You have opinions about how evals should work. • Remote. You can work from the location of your choice. • Previous AI engineering experience: agents, harnesses, deep model understanding. • Previous founder or early-stage builder. You've worn every hat and liked it. • Open source contributions to the AI tooling we live in. • TypeScript/React on the frontend. Python on the backend and agents. Modal for infrastructure. You don't need to know all of it coming in. You need to learn fast. • 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.
Responsibilities
• Build the agent runtime. Sandboxed execution, tool orchestration, memory. The part of Viktor that turns a sentence in Slack into a real action against a real API. • Ship integrations. We connect to thousands of tools. Salesforce, Notion, Stripe, QuickBooks, HubSpot, Shopify, whatever customers ask for next. OAuth, webhooks, schema mapping, error handling. Each new integration unlocks a new shape of customer. • Run the infrastructure. Viktor handles 600K+ tool calls a day. Container orchestration, autoscaling, cost per task. You're the reason it stays fast and cheap. • Ship product. Features that go directly to users through Slack and Teams. You'll see people using what you built within hours. • Whatever needs building. Small team, large surface. You'll work on things that aren't in this document. • HOW YOU'LL KNOW YOU'RE SUCCEEDING • You're shipping to production every day, and the changelog has your name on it. • A feature you built is the reason a customer closed. • When Viktor breaks at 3am, you can fix it because you understand the system end to end. • Founders are writing less code because you've taken over surfaces they used to own.
Benefits
• No layers. You work directly with both founders on the surface that matters most. Decisions get made in the room, not in a Jira ticket. • The agent is the product. You're not bolting AI onto something — you're building the thing customers came for. Every reliability win, every new tool, every memory improvement 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. You learn what actually scales because the system tells you immediately. • The feedback loop is hours, not quarters. Ship in the morning, customer uses it in the afternoon, you see what worked by end of day. If that pace is what you've been missing, this is the room. • Previous AI engineering experience: agents, harnesses, deep model understanding, eval infrastructure. • Previous founder or early-stage builder. You've worn every hat and liked it. • Open source contributions to the AI tooling we live in. • TypeScript/React on the frontend. Python on the backend and agents. Modal for infrastructure. You don't need to know all of it coming in. You need to learn fast. • 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. • 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. • Competitive salary, meaningful equity, and the kind of ownership that only exists at this stage. • We're in Munich, New York, and Warsaw. Onsite preferred. The best work happens when you're in the room.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT