Operations Engineer

We're hiring someone technical to work inside the operations team and build the systems it runs on.

You'll sit inside the operations team - hiring, finance, legal, people, vendors - and turn the parts that run on memory, spreadsheets and copy-paste into systems that run themselves. This isn't a support role for ops. It's an engineering role pointed at ops.

You'd spend your first weeks sitting with the people doing the work: recruiters, finance, people ops. After that you'd start replacing the parts that shouldn't need a person, and keep going.

What You'll Build

The connective tissue - Slack, Ashby, Mercury, Notion, Attio, Linear, Google Workspace, wired together so data moves without a human moving it.

Internal tools - dashboards, portals, forms, small apps. Whatever's the shortest path between a recurring problem and it being gone.

Hiring infrastructure - pipeline automation, scorecard flows, agency tracking, status visible without anyone asking.

Finance systems - invoice and contractor flows, reconciliation, spend visibility, month-end that doesn't eat a week.

Employee lifecycle - onboarding and offboarding that provision, brief and revoke without a checklist someone has to remember.

Instrumentation - if a founder asks how long something takes or what it costs, the answer is a link, not an investigation.

Why This Role Is Different

Nobody hands you a backlog. You find something slow, decide it's worth fixing, build it, and tell us after. Rough and shipped this week beats polished next month, provided you own it once it's live and notice yourself when it breaks.

Who You Are

You write code and can debug it. We use AI tools heavily and expect you to, but they don't replace knowing what the code does.

3+ years building software in some form: engineering, internal tools, technical founder, or ops work that was mostly automation.

You think about what happens at three times the volume, and what happens when the person who knows how it works leaves.

Genuine interest in other people's jobs. Much of this role is asking someone why they do it that way.

Startup pace, or a convincing reason you'd be fine with it.

Warsaw, on-site.

Useful, not required: internal tooling at a startup, LLM APIs or agent frameworks in production, exposure to finance or recruiting.

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

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. Munich, New York, Dublin, and Warsaw. Remote for some roles.