Re-architect Dropbox's Identity platform for a multi-product future

Dropbox is hiring a Senior Infrastructure Software Engineer to re-architect its Identity systems as the company shifts from a single-product to a multi-product company, covering distributed systems design, API design, phased data migrations, and persistent storage at high QPS. This interview targets deep infra engineering experience (8+ years) and probes distributed-systems tradeoffs, migration planning, and cross-team execution rather than general web development.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Distributed systems and API design at scale
Phased data migration planning and execution
Persistent storage design tradeoffs
High-QPS production service operations and on-call
Identity & Auth concepts: OAuth, SSO, OIDC, SAML, MFA, RBAC
Cross-team collaboration with multiple dependent product teams

Common question themes

Design or re-architect a large distributed system for a new multi-tenant use case

Plan and execute a phased data migration without breaking dependent services

Resolve conflicting requirements from multiple product teams depending on your platform

Debug or respond to an incident in a high-QPS production identity service

Reason about OAuth/SSO/SAML tradeoffs in a platform redesign

How candidates describe it

Real Senior Infrastructure 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 Dropbox Senior Infrastructure Software Engineer interviews

All Dropbox interviews