Cut Notion's page-load and interaction latency as a core Web Infrastructure engineer

Interview for Notion's Web Infrastructure team, owning web client performance and developer tooling used by all Notion product engineers. Expect deep React/bundling performance system-design questions and discussion of real-user metrics, aimed at candidates with 8-10+ years building and optimizing large web applications.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

React/large web app performance optimization
Bundling and build tooling (e.g., Webpack) and profiling
Systems thinking: paved-road abstractions and developer tooling
Real-user performance metrics (page load, interaction latency)
Monorepo and codebase modularization

Common question themes

Design a plan to reduce time-to-render on a large, complex web page

How would you reduce interaction latency across many components

Walk through a real-user performance metric you improved and how you measured it

How do you build developer tooling that many teams will actually adopt

Experience modularizing a large monorepo or reducing cyclic dependencies

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