All jobs
What we're looking for
- Experience running a community for a product, ideally B2B SaaS, dev tools, or AI
- Ability to manage stakeholders in support, engineering, and product
- Experience in organizing events and building onboarding flows
- Technically curious and AI-native
- Strong writing skills
About the role
The Short Version
Thousands of people use the product 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 the 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 the product for us. You also sit at the centre 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
The product is growing fast. It 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, no community team above you, 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.
Organise 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. The community isn't just Slack. You'll moderate the Reddit presence, own review surfaces on 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. Onboarding flows, welcome sequences, 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 evangelising the product and give them a reason to do more: ambassador program, early access, spotlights, swag, referrals.
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 the product 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 and ambassador 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, public ratings are climbing, customer stories flow into marketing, and "the community" is something prospects hear about as a reason to choose the product.
Who You Are
You've run a community before — a Slack, Discord, forum, or subreddit for a product, ideally B2B SaaS, dev tools, or AI — and you can show what it looked like before you and after
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 the product actually does. AI-native.
A sharp writer. Clear, warm, fast. Short messages that land.
Comfortable in chaos. Small team, full ownership, no playbook. You decide and move.
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 travelled: 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.
Everyone here owns something real — not a task, but a surface of the company that customers depend on. When it breaks, you fix it. When it wins, everyone knows whose work it was.
Compensation
Competitive salary and meaningful equity at an early stage. Onsite preferred across our office locations — the best work happens when you're in the room.
Thousands of people use the product 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 the 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 the product for us. You also sit at the centre 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
The product is growing fast. It 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, no community team above you, 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.
Organise 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. The community isn't just Slack. You'll moderate the Reddit presence, own review surfaces on 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. Onboarding flows, welcome sequences, 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 evangelising the product and give them a reason to do more: ambassador program, early access, spotlights, swag, referrals.
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 the product 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 and ambassador 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, public ratings are climbing, customer stories flow into marketing, and "the community" is something prospects hear about as a reason to choose the product.
Who You Are
You've run a community before — a Slack, Discord, forum, or subreddit for a product, ideally B2B SaaS, dev tools, or AI — and you can show what it looked like before you and after
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 the product actually does. AI-native.
A sharp writer. Clear, warm, fast. Short messages that land.
Comfortable in chaos. Small team, full ownership, no playbook. You decide and move.
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 travelled: 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.
Everyone here owns something real — not a task, but a surface of the company that customers depend on. When it breaks, you fix it. When it wins, everyone knows whose work it was.
Compensation
Competitive salary and meaningful equity at an early stage. Onsite preferred across our office locations — the best work happens when you're in the room.
Compensation & benefits
Salary: Undisclosed
About TechTree's client
This innovative company 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.