Security Community & Relationships Manager

Why this role

AI is changing how security work gets done, and the practitioners who figure it out first are building it themselves: agents, skills and detections for their own work. Security people trust what they can test and what their peers build.

We grow through relationships and by inviting them in. Practitioners bring their own AI to Defendermate through our MCP server, and we want the best of them building on it: in contests, through bounties for finding gaps in how our agents reason, and by contributing attack techniques, detections and agents of their own. You'll build those relationships, with practitioners and with the people who lead their communities, and run the programs that bring them in.

Who you'll work with

You'll work closely with our security research team (who design and judge the challenges and review contributions), product engineering (what builders need from the platform), and the rest of go-to-market (events, content and the people evaluating us).

What you'll build

• Relationships across the security community: with chapter and meetup leads (null, OWASP, BSides), CTF and conference organisers, researchers and creators, so Defendermate is welcome where practitioners gather.
• Contest seasons: challenges to build agents and skills on our platform, scored against real test cases, designed and judged with our security team.
• A bounty programme: rewards for practitioners who find gaps in how our agents decide whether something is exploitable.
• A contribution engine: community-written attack techniques, detections and agents, with recognition, leaderboards and contributor spotlights.
• Ambassadors and showcases: community voices, winners on stage at events, and hands-on workshops.
• Our speaking and events calendar: talk submissions, podcast bookings, our own podcast's guests and recordings, and event logistics.

What you'll do

• Run community campaigns where practitioners gather: security research communities (null, OWASP, BSides, bug-bounty circles), cloud and Kubernetes communities, and AI-agent builders.
• Use the product as a practitioner would, and bring what the community needs back to the team.
• Create the tutorials, examples and talks that get builders started.
• Run the speaking and events calendar: find and submit talks, book podcasts, line up guests and recordings for our podcast, and handle event logistics.
• Measure what matters: invitations, sign-ups, first builds, active contributors, accepted contributions.

Your first year

• First 90 days: an invite-only beta season is running, and the bounty and contribution programmes are designed with the security team.
• First year: public contest seasons have run at least twice, there's a steady base of active contributors, winners have been showcased at a major event, there's a steady flow of accepted talks and podcast slots, and the community measurably brings in new users.

You might be a fit if

• You have security credibility: you've done vulnerability research, testing or security engineering, and practitioners respect you.
• You've built or run a community, a CTF, a meetup or a relations programme, and people in the security community know and trust you.
• You write and speak clearly.
• You're comfortable with GitHub and scripting, and with trying products hands-on.
• You use AI tools and agents heavily, and you're excited about what practitioners can build with them.

Bonus points: organised CTFs, bug-bounty events, security meetups or conference talks; run a podcast; built on MCP or agent frameworks; a following in the security community.