Viktor - Agent Harness Engineer (On-site)
Requirements
• 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. • Onsite. This is an in-office role, not remote.
Responsibilities
• Previous AI engineering experience: agents, harnesses, eval infrastructure. • Previous founder or early-stage builder. • Open source contributions to the AI tooling we live in. • Python. No agent framework, no orchestration library. We build the harness ourselves, from the loop up. • 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.
Benefits
• 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. 1.5M+ 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. • 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 • 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. • We're one of the fastest-growing companies in the world. The product works. The market is pulling. • This is a rare window: everyone here owns something real. Not a task. A surface of the company that customers depend on. • That doesn't last forever. Right now, it's still true. • Top-of-the-market salary and the kind of ownership that only exists at this stage. • The best work happens when you're in the room. Munich, New York, and Warsaw. Remote for some roles.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT