Build infrastructure handling hundreds of billions of files and petabytes of data at Dropbox

Work on the backbone systems behind Dropbox's file metadata, storage, and analytics infrastructure at massive scale — metadata for hundreds of billions of files, hundreds of petabytes of data, millions of concurrent connections. This is a deep systems role (IC3-level) requiring real distributed-systems and OS-internals depth, with occasional on-call.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Distributed systems design at massive scale
OS internals: filesystems, concurrency primitives, networks
Multi-threaded backend system experience
Production debugging and on-call incident handling
Language proficiency (Python, Go, C/C++, or Java)

Common question themes

Design infrastructure to manage metadata for billions of files

Explain semaphores vs. mutexes and when each applies

Describe debugging a production issue in a distributed backend system

Tell me about an on-call incident you handled and its root cause

How would you improve interoperability across ecosystems linking many services

How candidates describe it

Real 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 interviews