Dropbox · Primly Community

Went through the full Dropbox loop last month. Here's what actually happened.

backend_bekah · 6 replies

Just finished a Dropbox interview loop for a senior backend role (storage infra team). Thought I'd write this up while it's fresh.

Rounds: Recruiter screen, 20 min, totally standard. Technical phone screen: one coding question, 45 min. I got a problem around merging interval lists. Went fine. Virtual onsite (4 hours spread over one day): coding x2, system design, behavioral.

Coding: Both problems were medium-hard. One was graph traversal, one involved designing a simple in-memory cache structure. They didn't trick you but they cared a lot about edge cases and time complexity. I got asked "what would break this at scale" on both.

System design: Design a file sync system. Yes, literally, you're interviewing at Dropbox and they ask you to design something adjacent to their core product. They want to see that you think about conflict resolution, partial sync, client-side state. Not a trick, just very on-the-nose.

Behavioral: Ownership questions. "Tell me about a time you took over a project that was off the rails." Standard but they probed deep on what I personally did vs. the team.

The interviewers were all pretty direct. One gave me real-time feedback mid-question which was nice. Total timeline from first recruiter contact to verbal offer was about 4 weeks.

Happy to answer specific questions.

6 replies

visa_vik

the 4 week timeline is reassuring. did the recruiter communicate proactively or did you have to follow up for status updates?

backend_bekah

mix of both honestly. recruiter sent updates after the onsite but i did nudge once around day 10 after the phone screen and heard back same day. they weren't ghosty, just not super proactive.

corp_refugee

"design a file sync system" at Dropbox is so on the nose it's almost funny. did they get annoyed if you started drawing parallels to their actual architecture or did they want you to pretend you were inventing it fresh?

backend_bekah

i referenced how they probably handle it and the interviewer didn't flinch, actually seemed to like it. i think they just want to see you can reason about the domain. don't need to pretend you've never heard of Dropbox.

sre_sol

the "what would break this at scale" follow-up is so consistent across big infra shops. good heads up. did they go deep on failure modes or was it more surface level?

careerveteran

solid writeup. the behavioral probing for what YOU did vs. the team is a really common senior-level trap. teams say 'we' constantly and the interviewer is left with no signal on individual contribution. glad you noted it.