The interview process was quite quick. I met the recruiter at a career fair on campus and was quickly called for an on-campus one-on-one interview. This was fairly standard, involving an online coding interface to type my answers. It lasted one hour and I was asked one main coding question.

Next week, I was invited for a phone interview, also one hour long with an online coding interface. This was again fairly standard. Following that, I was invited on-site soon after. I scheduled the interview for two weeks later and went on site.

The day began at 10 am. There were:

• Three coding interviews
• One interview about my projects and leadership roles
• A demo of one of their new beta products

Each interview was one hour long and featured moderately challenging questions. Note that the HR person insisted there would be emphasis on concurrency-related questions, for which I prepped especially. However, there were none, which surprised her.

The day on-site ended at 4 pm.

I received an email notification the following week, approximately three business days later, stating that I was unfortunately not a good match. They noted that with more experience, I would likely be a better fit, and I appreciate that clarity in their feedback.

Overall, my experience was very good, and the interviews were fair and relatively easy. I believe given that Dropbox is a new and fairly small company, they need excellent candidates. It appears that if you are not perfect, you may not be hired even if you are pretty good, as they probably need the best people to move the company forward. Shame, but oh well.

Write methods to log hits and get the number of hits in the past 'x' minutes.

Write a program to get possible valid words for a given phone number.

Write a program to find all reachable web pages from a given URL.

Write a program to find all duplicate files within a folder.