We focus on making the user's life simpler, and we are trying to build a company that makes money because people pay us for what we offer, which is fairly unique in this day and age where most companies are focused on eyeballs to show ads.
We also solve challenging technical problems at scale, both on the client (large amounts of personal data, in fast, low-resource clients, across a wide variety of platforms) and in our backend (large amounts of data, mostly unique per user). When we build things, we strive to build them correctly, both because we're protecting data that is precious to our users, but also because we believe in quality and things just working for our users.
Benefits, time off, etc., are all world-class, but they're not the reason you should work here. The reason to work here is the focus on the user, the focus on quality, and solving hard engineering problems.
The company is growing fast, and growing causes pain.
Medium-term goals change more often than at a big company or than they would if it was a less competitive space, since we're always trying to balance being nimble without getting distracted.
It's part of the fun, but it can take a little to get used to.
I came in for an onsite tech screen, something that Dropbox offers for people who are interviewing locally. Two interviews back to back, both whiteboarding questions. The questions themselves were pretty standard, but the way I was treated in the in
A recruiter reached out to me on LinkedIn. After a few conversations and a technical phone screen, I went onsite for 5 hours of interviews at the SF HQ. This was followed by dinner at Dropbox. The onsite consisted of: * Two whiteboard problems * A
On-campus interview. I found a tech talk on Facebook and then submitted my resume online for an on-campus interview. They had an on-campus dinner the night before the interviews, which was kind of like a behavioral interview scenario. It wasn't tha
I came in for an onsite tech screen, something that Dropbox offers for people who are interviewing locally. Two interviews back to back, both whiteboarding questions. The questions themselves were pretty standard, but the way I was treated in the in
A recruiter reached out to me on LinkedIn. After a few conversations and a technical phone screen, I went onsite for 5 hours of interviews at the SF HQ. This was followed by dinner at Dropbox. The onsite consisted of: * Two whiteboard problems * A
On-campus interview. I found a tech talk on Facebook and then submitted my resume online for an on-campus interview. They had an on-campus dinner the night before the interviews, which was kind of like a behavioral interview scenario. It wasn't tha