AI Software Engineer, Security

About the role

Notion is looking for an experienced engineer to define the security foundations for our AI products. You will work with product and engineering teams on agent runtimes, tool permissions, retrieval, content writes, observability, and abuse-resistant design.

This role is based in San Francisco. We work from our offices on Mondays, Tuesdays and Thursdays (our Anchor Days) because we do our best thinking and building together in person.

Responsibilities

• Define and build security architecture for product surfaces that operate across customer workspace content, including tool execution, content writes, retrieval, permission checks, provenance, and auditability.
• Make the secure path the easy path for product teams by shipping reusable libraries, review patterns, test fixtures, and guardrails that prevent classes of vulnerabilities.
• Build automated red-team and regression testing for risks such as prompt injection, indirect instruction following, data exfiltration, tool misuse, cross-tenant leakage, and unsafe workspace mutations.
• Translate threat models for new product surfaces into concrete engineering requirements, production checks, and launch criteria.
• Use production signals, incident learnings, and targeted experiments to harden Notion over time, then feed those learnings back into architecture and developer workflows.
• Help define the security bar for how engineers use coding agents, MCP-enabled tools, hooks, and internal automation without introducing new risk.

Requirements

• 8-10+ years of experience designing, building, or securing complex software systems.
• Comfortable working in production code with product and platform engineers.
• Experience building or securing products with tool use, retrieval, workflow automation, content writes, or complex permission boundaries.
• Hands-on experience with prompt-injection testing, red teaming, model behavior evaluation, or abuse-resistant application design.
• Experience with enterprise SaaS security models: permissions, sharing, audit logs, data residency, encryption, compliance, or customer-facing trust guarantees.
• Experience building developer tooling, CI checks, coding-agent workflows, MCP integrations, or internal frameworks that shape how engineers build software.
• Public security research, vulnerability writeups, conference talks, or open-source work related to product security or secure developer infrastructure.

Skills

• Secure software engineering craft.
• Security architecture judgment.
• Security product strategy.
• Builder mindset.

Nice to haves

• Experience building or securing products with tool use, retrieval, workflow automation, content writes, or complex permission boundaries.
• Hands-on experience with prompt-injection testing, red teaming, model behavior evaluation, or abuse-resistant application design.
• Experience with enterprise SaaS security models: permissions, sharing, audit logs, data residency, encryption, compliance, or customer-facing trust guarantees.
• Experience building developer tooling, CI checks, coding-agent workflows, MCP integrations, or internal frameworks that shape how engineers build software.
• Public security research, vulnerability writeups, conference talks, or open-source work related to product security or secure developer infrastructure.