Responsibilities

• Positioning and narrative. Define what "always-on red team" means in a market crowded with traditional pentest firms and AEV (adversarial exposure validation) platforms. Make the difference obvious in one sentence.
• Research-led content. Work directly with our security researchers to turn attack-chain research, tradecraft findings, and assessment data into posts, talks, and reports that practitioners actually read and share.
• Demand generation. Build the pipeline engine end to end: target account lists, outbound infrastructure, email, LinkedIn, retargeting, and the measurement to know what's working.
• Account-based marketing. Our buyer universe is a few hundred named enterprises, not a funnel. Design programs that reach specific accounts and specific people inside them.
• Sales enablement. Decks, one-pagers, case studies, competitive teardowns, objection handling, and the security questionnaire answers that unblock procurement.
• Community and events. Show up where security people are: BSides, DEF CON, Black Hat, RSA, CISO dinners, podcasts, and the private communities where buying decisions actually get influenced.
• Founder amplification. Ghostwrite, edit, and produce for the CEO and the research team. Their credibility is our largest marketing asset.
• Website and product marketing. Own the site, launches, pricing pages, and the way we describe what we do as the product changes.
• Analyst and press relations as we grow into it.

Requirements

• You write well and you write a lot. Marketing at our stage is mostly writing. Everything else is downstream of it. You'll be asked to write during the interview process.
• You can earn technical credibility with security practitioners. You don't need to have been a red teamer. You do need to be able to read a writeup on EDR evasion or an initial access chain and turn it into something a security engineer would send to a colleague. Tell us what security content you already read and who you think does this well.
• You have shipped pipeline, not just brand. You can point to sourced meetings and closed revenue you were accountable for, and explain the specific mechanics that produced them.
• You have positioned a product in a crowded category and can walk us through the reasoning, including what you decided not to say.
• You've done this early. You've worked somewhere that had no playbook, no team, and no budget, and you built the motion anyway.
• You have judgment about tone. We market offensive capability. Fear-mongering reads as amateur to sophisticated buyers, and some things shouldn't be published at all. We take responsible disclosure and customer safety seriously and expect you to as well.
• You're comfortable being measured. You'll propose the numbers you want to be held to in your first quarter.

Preferred

• Background marketing to CISOs, security engineering, or IT leadership
• Experience in offensive security, exposure management, detection and response, or an adjacent category
• Fluency in how the exposure management landscape is actually framed today, including CTEM and AEV, and where we sit in it
• Existing relationships in the security community, whether media, analysts, conference organizers, or practitioners
• Experience with enterprise sales cycles and long, multi-stakeholder deals
• Comfort with the modern stack: HubSpot or similar, Clay, Apollo, analytics, basic design tooling
• Public work we can look at: a newsletter, a talk, a body of writing, a brand you built