Build Notion's trust, safety, and AI-guardrail systems protecting millions of users

Notion needs a software engineer with 5-8 years of experience to build authentication, fraud/abuse detection, and AI safety guardrails protecting the workspace at scale. Based in SF or NYC with in-office Anchor Days (Mon/Tue/Thu), this role sits at the intersection of trust & safety, security, and AI-powered product features, partnering across Engineering, Security, Legal, and Data.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Authentication and account security systems
Fraud/abuse detection at scale (phishing, spam, scraping, ATO)
AI safety guardrails for agents and LLM features
Cross-functional partnership with Security, Legal, Data
Ownership of ambiguous, unscoped problems

Common question themes

Tell me about a trust, safety, or security problem you owned end to end

How would you design detection for account takeover or credential stuffing

How do you think about guardrails for an AI agent with access to sensitive data

Describe a time you took ownership of an ambiguous problem with no clear owner

Have you used ML or LLMs to fight fraud/abuse — walk through the system

How do you balance blocking bad actors against not disrupting legitimate users

How candidates describe it

Real Software Engineer interview stories — retold from candidates' public write-ups, with sources.

Google · L3 Software EngineerOffer

Google L3 software engineer interview: phone screen, four coding rounds, and the Googleyness round

A candidate with two years of experience went from recruiter outreach to offer over about four months. The onsite was four 45-minute coding rounds — three of them featuring binary trees — and one round turned into a 25-minute chain of follow-ups about approximating an optimal solution at scale.

Interviewed June 2020 · Bangalore, IN

Google · L4 Software EngineerNo offer

Google L4 Software Engineer Interview: Eight Rounds, No Offer

An L4 Software Engineer candidate went through two phone screens, three onsite rounds, a culture conversation, and a team-matching call with a Google hiring manager, then watched the process stall for about a month and a half over a tightened experience requirement before an added extended round ended without an offer.

Interviewed February 2024 · Not specified

Google · L5 Software EngineerNo offer

Google L5 software engineer interview: phone screening, three onsite rounds, system design, and a late rejection

A candidate interviewing for an L5 role went through a phone screening, three onsite coding rounds, a mobile system design round, and a Googleyness and Leadership round. Two of the four technical rounds went poorly by the candidate's own assessment, and after roughly two months of silence the recruiter reported that the role had been closed.

Interviewed January 2023 · Not specified

View the original posting

All Notion Software Engineer interviews

All Notion interviews