Job description

THE SHORT VERSION Thousands of people use Viktor every day, and a lot of them are in our community Slack right now, asking questions, sharing workflows, hitting walls. You own that room, and every other place Viktor's community lives: Reddit, Trustpilot, G2, wherever the conversation goes next. You turn quiet lurkers into power users, and power users into the voices who sell Viktor for us. You also sit at the center of the company, pulling support, engineering, and product together so the community's needs actually get met. When the community is alive, people stay. When it goes quiet, they churn. You're the person who keeps it alive. WHAT'S ACTUALLY GOING ON HERE Viktor is growing fast. The product creates a flood of “how do I...”, “can it...”, “look what I built” energy, and right now nobody owns the channel where that energy lives. It's reactive, ad hoc, and the best customer stories never make it back to the team. That's the seat. First community hire. You report to our CMO, and there is no playbook to inherit. You decide what this function becomes. WHAT YOU'LL ACTUALLY DO - Run the community Slack. Own the room day to day. Answer fast, route the hard stuff, seed conversation, make sure no question dies unanswered. Set the norms, the channels, the culture. - Coordinate across the company. You sit between customer support, engineering, and product, and you manage those stakeholders. Route issues to the right owner, chase fixes to done, push the community's needs into the roadmap, and make sure the loop actually closes instead of dying in a thread. - Organize events and fuel grassroots movements. Founder AMAs, build-alongs, office hours, power-user roundtables, launches, run end to end. And the bottom-up stuff: local meetups, community-run challenges, and champions who want to host their own thing. You give grassroots momentum a backbone and the tools to grow. - Own the wider community footprint. Viktor's community isn't just Slack. You'll moderate our Reddit presence (a subreddit we'll launch), and own our review surfaces, Trustpilot, G2, and the rest. Run the campaigns that turn happy users into public proof at scale, and keep the rating climbing. - Activate people. Get signups into the community, lurkers into participants, participants into champions. In-community onboarding (channel norms, welcome threads), prompts, challenges, recognition, whatever moves people up the ladder. - Relay feedback to the team. You're the early-warning system. The bug everyone hits, the feature everyone asks for, the wall everyone slams into. You spot the pattern, write it up, and put it in front of the right people so it gets acted on. - Build the champion layer. Find the people already evangelizing Viktor and make them more visible: spotlights, member-hosted sessions, recognition. You work alongside the teammates who run our ambassador and early access programs. - Turn the community into content and proof. The best workflows, stories, and quotes become case studies, social posts, and launch fuel, with growth and marketing. THE BAR This role is judged on a living, growing, engaged community, not post count. “I replied to everyone” isn't the bar. “More people are getting more value from Viktor this month than last, the team knows exactly what customers need because of me, and our public reputation is climbing” is. HOW YOU'LL KNOW IT'S WORKING - 30 days. You know the room cold. Response times are tight, the dead channels are gone, and you've shipped the first version of onboarding for new members. The team is already seeing feedback summaries from you weekly. - 60 days. Active members are climbing, you've run your first event with real turnout, a champion layer is forming, and review volume on G2 and Trustpilot is up. Support, engineering, and product are moving against patterns you surfaced. - 90 days. The community is a growth and retention engine. Events run on a cadence, grassroots momentum is building, our public ratings are climbing, customer stories flow into marketing, and “the community” is something prospects hear about as a reason to choose Viktor. WHO YOU ARE - You've run a community before, a Slack/Discord/forum/subreddit for a product, ideally B2B SaaS, dev tools, or AI, and you can show what it looked like before you and after, and which number you personally moved. - Genuinely social online. You start conversations, you make people feel seen, you're funny in a thread. This can't be faked. - A coordinator who gets things done across teams. You can manage stakeholders in support, engineering, and product, hold them to commitments, and close loops without a manager pushing you. You're the connective tissue, not a bottleneck. - Operator, not just a vibes person. You run events, build onboarding flows, track engagement, and close the loop. You ship. - Technically curious. You can hold your own with technical users, read a workflow, and understand what Viktor actually does. You build with AI every day and can show what you built. - Quick to read a product and its users. You work out fast who our customers are and what they get stuck on. - A sharp writer. Clear, warm, fast. Short messages that land. - Comfortable in chaos. Small team, full ownership, no playbook. You decide and move. PROBABLY NOT A FIT IF - You can describe your last community's totals but not the number you personally moved. - You call yourself AI-native but have nothing you built with AI to show. - Community management, for you, mostly means moderation. - You would run the room like a social account, measured in posts and followers. - You bring the playbook from your last company and apply it before learning this room. - You find it hard to say no to the loudest requests in the room. EVEN BETTER IF - You've stood up a community function from zero, or been close to the first hire. - You've moderated a subreddit or forum, or run review-gen campaigns on G2, Trustpilot, or Capterra that moved the rating. - You've run an ambassador or champion program that moved a real metric. - You've grown grassroots, community-led events: meetups, user groups, or member-hosted sessions. - You've turned community moments into content that traveled: case studies, threads, videos. - You've worked with technical buyers and builders (devs, ops, marketers). WHY THIS ROLE IS DIFFERENT - You own a surface customers depend on, not a content calendar. The community is a real growth and retention lever, and it's yours end to end. - You're the customer voice inside the company. You sit between support, engineering, and product, and the founders read your feedback summaries. Roadmap decisions reference your notes. - The work is public. The community, the events, the Reddit threads, the reviews, it all goes out under your name as much as the company's. 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.

Requirements

Must-haves

Run the community Slack. Own the room day to day. Answer fast, route the hard stuff, seed conversation, make sure no question dies unanswered. Set the norms, the channels, the culture.
Turn the community into content and proof. The best workflows, stories, and quotes become case studies, social posts, and launch fuel, with growth and marketing.
30 days. You know the room cold. Response times are tight, the dead channels are gone, and you've shipped the first version of onboarding for new members. The team is already seeing feedback summaries from you weekly.
You've run a community before, a Slack/Discord/forum/subreddit for a product, ideally B2B SaaS, dev tools, or AI, and you can show what it looked like before you and after, and which number you personally moved.
Genuinely social online. You start conversations, you make people feel seen, you're funny in a thread. This can't be faked.
Operator, not just a vibes person. You run events, build onboarding flows, track engagement, and close the loop. You ship.
Technically curious. You can hold your own with technical users, read a workflow, and understand what Viktor actually does. You build with AI every day and can show what you built.
Quick to read a product and its users. You work out fast who our customers are and what they get stuck on.
A sharp writer. Clear, warm, fast. Short messages that land.
Comfortable in chaos. Small team, full ownership, no playbook. You decide and move.
You can describe your last community's totals but not the number you personally moved.
You call yourself AI-native but have nothing you built with AI to show.
Community management, for you, mostly means moderation.
You would run the room like a social account, measured in posts and followers.
You bring the playbook from your last company and apply it before learning this room.
You find it hard to say no to the loudest requests in the room.
You've stood up a community function from zero, or been close to the first hire.
You've moderated a subreddit or forum, or run review-gen campaigns on G2, Trustpilot, or Capterra that moved the rating.
You've run an ambassador or champion program that moved a real metric.
You've grown grassroots, community-led events: meetups, user groups, or member-hosted sessions.
You've turned community moments into content that traveled: case studies, threads, videos.
You've worked with technical buyers and builders (devs, ops, marketers).
You own a surface customers depend on, not a content calendar. The community is a real growth and retention lever, and it's yours end to end.
You're the customer voice inside the company. You sit between support, engineering, and product, and the founders read your feedback summaries. Roadmap decisions reference your notes.

Nice-to-haves

None flagged.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

restai

Platform: ashby
Effort: quick