Skip to content

Agent Harness Engineer

ViktorWarsaw or Munich onsite

First seen Apr 29 · open 206 days · posted onceNo pay listed

HirQ verdict

44/100 · Weak. Based on age, reposts, pay, the company's hiring and ghost signals.

Medium ghost risk
True age
206 days
Reposts
Posted once

See the evidence behind this score.

Pro shows each part of the score, the reasons, the pay percentile and the listing history.

HirQ's ghost-risk estimate and company labels are automated opinions based on what we observe on employers' public job boards: how long a listing has been open, whether it was re-listed, wording in the description, and how often roles on that board close. They are not statements about an employer's intent, and a high-risk listing can still be a real opening. Figures are as of the date shown. How we measure

At a glance

Pay
No pay listed
Level
Mid level
Type
FullTime
Team
Product & Engineering
Work setup
On-site

Viktor hiring

Company page
SlowingHiring48· WeakStaffing & Recruiting
Open roles
22
New in 30 days
3
Closed in 30 days
12
Hiring trend, 13 weeksPro
Follow-through: ••%Pro

About the role

From Viktor's careers page, checked Nov 22

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 agentic engineering by default. If you've never built an agent, this isn't the role.

THE HARD PART

We're building a harness ready for AGI. Models keep getting better on their own; the harness decides how much of that intelligence turns into real work. Viktor shouldn't wait to be handed tasks. It should explore what a company is doing and automate it on its own.

Getting there is context engineering at the frontier: how the system prompt, skills, memory, and tools interact on diverse, complex problems, and how that interplay holds up across the real work of tens of thousands of workspaces.

WHAT YOU'LL ACTUALLY DO

  • Build the agent runtime: the loop where it plans, acts, and verifies its own work instead of declaring success it didn't earn.
  • Engineer the context: shape how the system prompt, skills, memory, and tools combine, and how the agent holds up when problems get diverse and complex.
  • Make the agent fluent with tools: composition across many integrations, recall, and the skill files that keep the right functions at hand.
  • Grow what the agent can do: memory it can trust, skills it writes for itself, work it runs on its own.
  • Make it measurably better: evals, catching regressions, and turning every failure into a fix.
  • Ship product: features that reach users through Slack and Teams within hours.
  • Whatever needs building. Small team, large surface.

WHO YOU ARE

  • You've personally built or significantly modified an AI agent harness, and can describe the trade-offs you made.
  • You understand how an agent's system prompt, skills, and tools interact on diverse and complex problems, and you've tuned that interplay yourself, not just read about it.
  • 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.
  • Genuine interest in how AI works. You've read the papers and have opinions about evals.
  • Munich or Warsaw, or remote in Europe.

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.
  • Frontier work. You're building a harness at the edge of what's currently possible, experimenting with agents that can take on full responsibilities, not just tasks.

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

Python. No agent framework, no orchestration library. We build the harness ourselves, from the loop up.

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.

WHY VIKTOR

Singular focus: we're building a harness that can hold an AGI-level model and make it useful for everyone.

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.

COMPENSATION

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. This role is Munich or Warsaw, or remote in Europe, and we bring the whole team together in person a few times a year.

Skills mentioned

  • Python
Apply on Viktor's siteOpens Viktor's own application page.

Similar jobs

Same role or field, nearby or remote, ranked by HirQ score.

More at Viktor

All roles

Keep exploring

Agent Harness Engineer

No pay listed · HirQ 44

Apply