Operations Engineer

Viktor; Warszawa; On-site; PLN 180,000 - 300,000; Full time

Job summary

Viktor is seeking a technically oriented engineer to join the operations team and build the systems it runs on. You will transform memory-heavy, spreadsheet-based processes into automated software that scales.

In the first weeks you’ll shadow recruiters, finance, and HR, then start removing manual steps and expanding automation. You’ll connect tools like Slack, Notion, Google Workspace, and internal dashboards, creating the shortest path between recurring problems and their solutions.

Qualifications

• 3+ years building software in some form: engineering, internal tools, technical founder, or automation-heavy ops work.
• Think about three times the volume and what happens when the knowledge leaves.
• Genuine interest in understanding how other people work.
• Startup pace; you can thrive in a fast-moving environment.
• Warsaw, on-site at least part of the time.

Responsibilities

• Build the connective tissue that links Slack, Notion, Google Workspace, and other tools so data flows without manual input.
• Create internal tools like dashboards, portals, forms, and lightweight apps to solve recurring problems.
• Develop hiring infrastructure with automated pipelines, scorecards, and agency tracking.
• Improve finance systems for invoicing, contractor flows, and spend visibility.
• Automate employee lifecycle processes from onboarding to offboarding.
• Provide instrumentation so founders can answer questions with simple links instead of deep investigations.

Skills

Software development

Debugging

AI tooling familiarity

Systems thinking

Job description

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.

How we work.

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.

What we need.

• 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.