Technical Content and Community Lead

The role

Enclave is a Zero Trust Network Access platform built specifically for MSPs.

The product works. Customers like it. But VPN servers are under constant attack, MSPs still rely on them, and not enough of them know there is a better option. Zero Trust Network Access replaces the VPN. Right now it’s a competitive differentiator for MSPs, not yet a baseline expectation. That window won’t stay open forever.

This is our first dedicated GTM hire. You’ll work directly with the founders to make Enclave known, understood, and talked about among MSP technical leaders and engineers, including those who aren’t yet looking for a new way to connect to customer sites. When they are ready to evaluate it, they should be able to find the information they need and recommend it to their customers.

Your job is to work out which people, communities and conversations matter in the MSP ecosystem, earn Enclave a place in them, and create technical material worth distributing through those networks.

This is not a conventional marketing role.

We are not looking for someone to execute predefined campaigns inside an existing GTM machine. We’re looking for someone who naturally spots weak surfaces, loose ends, distribution opportunities, and friction points, and improves them.

If the website is unclear, you improve it. If technical buyers keep asking the same questions, you create the resource that answers them properly. If MSP conversations are stalling, you figure out why. If there’s a distribution opportunity nobody is pursuing, you explore it.

You need to understand the product deeply enough to own how it’s positioned and presented, commercial enough to run a partner call, and pragmatic enough to automate whatever you keep doing twice.

What you’ll do

TL;DR: You’ll grow the audience for Enclave among the right MSP people and make it easier for them to understand, evaluate, and recommend it.

That starts with showing up where MSP engineers already talk, building relationships, and earning their attention and trust. You’ll:

• Participate regularly in practitioner communities: Reddit, Slack groups, forums, Discord. Reply to threads, answer questions, and contribute to conversations beyond our own product
• Build relationships with influential MSP operators and technical leaders, peer groups, podcast hosts, newsletter editors, publishers, event organisers, and practitioner communities
• Earn opportunities for Enclave and our technical work to appear in those networks through guest contributions, interviews, talks, joint investigations, and recommendations from peers
• Develop original technical investigations, experiments, and recurring editorial formats that MSP practitioners would find interesting even when they aren’t evaluating Enclave. Topics might include access practices, customer isolation, or the operational cost of network complexity
• Build a deeper model of MSP practitioners, distinguishing engineers, technical leaders and owners by the problems and behaviours that signal relevance. Use it to shape topics, formats and distribution
• Orchestrate owned, community, earned and partner channels into a coherent distribution system, each with a deliberate purpose rather than reposting the same material everywhere

Useful technical material gives you something worth bringing to those conversations and helps interested MSPs take the next step. You’ll create written and video material including:

• tutorials
• implementation guides
• troubleshooting walkthroughs
• architecture explainers
• onboarding material
• technical essays and long-form written content
• short-form demos and technical videos
• documentation improvements
• partner-facing enablement material

Write and speak like a technically competent peer: useful, direct and credible beats polished marketing production. Help MSP engineers do their jobs better while showing them why Enclave matters.

We’re a small team. Use AI and automation for research, iteration, repurposing, analysis and operational leverage. You retain ownership of strategy, positioning, voice and final editorial decisions. The output must be informed, researched and accurate. No slop.

To help that wider audience find answers, evaluate Enclave, and get it working, you’ll also:

• Own, optimise, and steer how Enclave presents itself online. That includes enclave.io, our ZTNA microsite, and how we show up in search results and AI answers
• Handle inbound conversations, qualify interest, run demos, and move commercial conversations forward
• Record demos and walkthroughs so partners can evaluate Enclave and show it to their customers without waiting for us
• Get close enough to partners to understand what blocks adoption, what they need to sell confidently, and where our positioning is not yet landing. Help them explain Enclave to their end-customers and understand how it fits alongside other technologies they use
• Help triage and participate in support conversations with partners and customers via Slack and email
• Build lightweight systems and automation around engagement, outreach, and content workflows
• Feed what you learn back into product, helping improve onboarding and the new-user experience

Longer term, there’s scope to build an MSP certification programme, launch a community writing programme, grow the content library into a structured learning resource, and start building a team around you. Those come after the foundations are laid, and how far this role goes depends on what you make of it.

What success looks like

We judge success by audience penetration and meaningful downstream behaviour, not content volume, impressions or follower growth:

• More of the right MSP engineers and owners knowing Enclave exists and understanding where it fits, including people who weren’t already looking for it
• Repeated exposure among target MSPs through participation in trusted conversations and invitations into communities, podcasts and events
• MSP engineers and owners referring Enclave to one another, whether that’s in forum posts, Reddit threads, or word of mouth
• Useful technical material being discussed and distributed beyond Enclave’s own website and channels
• Growth in branded search, qualified inbound conversations and demo requests, with evidence of influence on pipeline
• Better follow-through and conversion from existing market interest because you built the systems and habits to progress conversations
• Partners and MSPs becoming more self-sufficient over time because the content, documentation, and tooling you helped shape means they don’t need to ask us
• LLMs surfacing Enclave when asked about ZTNA for MSPs

Who you’ll work with

You’ll work directly with the founders, and will need to understand the product, the market, and our partners well enough to make good judgement calls without waiting for a brief. You’ll have the authority to speak publicly about the product, adjust messaging, and publish without an approval chain.

We build specifically for MSPs and prioritise product quality, clarity, and long-term trust over aggressive sales tactics or startup theatre. Our partners get an 11-star support experience, and you’ll be part of delivering that.

The product is designed to be easy to understand and easy to deploy. Customers regularly describe Enclave as intuitive and low-friction, and praise us for our support responsiveness and competence. Reducing complexity, whether in product experience, documentation, or communication, is a core part of how we think about the company.

We expect focus, not a long list of priorities. We value people who improve systems, automate repetitive work, and create leverage.

This might be for you if

You understand networking and infrastructure well enough to have credible technical conversations with MSP engineers and technical buyers. You’ve probably been that engineer at some point. You’re the kind of person who’d write a script to monitor your ISP’s uptime because you didn’t trust their SLA.

Enclave works exclusivley with MSPs, so you’ll need to understand how they work and think, and emphathise with that business model. So you’ll need to have worked in that space, know how they make money and what a ticket costs, and understand the drivers, blockers and differntiators that govern the adoption of new technologies.

You might have one of these backgrounds:

• DevRel or technical community operator at an infrastructure company. You’ve built content libraries and engaged practitioners before, and you can point to the work.
• First dedicated GTM hire at a technical startup. You built the docs, the content, and the community presence yourself because there was nobody else to do it.
• MSP engineer who moved vendor-side into solutions engineering or partner enablement. You know the workflows and the pain because you’ve lived them.
• Founder or operator who has built an audience, a distribution channel, or technical credibility from scratch. You know what it takes to make something visible when nobody is paying attention yet.

You write clearly and explain technical concepts well. You naturally participate in technical communities because you find the subject matter interesting. You own editorial judgement: what is worth investigating, which positions Enclave should take, what will matter to MSPs, and where each idea belongs. You can point to work that helped you build an audience and relationships with practitioners.

You probably have a strong instinct for leverage. You automate repetitive work, improve systems without being asked, and think about how to make things findable and useful rather than just published.

You’re comfortable operating independently in a remote and async-first environment. You probably prefer shipping useful work over talking endlessly about process.

You must be based in the UK and have the right to work here.

This probably isn’t for you if

The way people find and evaluate software is changing. Practitioners increasingly discover products through AI answers, search results, peer recommendations, and technical content they trust. Paid ads, cold outreach, and LinkedIn campaigns still exist, but they’re noisier than ever and everyone is running the same plays. The companies that win now are the ones that keep showing up in credible technical contexts over time.

If your instinct is still to reach for paid acquisition, outbound sequences, or campaign-driven demand gen, this role is not for you.

You’re a delegator, not a doer. You’re uncomfortable with ambiguity, not having all the answers, or figuring things out as you go.

You are uncomfortable being customer-facing, technically hands-on, commercially involved, and highly self-directed at the same time.

How to apply

Send us your CV, and include a link to something technical you’ve written or recorded, with a brief note on how it reached practitioners. Add a paragraph or two on which MSP communities or conversations you’d earn Enclave a place in, and what you’d contribute to them.