Senior Infrastructure Engineer building Dropbox's next-generation search platform (Dash + file/folder search)

Build a highly scalable in-house search platform that unifies Dropbox Dash (AI-powered work search) with Dropbox's native file/folder search — spanning lexical search, vector search, multi-modal search, Q&A, and recommendations, at an indexing scale of trillions of documents. Requires 9+ years of backend systems experience and comfort owning long-term, ambiguous infrastructure projects.

Practice this interview

Free · a live voice mock calibrated to this exact role

Start the mock interview

What this interview tests

Scalable indexing architecture for lexical, vector, and multi-modal search
Unifying two search products into one platform
Distributed, geographically-dispersed backend systems at trillion-document scale
Operating system/filesystem/network fundamentals
Ownership of ambiguous, long-term infrastructure projects
On-call and production reliability for search services

Common question themes

Design an indexing platform that serves lexical, vector, and multi-modal search from one system

How would you scale a search index to trillions of documents while keeping it fresh?

Tell me about a long-term infrastructure project you owned end-to-end under ambiguous requirements

Describe your experience with search infrastructure like Elasticsearch

How do you approach international expansion for a latency-sensitive backend service?

Walk me through a production incident on a large-scale distributed backend you debugged

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