Dropbox interview prep

See what Dropbox asks, then get a plan for it

Real Dropbox frontend questions and candidate reports, turned into a week-by-week prep plan.

~2 min · free preview

Company prep

Dropbox Front End Interview Guide

The Dropbox frontend interview process, real questions, and candidate reports.

Questions
162
Reports
Solved
—

Verified by FrontendLead

Practice questions162

StatusQuestionSolution

Premium Question

Easy

Text Solution

Premium Question

Medium

Text Solution

Premium Question

Medium

Text Solution

Premium Question

Medium

Text Solution

Premium Question

Medium

Text Solution

Premium Question

Easy

Text Solution

Premium Question

Medium

Text Solution

Premium Question

Hard

Text Solution

Premium Question

Medium

Text Solution

Premium Question

Hard

Text Solution

Premium Question

Easy

Text Solution

Premium Question

Hard

Text Solution

Premium Question

Hard

Text Solution

Premium Question

Medium

Text Solution

Premium Question

Medium

Text Solution

From the community

Interview reports

Dropbox frontend interviews are among the most frontend-specific loops members describe. Expect DOM traversal, a multi-phase coding problem that punishes messy structure, a photo carousel with caching and retries, a vanilla JS debugging round, and a long system design. Several candidates call it the most complete test of a frontend engineer they have taken.

This guide is built from 17 Dropbox interview reports that FrontendLead members posted between November 2023 and January 2026, plus the 15 coding questions members have tagged with Dropbox. You’ll get the stages, what each round grades, and a four-week plan that targets them. The exact prompts candidates were asked are in the members-only sections below.

By Shivam Bhalla · Updated

01

Dropbox frontend interview at a glance

Aspect
What to expect
Timeline
3 to 6 weeks from first screen to decision
Stages
Phone screen(s), then a multi-round virtual onsite
Onsite loop
Often 5 to 6 rounds: coding, debug, system design, deep dive, HM/BQ
Coding style
Vanilla JS and React; multi-phase problems with growing requirements
Signature topics
Text-editor style class problems, DOM class queries, photo carousel, TodoMVC debug
System design
Longer than many companies (members report ~75 minutes)
Languages
JavaScript is the default; confirm TypeScript availability
OA option
Some candidates choose OA vs live phone; OA text-editor variants are common
02

The Dropbox front end interview process

Confirm logistics with your recruiter. The path below matches most FrontendLead frontend reports.

  1. 1

    Recruiter and phone screens

    1 to 2 rounds

    Early rounds often cover DOM traversal helpers or a single multi-phase coding problem that builds on itself. Structure your code for extension; messy phase-1 code becomes a refactor tax later.

  2. 2

    Online assessment (optional path)

    Timed

    Some candidates are offered OA instead of a live phone. Reported OAs include text-editor style tasks with many test cases. Members warn that 90 minutes can feel tight if you have not practiced the pattern.

  3. 3

    Virtual onsite

    4 to 6 rounds

    Typical mix: practical coding (carousel or continued editor-style problem), vanilla JS debugging (TodoMVC-like apps with several bugs), frontend system design (calendar, contacts, or similar), project deep dive, hiring manager, and behavioral. Design slots are often longer than at peer companies.

  4. 4

    Decision

    Fast feedback common

    Several members heard within a day. Dropbox grades breadth: coding, debugging, design, and behavioral all need to clear the bar.

03

How Dropbox frontend loops differ

Unlike companies that lean on algorithm drills for frontend titles, Dropbox leans into browser and product skills:

  • DOM APIs and tree traversal
  • Incremental feature building with clean state
  • Reading and fixing unfamiliar vanilla JS
  • Frontend system design with real component and API modeling
  • Behavioral depth, including leadership give-and-receive stories

Distributed-systems prep alone will not save a frontend loop here.

04

What the coding rounds actually test

These are the patterns that come up again and again in Dropbox reports. Each card links to the closest verified practice question on FrontendLead.

Multi-phase class / editor problems

Phone and OA

A single problem grows across phases. You maintain class state and methods; poor structure in phase 1 makes later phases painful. Text-editor style backspace/delete behavior and rich in-memory stores are reported variants.

Practice: Command Undo Stack, Parser for Rich Text Editor, and Transactional Record Store.

DOM traversal by class and hierarchy

Classic phone screen

Implement get-by-class-name on a node tree, then a hierarchy query (for example a>b>c) that returns matching deepest nodes. Recursion and careful classpath parsing matter.

Practice: getElementsByClassName and Traverse DOM.

Photo carousel with production concerns

Onsite coding

Prev/next controls, async image loading, caching, retry, loading states, throttling, and layout. Interviewers grade resilience as much as the happy path.

Practice: Image Slider, Lean Photo Carousel, and API Retry.

Vanilla JS debugging

Onsite staple

A TodoMVC-like app with roughly 5 to 7 bugs spanning object updates, event listeners, CSS positioning, regex, and inputs. Ask for a hint if stuck more than a few minutes.

Practice: To-do App and tight vanilla JS fundamentals via trivia questions.

In-memory store with evolving requirements

Some onsites / apprenticeship

Set/get/delete that later adds aggregation, modification counts, and top-N queries. Design for extension.

Practice: Transactional Record Store and Mini Record Store.

05

Real Dropbox interview questions reported by candidates

Every question below comes from a FrontendLead member’s interview report. Dates are when the report was posted.

Round Question Level
Initial screen Single problem in 4 phases; class with methods and state that grows each phase IC3 Senior UI (Jan 2026)
Phone getByClassName(root, className) then getByClassHierarchy(root, "a>d") Frontend (Dec 2023)
Phone / OA Text editor behavior (backspace vs delete) with many test cases Frontend (Jun 2024)
Onsite coding Photo carousel: paging, data fetch bugs, throttling, frontend optimization Frontend (Jun 2024)
Onsite coding Photo carousel in vanilla JS with cache, retry, loading Senior (Dec 2023)
Onsite debug TodoMVC-style app with ~5–7 bugs (events, CSS, regex, inputs) Frontend (Dec 2023)
Onsite In-memory DB: set/get/delete, then modification counts and top-N keys Apprenticeship (Apr 2024)
System design iPhone-style contacts API / system design Frontend (Jun 2024)
System design Google Calendar-style frontend component, model, and API design Senior (Dec 2023)
System design Design Google Calendar (75-minute style design slot) Frontend (Nov 2023)

Members can read the full write-ups in the Dropbox interview reports.

06

What Dropbox system design interviewers dig into

Design rounds are long and frontend-true: component boundaries, client models, and APIs for products like calendars and contacts.

Component and model design

Asked directly

Break the UI into components, define the client data model, and show how props and state flow.

API design for the client

Asked directly

Endpoints, payloads, pagination, and how the UI handles partial failure. Contacts and calendar prompts both go here.

Production concerns

Follow-ups

Caching, retries, offline/poor network, and performance of large lists.

Practice: Network Requests and system design questions.

Scope control

Common pitfall

Members who dove into tiny details too early lost the plot. Agree on requirements, sketch the model, then deepen.

07

Worked example: class hierarchy DOM query

Practice this until the hierarchy walk is automatic:

function getByClassName(root, className) {
  const out = [];
  const walk = (node) => {
    if (!node) return;
    if (node.classList?.contains(className)) out.push(node);
    for (const child of node.children || []) walk(child);
  };
  walk(root);
  return out;
}

function getByClassHierarchy(root, path) {
  const parts = path.split('>').map((s) => s.trim()).filter(Boolean);
  const out = [];
  const walk = (node, i) => {
    if (!node || i >= parts.length) return;
    const match = node.classList?.contains(parts[i]);
    if (!match) {
      for (const child of node.children || []) walk(child, i);
      return;
    }
    if (i === parts.length - 1) out.push(node);
    else for (const child of node.children || []) walk(child, i + 1);
  };
  walk(root, 0);
  return out;
}

Clarify whether hierarchy steps must be direct children or descendants before coding. Narrate the difference out loud.

08

Behavioral, deep dive, and hiring manager

Dropbox onsites spend real time on behavioral and HM conversations. Members reported deep project dives, leadership give-and-receive questions, and a full hour that felt like an interrogation when stories were thin. Prepare questions for the HM; empty air in a 30-minute slot is a reported miss.

Practice with FrontendLead’s behavioral questions.

09

How the loop changes by level

Mid-level

Breadth still required

You still face debug, carousel, and design. Completeness and clear communication matter more than inventing novel architectures.

Senior

Design and ownership

Longer design, sharper production follow-ups, and project stories with scope and impact. Multi-phase coding expects clean extensibility.

10

A four-week Dropbox prep plan

  1. 1

    Week 1: DOM and multi-phase coding

    Phone readiness
  2. 2

    Week 2: Carousel and async resilience

    Onsite coding
  3. 3

    Week 3: Debug and system design

    Long rounds

    Debug a messy todo app under time. Mock calendar and contacts designs for 60+ minutes. Use system design questions and To-do App.

  4. 4

    Week 4: Behavioral and timed OA-style

    Close gaps

    Leadership stories, HM questions list, one timed multi-phase problem. Review coding, trivia, and behavioral.

11

Mistakes that sink Dropbox candidates

  • Writing phase-1 code that cannot extend, then drowning in refactors.
  • Choosing OA without practicing text-editor style problems and burning the clock on tests.
  • Staying silent for five minutes in the debug round instead of asking for a hint.
  • Diving into micro-details in system design before locking requirements and the model.
  • Underpreparing behavioral and HM questions on an otherwise strong coding loop.
12

Dropbox front end interview FAQ

How long is the Dropbox frontend interview process?

Members typically report three to six weeks, with a multi-round onsite after one or two screens.

Does Dropbox ask LeetCode for frontend roles?

Frontend loops emphasize DOM, multi-phase JS/React problems, debugging, and frontend system design more than classic LeetCode. Confirm your loop with the recruiter.

Should I pick the OA or the live phone screen?

If you are strong at methodical, test-case-driven JS problems, OA can work. Members who picked OA cold often regretted the text-editor style pressure. Prefer live if you communicate better while coding.

What should I practice first?

DOM class queries, one multi-phase stateful problem, a resilient photo carousel, and a timed vanilla JS debug session.

Where can I find real Dropbox interview reports?