Getting the opportunity to work closely with really bright and motivated people is in itself a strong motivation to perform well at Dropbox.
You also really get a sense that you are doing something good for the world, that the work you do has a measurable impact on people using Dropbox, Mailbox, or Carousel.
There are also a lot of stellar perks, from the game room, stocked with DDR, foosball, ping pong, and more, to the amazing Tuck Shop, our cooks and baristas, providing us with a five-star breakfast, lunch, and dinner experience.
Honestly, the Tuck Shop is better than many restaurants!
At Dropbox, we have some issues with code quality and in communication between teams on shared projects.
As there is a lot of pressure to meet deadlines, at times code modularity and quality has been sacrificed for rapid development.
This has come to bite us in the butt at times, as someone has made a change in a shared project which has derailed the work of another team.
This is getting better, but still it is as of yet an unsolved problem, besides having some people whose jobs are actually improving and cleaning up the codebase.
It would be nice if we had a little more space. Sometimes I feel like there aren't really great places to work besides our desks.
I would love having a quiet workspace with comfortable chairs where people could come and go but that would always be quiet, just to have the chance to get away from the noise of the office.
The interview process was a coding assessment and a phone screen. The coding assessment was a design question consisting of four parts. It increased in difficulty and involved designing a system to do a certain task.
Phone interview: The question was to find all duplicate files in a file system. Follow-up questions included: * What if files are large? * What if files are small? The interviewer was kind of indifferent.
After the resume screen, the second stage was a coding interview. I was asked one question related to recursion, specifically to find a duplicate file in a filesystem. This was conducted in a browser-based text editor.
The interview process was a coding assessment and a phone screen. The coding assessment was a design question consisting of four parts. It increased in difficulty and involved designing a system to do a certain task.
Phone interview: The question was to find all duplicate files in a file system. Follow-up questions included: * What if files are large? * What if files are small? The interviewer was kind of indifferent.
After the resume screen, the second stage was a coding interview. I was asked one question related to recursion, specifically to find a duplicate file in a filesystem. This was conducted in a browser-based text editor.