Technical Content Writer (Looking For immediate joiners)

The Opportunity -

As our Technical Content Writer, youll own the editorial engine that defines and explains

the AI Security Engineer category. Your work will educate CISOs, influence analysts,

enable sales and fuel demand. From deep-dive whitepapers to crisp battlecards, youll turn

dense security concepts into clear, credible narratives.

Who Youll Write For

• CISOs & Security Leaders: strategic POVs, category explainers.
• Security Practitioners: use cases, workflows, integration docs.
• Analysts & Media: research reports, trends, category briefs.
• Sales Teams & Prospects: one-pagers, battlecards, case studies.

What You’ll Do

Editorial & Thought Leadership

• Publish long-form pieces (1,200–2,500 words): whitepapers, POV essays, deep

dives (DSPM vs DLP, Insider Risk, DDR).

• Ship mid-form posts: blogs, field notes, feature explainers.
• Ghostwrite for founders (LinkedIn, op-eds, talk abstracts) and craft sales

enablement (one-pagers, battlecards, objection handling).

Research & Rigor

• Interview SMEs (CTO/PM/SE), fact-check, and cite vendor-neutral sources.
• Track threats/trends (SaaS exfil, cloud exposure, LLM/AI data risks) and propose

story angles.

• Create simple diagrams/flows (Mermaid/draw.io/Figma) to explain “how it works”.

Product & Docs

• Translate features into benefit-led narratives; draft release notes and light API/SDK

snippets when needed.

Distribution & SEO

• On-page SEO (titles, meta, internal links, schema), content briefs, and interlinking.

• Partner with design for visuals; measure impact via GA4/GSC and optimize.

Must-haves

• 3–7 years B2B tech writing with a portfolio (blogs/briefs/whitepapers) showing

clarity and structure.

• Security-literate storytelling: Can explain DLP vs DSPM vs DDR in plain English;

describe a simple SaaS data-exfil scenario; classify PII/PHI/PCI and why it matters.

• Cloud & SaaS basics: Understand AWS S3 access/policies, IAM roles, what KMS

does; common sharing/retention controls in M365/Google Workspace.

• Ops context: Knows what SOC/SIEM/SOAR do and how signals flow from detection

triage response.

• Editorial discipline: Structured outlines, SME interviews, rigorous fact-checking &

citations, clean revisions, plain-language edits.

• Tools: Markdown, Google Docs, Notion/Confluence; diagrams in

draw.io/Mermaid/Figma; basic on-page SEO and ability to read GA4/GSC.

Nice-to-haves

• Light lab chops to validate flows (e.g., reproduce a simple S3 exposure or SaaS

share-outside-org); familiarity with Wireshark/Burp/Nmap or light Python/SQL for

demos.

• Case studies: From customer interview to quantified outcomes.
• Framework fluency: MITRE ATT&CK mappings; compliance contexts (NIST/ISO

27001/SOC 2/GDPR).

• AI/LLM data-risk patterns: Prompt/response leakage, shadow AI usage, SaaS

connector risks.

• Published bylines in security/enterprise tech outlets.

How You’ll Work

• Collab: Founders, PM, Eng, Design, Sales. Fast SME access, tight review loops.
• Stack: Docs/Notion, Markdown, draw.io/Mermaid, Figma, GA4/GSC, an SEO

assistant, and LLMs for draft acceleration (with strict fact-check).

Role details

• Title: Technical Content Writer
• Location: Bengaluru (hybrid; onsite for interviews/whiteboard sessions as needed)
• Type: Full-time
• Reporting to: Head of Marketing (dotted line to Product/CTO for technical review)
• Comp: Competitive; depends on experience. Equipment & tools provided.