You build and own the machinery behind Viktor's partnerships engine: the outbound motions that find creators and agencies, the CRM that holds the pipeline, and the attribution that proves any of it worked.
You ship with AI coding tools daily. That is not a bonus here, it is the expected way of working, and nobody will ask you to justify it.
Viktor is an AI teammate that lives in Slack, connects to 3,200+ tools, and does real work. 56,000+ workspaces have hired him. We raised a $75M Series A led by Accel in May 2026, and we are about forty people heading toward a hundred.
Partnerships is one of the fastest-compounding channels we have: hundreds of creators, multiple agencies, newsletter sponsorships and an ambassador program, with real budget behind them. What it does not have yet is infrastructure. Sourcing, enrichment, sequencing, CRM hygiene and attribution are held together by hand. That is the job.
Build and run automated outbound motions end to end: sourcing, enrichment, sequencing, reply handling, CRM sync, across email and social, with deliverability and dedup handled properly.
Own Attio as a system, not a spreadsheet with opinions. Data model, pipelines, enrichment on entry, automated stage transitions, hygiene and reporting, so pipeline state is always trustworthy.
Ship internal tools fast with AI coding tools: scrapers, scoring pipelines, dashboards, integrations across Attio, Modash, Dub, Sheets, email infra and Slack.
Keep partner and placement data flowing between systems, and extend our attribution so every motion is measurable through to signups and revenue.
Turn the team's recurring manual work into automations that Viktor or your scripts run on schedule, and maintain them like production systems.
You will not be asked to do core product engineering, run paid ads platforms, or make the commercial calls on partners. This seat is the infrastructure under the channel.
Show us things you built and shipped yourself, with what they produced attached. Meetings booked, replies, pipeline created. A tool tour is not evidence; a working motion with numbers behind it is.
We will ask you to open your own machine and build in front of us, with whatever AI tooling you normally use.
Day 30. Something you built is running unattended and producing replies.
Day 90. One outbound motion live and producing qualified partner replies weekly, with reply and booking rates reported. Attio is the single source of truth for the pipeline. Three recurring manual workflows are gone. Every active motion is measurable to signups.
And the real test: someone else could operate what you built from your docs alone.
You ship internal tools and automations with AI coding tools as your primary workflow, and you can demo real things you built solo and show how you got there.
You have built and operated outbound at volume, and you can talk deliverability, warmup, enrichment, dedup and reply handling with actual numbers.
You own a CRM as a system: objects, pipelines, automations, API. Attio ideally, but Clay, HubSpot or your own build all count if you rebuilt it rather than configured it.
You are comfortable with APIs and scripting in Python or TypeScript, and you have wired 3+ SaaS tools into one working pipeline with webhooks, scheduled jobs and error handling that survives contact with reality.
You measure your own work. You know what your automations returned.
You have worked inside the Clay ecosystem, or built the outbound stack at a seed to Series B B2B SaaS company solo.
You have run creator, affiliate or partner programs and know where that data gets messy.
You already use an agent to run parts of your own job.
You configure tools through UIs and file a ticket for anything that needs code.
You want product engineering, and GTM tooling is the way in.
You have played with AI tools but cannot point at something you shipped with them that ran in production for months.
Your outbound experience is volume without deliverability discipline.
You need someone to turn outcomes into tickets before you can start.
You are building GTM infrastructure at the company that makes the AI teammate, and Viktor is part of your toolkit rather than just the product you support.
No legacy systems, no committee. You own the stack.
The channel is already working and already attributed, so what you build shows up in signups and dollars within weeks rather than becoming a case for a channel.
As partnerships grows, the person who built its infrastructure is the obvious owner of GTM engineering company-wide.
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.
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.
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.
RevOps Roles analysis
Benefits, tools, and company context we extract from the full posting and classify, so you can scan in seconds what the write-up buries in prose.
Opens in a new tab
ViktorVIKTOR is a Dutch (Rotterdam-based) software company offering a low-code, Python-based platform that lets engineers build and share web apps and AI agents to automate technical workflows. It integrates with existing engineering software and targets AEC, engineering, and industrial firms.
Visit website