Technical Content and Community Lead

Responsibilities

• 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
• The shape of the role: technical content creation, web, search and AI visibility, partner enablement, community presence, inbound commercial, and support and product feedback
• 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.
• 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

Requirements

• You’ll 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 exclusively with MSPs, so you’ll need to understand how they work and think, and empathise with that business model.
• 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 differentiators that govern the adoption of new technologies.
• You must be based in the UK and have the right to work here.
• This role is for someone who understands MSPs and can work independently in a remote, async-first environment.

Preferred

• DevRel or technical community operator at an infrastructure company.
• First dedicated GTM hire at a technical startup.
• MSP engineer who moved vendor-side into solutions engineering or partner enablement.
• Founder or operator who has built an audience, a distribution channel, or technical credibility from scratch.
• You write clearly and explain technical concepts well.
• You own editorial judgement: what is worth investigating, which positions Enclave should take, what will matter to MSPs, and where each idea belongs.