We're a small office working on technically difficult problems across the stack that are critical to Dropbox's success. You'll have an opportunity to make an impact on both our 500+ million users and our ~60 person office and culture. We work on hard problems that matter, and we've built an excellent community here.
--
More specifically, at the moment, we're looking for:
We're a small office working on technically difficult problems across the stack that are critical to Dropbox's success. You'll have an opportunity to make an impact on both our 500+ million users and our ~60 person office and culture.
More specifically, at the moment, we're looking for...
We're a small office working on technically difficult problems across the stack that are critical to Dropbox's success. You'll have an opportunity to make an impact on both our 500+ million users and our ~60 person office and culture.
More specifically, at the moment, we're looking for...
At Dropbox NYC, we're a small, growing team making a big impact on Dropbox's products and infrastructure. We work together on wholly-owned projects in NYC ranging from web/mobile product engineering to lower-level infrastructure. For example, the infrastructure team for Dropbox Paper (https://www.dropbox.com/paper), entirely based in New York, is responsible for bringing this exciting new product to the scale and stability required for general release.
Working on challenges that only a big company faces in the setting of small office has been an incredible experience, and we've only just begun.
Dropbox NYC | New York, NY | Mobile, Web, Infrastructure | Full Time, Onsite
We're a small team working together on products and infrastructure critical to Dropbox's success. I've been here since Dropbox's first day in NYC, and I'm very excited about the caliber of our team and the impact we've made in just the last year. The adventure has been amazing thus far, and it's only just begun.
Dropbox | New York City | Software Engineer / Site Reliability Engineer | ONSITE
We're a small team building the foundation for Dropbox's first engineering office outside San Francisco. We work on impactful projects that are essential to Dropbox's success. It's a lot of fun, and we've only just begun.
Dropbox | New York City | Software Engineer / Site Reliability Engineer | ONSITE
We're a small team building the foundation for Dropbox's first office outside San Francisco. We work on impactful projects that are essential to Dropbox's success. It's a lot of fun, and we've only just begun.
We're a dozen engineers building the foundation for Dropbox's first office outside San Francisco. We work on impactful projects that are essential to Dropbox's success.
If you can test everything manually with confidence that every incremental change breaks nothing you've ever thought about prior to the present, I suggest you work on more complicated things. Otherwise, you're mistaken.
The irony is that AngelList allegedly generates funding for real engineering teams.
DigitalOcean is fabulous. It's very nice hardware and not very expensive. No AWS services, but if all you need is root access to an OS image, I can't recommend it enough.
My point was more on shipping new features quickly, not shipping buggy software. It's up to your engineering process to ship solid software. The Play Store just enables your product team to figure out product/market fit ASAP.
This is incredibly misleading. Saying that the difference between iOS 4 and iOS 7 is equivalent to the difference between Android 4.1 and Android 4.4 is absurd.
The big jump in Android was from Android 2 to Android 4 (Android 3 was mostly a release for tablets). Sure, there are differences between Android point releases, but they're not as substantial as the "major versions" the chart suggests.
PhoneHome home doesn't send any data that your application couldn't otherwise expose. It just provides an easier way to do it for the developer.
Regarding sensitive data, Facebook has had issues leaking user tokens in logs, and I imagine they're not alone. The typical way to handle this is to put all the sensitive information (if you have to log it at all) at a certain level and then use ProGuard to strip the calls out of the bytecode when making a production build, but between Android and remote libraries, I found that this involves a lot of whack-a-mole to get a config file that works.
But, if you've got everything through a layer of indirection (using PhoneHome), it's easy enough just to switch on the BuildConfig.DEBUG to decide whether to print to the system log.
Feel free to reach out again if you're interested and interviewing -- we're still growing quickly!