Product Marketing Manager

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 role in one line You own how Viktor shows up in the world. Positioning, launches, and the long-form work that names what we're building. You write the LP, the ad, the X thread, and the essay, and you orchestrate the launch motion that puts them in market on the same day. You ship every week. What's actually going on The product works. Teams that try Viktor keep using Viktor. The bottleneck isn't belief. It's language. In May 2026 we closed a $75M Series A led by Accel, with Slack's founders co-investing. The fuel is there. What's missing is the person who turns the product into language the market can carry. We're mid-sequence on vertical sub-launches across the ICPs we sell to today, with more queued for the rest of the year. Each one needs its own positioning, hero story, and proof. Behind those sits the biggest narrative we'll ship this year. The category doesn't have language for it yet. The person who takes this seat writes it. Positioning lives in a few heads and gets produced ad hoc across the team. Nobody owns it end to end. That's the seat. Founding PMM. No PMM above you. No playbook to inherit. Why this role is different The biggest launch of our year is yours. Positioning, launch motion, the essay that names the category. One launch a year matters more than the rest of the year combined. This is that launch, and it lands on your desk. The work is public. Essays, threads, LPs, PR. What you write goes out under your name as much as the company's. PMMs at this stage usually live in slide decks. Here the surface area is the open internet. Narrative is treated as strategic. The founders see writing as leverage, not as a support function. You will spend zero hours convincing anyone that this matters. First hire is yours inside six months. Likely a writer or a launch PM. Your call on sequencing, your call on who. What you'll actually do Own positioning across our ICPs. Media Buyer, CSM, AE, ecom operator, agency owner, plus whoever comes next. Pain framework, jobs-to-be-done, what loses the deal, what wins it. Refreshed off real customer evidence on a quarterly cadence. Run the launch motion. Every meaningful product moment (major launches, vertical positioning, model upgrades, connector classes, pricing) gets a narrative doc first, then a coordinated launch across LP, paid, organic, PR, and sales. You write the narrative, you sequence the surfaces, you decide when we go. Write the long-form. Roughly one deep essay every two to three weeks, in the Anthropic and Linear register. Positioning theses, category doctrine, post-mortems of Viktor deployed at real customers. These travel further than ads, and they recruit talent and capital, not just users. Hold the competitive line. Glean, Harvey, ChatGPT Enterprise, Cognition, n8n and Make-as-AI, vertical agents, and the "Slack bot built in a weekend" objection. Battlecards live, refreshed as needed. Sales reads them weekly. Live with product and the founders. 30%+ of your week with product, engineering, and the founders. PMM at an AI company that ships weekly cannot live in a slide deck. How you'll know it's working 30 days. Positioning shipped for two active ICPs. First long-form essay live. Competitive baseline written. First customer case study end to end. 60 days. A third ICP positioned. First major narrative essay published. Active verticals refreshed across LP and paid. Three customer stories in market. 90 days. Positioning ready for the next wave of sub-launches. Cadence established: one deep essay every two to three weeks, weekly competitive refresh, narrative review on every paid surface. The big launch of the year is on rails. Who you are You've personally written and shipped a launch narrative at an AI, dev tools, or PLG SaaS company that scaled to millions of users or hundreds of millions in ARR. You can bring the artifact and tell us what it returned. You've owned positioning across three or more ICPs at one company. You can walk through the framework you use to keep them distinct. You write the essay, the LP hero, and the X thread. Three different muscle groups, same person. You have samples in all three. You hold a clear point of view on the AI coworker category and where it goes: horizontal vs vertical, agentic vs assistive, platform vs single-product. We don't expect you to agree with our current take. We expect you to have one. You use AI heavily and well, for first drafts, call synthesis, competitive crawl, variant generation. PMM at an AI company that doesn't is a no-hire. Comfortable in Notion, Linear, PostHog, Hex, and basic SQL, or willing to learn fast. We don't gate on toolkit. Bring the work. Even better if You've held a founding PMM seat at a Series A or B AI company. Scope here assumes solo. You've launched a marketplace, app ecosystem, or platform end to end. You've done vertical SaaS positioning reps in any of our verticals: Media Buying, RevOps, CS, ecom, agency. You came up as a journalist, technical writer, or research-org comms. Long-form essay craft is real and hard to fake. How we work Small team, high trust, low process. Decisions are made by owners, not committees. You will ship in your first week. You will talk to users your first day. Few alignment meetings, no 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 write 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 the founding stage. Onsite preferred at one of our hubs. We'll consider remote for the right person. 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.