Executive Assistant

Viktor is the AI coworker. 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 with a single teammate.

The team is small. The scope is not.

The Short Version

You're the person customers reach when they need help, and you're the person who makes sure they get more out of Viktor every week than they did the week before. When a workspace goes quiet, you notice. When a power user hits a wall, you unblock them. When something breaks, you're already on it before the second message lands.

The work shifts between firefighting and building. One morning you're walking a new admin through their first workflow, the afternoon you're debugging an integration with engineering, the next day you're writing the onboarding guide that didn't exist yet. You move between technical depth and customer empathy without losing either.

What's Actually Going On Here

We're a small team across Warsaw and Munich. Viktor is live with customers and growing fast. Customers churning quietly because no one caught the signal is the failure mode we're hiring against.

That's the seat. You own the customer relationship from post-sale onward and you make Viktor stick.

What You'll Actually Do

The work spans onboarding (getting new workspaces from signup to real daily usage), technical support (triaging issues, reproducing bugs, working with engineering to close them), account management (regular check-ins, usage reviews, expansion conversations), enablement (workflows, templates, internal champions), churn prevention (spotting drop-off early and acting on it), and feedback loops back to product (real customer pain, prioritized and written up so engineering can act on it).

What ties it together: you treat every customer like the product depends on them, because it does. You don't pass tickets around — you own them until they close. You spot patterns across accounts and turn them into things that scale: playbooks, docs, automations.

The Bar

This role is judged on retention, expansion, and customer signal - not ticket volume. You'll be measured on net revenue retention, time-to-value for new customers, response and resolution times, and how much useful product feedback you push back into the team. "I got back to them" isn't the bar. "They're getting more out of Viktor this month than last" is.

How You'll Know It's Working

• 30 days. Customers know who to ping. You've shipped the first version of onboarding and a usage dashboard you actually look at.

• 60 days. Response times are tight, churn signals get caught early, and engineering is shipping fixes against issues you've scoped and prioritized. Customers describe the support experience as a reason they stay.

• 90 days. You're the customer voice inside the company. Product roadmap decisions reference your notes. Expansion conversations are happening on accounts that would've quietly churned otherwise.
  

Who You Are

• Problem solver. You don't escalate things you could figure out. You read the logs, reproduce the bug, try the workaround, then bring engineering a clean repro.

• Customer-obsessed without being a pushover. You push back on bad-fit asks. You say no when no is the right answer.

• Technically curious. You don't need to be an engineer, but you can read an API doc, understand a webhook, and hold your own in a technical conversation. AI/SaaS background is a strong plus.

• Comfortable in chaos. Startup, small team, full ownership — you've done this or you're clearly built for it. No playbook to inherit, you write your own.

• Strong written and spoken English. Every customer interaction is in English. Warsaw-based, CET, in the office regularly.

• Experience in CS, AE, customer support, or technical support engineering — ideally at a software or AI company. We care more about evidence you've owned customers end-to-end than the job title.

• AI-native. You use tools like Claude or Viktor as your actual daily workflow.
  

Even Better If

• You've been the first CS hire somewhere before, or close to it — built the function rather than inherited it.

• You've worked with technical buyers and admins (devs, IT, ops leads) and can speak their language.

• You've shipped customer-facing docs, in-app guides, or onboarding flows that materially moved a metric.

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, meaningful equity, 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.