Operations Lead
TLDR
Own end-to-end, cross-functional operational streams across product, growth, finance, people, and customer ops to drive work from brief to done.
About Viktor
Viktor is the AI teammate. It lives in Slack and Microsoft Teams, connects to thousands of tools, and does real work for real companies: finance, marketing, ops, engineering. We're building the product that replaces half the SaaS stack.
The team is small. The scope is not.
The Short Version
You're the person who gets things done. When work needs to move (a vendor chased, a contract pushed to signature, a new office registered in a new country, a customer ticket answered, a new hire's first week running on autopilot), it lands with you and it closes. Quietly, quickly, correctly. You don't wait to be asked twice.
The work shifts week to week: one morning it's product ops across Viktor and Jace, the afternoon a growth experiment to coordinate and a vendor invoice that won't pay itself, the next day standing up entity registration in a new country.
What's Actually Going On Here
We're 19 people across Warsaw and Munich, scaling fast post-Series A. The Chief of Staff and Co-Founder are running too much of the operational work themselves, across product, growth, finance, people, and customers. That's the bottleneck we're hiring against. You own live operational workstreams across the company and run them to done.
What You'll Actually Do
The scope is broad on purpose. You'll work across:
Product ops. Non-technical coordination across Viktor and Jace: releases, cross-team threads, the connective tissue between product, growth, and engineering.
Growth ops. Logistics behind campaigns, partnerships, and experiments. Briefs to execution.
Financial ops. Vendor onboarding, expenses, invoices, signatures, document filing, working alongside our accounting and legal stack.
People ops. Hiring execution end-to-end and new-hire onboarding logistics so first weeks run without anyone babysitting them.
Customer ops. Learn both products cold, then own response quality and speed across all channels.
Company ops. Setting up offices, registering the company in new countries, internal processes that let us scale past 15, events and offsites booked end-to-end.
What ties it together: you take a brief, come back with a recommendation, and execute. You don't hand work back up, and you fill gaps before anyone names them.
The Bar
This role is judged on closure rate, not effort. You'll be measured on how many threads you're driving, how fast they close, how clean the handoff is when something leaves your desk, and how often anyone has to ask twice. The target is zero.
How You'll Know It's Working
30 days. A steady portfolio of threads closing each week. Friday summary going out: what closed, what's in flight, what's blocked.
60 days. Live work routes to you, not around you. Customer response quality and speed visibly up. External initiatives (events, partner work, country expansion) land on time.
90 days. You're the operational backbone. The founders spend materially more time on product and strategy. New hires have a first week that runs on autopilot.
Who You Are
Bias to action. You'd rather start, learn, and adjust than wait for a perfect brief.
Adaptable. Five live threads in a single morning, none dropped.
Highly organized. You run systems, not memory.
Proactive. You see a gap and fill it without being told.
Low-ego and impossible to derail. You handle the unglamorous stuff with the same care as the visible stuff.
Strong written and spoken English. Polish is useful. Warsaw-based, in the office five days a week.
No specific years of experience required. We care about evidence you get things done.
AI-native. You'll use Viktor and Jace as your real daily workflow, not a demo.
Even Better If
You've run ops in a high-volume, high-growth environment: founder's office, bizops, recruiting, agency coordination, conference ops.
You've built a process from scratch that someone else inherited and didn't have to rebuild.
You've helped a company expand into new countries or set up new offices.
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.
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.
Why Viktor
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.
Compensation
Competitive salary 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.
Viktor builds an AI coworker that integrates seamlessly into Slack and Microsoft Teams, connecting with thousands of tools to assist companies in finance, marketing, operations, and engineering. By streamlining processes, Viktor aims to replace a significant portion of the SaaS stack with a single, intelligent teammate.