The process took 3 weeks from start to finish.
An initial phone screen was followed by recruiter emails to arrange an in-person interview at SF HQ. There were materials in a Dropbox for use in an MBA-style case study. This involved a role-play where you were to pitch Dropbox for business to a media company.
The experience was a bit odd, as they have a non-disclosure policy. I typically like to course-correct during a customer engagement based on feedback. Without feedback, it made for a somewhat awkward exchange.
The team there is very young, and they are trying to establish their processes to scale up/out for their new Enterprise offering, where I could have helped. I believe 'fit' is also important to them. Perhaps I was a little too old, a little too hardware-focused, and a little too 'big' company for them, but it was an interesting experience in the new world of interviewing, and I wish them the best.
How would you quantify TCO on the Dropbox for Business offering to help justify its cost for internal approval during the sales process?
In a Windows environment where you are using Dropbox with AD, what happens to the data when a user leaves the company?
The following metrics were computed from 2 interview experiences for the Dropbox Solution Architect role in San Francisco, California.
Dropbox's interview process for their Solution Architect roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Dropbox's Solution Architect interview process in San Francisco, California.