You get to work with some of the best people in tech. The technical scale is massive, and the engineering org overall is small enough that you can get close to the action.
The culture is collaborative and supportive, although there is occasional cross-team conflict. However, I don't think it's more than can be expected given the size. Generally, engineering leaders are involved in resolving such conflict.
There's just a lot of people and strategy pivots as Dropbox tries to figure out its next big thing.
There was a recruiter call, followed by a panel interview with three sections. Two were technical, and one was behavioral. The coding was medium level. There was a lot of explaining your thought process and resume grilling.
I interviewed for Dropbox in Seattle. Initially, my recruiter informed me that I would have a phone screen, a two-hour onsite interview at the Seattle office, and a full-day loop at the headquarters. The first phone screen seemed to go well. The int
Briefly self-introduce for a few minutes, then proceed to algorithm questions. My question is related to finding duplicate files. The total interview time is 1 hour. The interviewer is a software engineer at Dropbox.
There was a recruiter call, followed by a panel interview with three sections. Two were technical, and one was behavioral. The coding was medium level. There was a lot of explaining your thought process and resume grilling.
I interviewed for Dropbox in Seattle. Initially, my recruiter informed me that I would have a phone screen, a two-hour onsite interview at the Seattle office, and a full-day loop at the headquarters. The first phone screen seemed to go well. The int
Briefly self-introduce for a few minutes, then proceed to algorithm questions. My question is related to finding duplicate files. The total interview time is 1 hour. The interviewer is a software engineer at Dropbox.