Dropbox Senior Infrastructure Software Engineer Interview

What this interview tests

• Distributed systems design at scale — Every posting tests large-scale distributed systems judgment -- API and storage design for Identity, trillion-document indexing for Search, exabyte-scale replication for Storage Core, and hundreds-of-billions-of-files metadata systems for the general Infra posting.
• Domain-specific technical depth — Identity and Auth expects OAuth, SSO, OIDC, SAML, MFA, and RBAC knowledge; Storage Core wants erasure coding and consistency tradeoffs in Go, Rust, or C++; Search wants lexical, vector, and multi-modal indexing architecture.
• Migration and re-architecture planning — Identity and Auth explicitly tests phased data migration planning without breaking dependent services, and Search tests unifying two existing search products into one platform.
• Production reliability and on-call — Storage Core and the general Infra posting both expect detailed root-cause-analysis stories from on-call incidents in mission-critical, high-QPS services.
• Ambiguity and technical strategy — Search and the general Infra posting both call out owning long-term, ambiguous infrastructure projects and setting medium-to-long-term technical direction with no clear right answer.
• Cross-team dependency management — Identity and Auth specifically tests resolving conflicting requirements from multiple product teams that depend on your platform.

Common question themes

Likely format

None of these four postings specify an interview format, so this is inferred. Given the consistent design-a-system phrasing paired with the nine-plus years of seniority expected in three of the four postings, expect deep system-design conversations centered on each team's specific domain -- identity, search indexing, storage replication, or metadata -- rather than generic algorithmic coding rounds.