I was introduced to a recruiter at Dropbox by a mutual acquaintance (who doesn't work at Dropbox). The recruiter and I set up a phone call where we talked about my background, the position(s) I was interested in, and the interview process.

There were multiple mobile positions, but since I would need to get past a technical phone screen regardless, she said we could figure out which would be a good fit after that.

The 1-hour phone screen was scheduled for a few days later. The recruiter had given me some tips when I talked with her, and the scheduler gave me some more, as well as the name of the person who would be interviewing me. The interviewer started by asking me to go over my background. We then did a coding problem (listed below). Although I was warned by the recruiter that the phone screen would be difficult, I didn't think the question was very hard. I had a few minutes at the end to ask some questions. Overall, the interviewer was friendly and professional.

The recruiter called the following week to tell me that I had passed the phone screen and they wanted to invite me onsite. She also apologized because apparently I was given the wrong problem during the phone screen (but I believe they gave me an easier question than intended, so I wasn't upset since it was to my benefit). She explained that she would be handing me off to another recruiter who worked more closely with the relevant hiring managers and knew more about the position(s) I was interviewing for.

I was introduced to the new recruiter via email and worked with him to schedule a phone call for the following week to talk about what role I would be interviewing for. After the phone call, I was still a little confused about exactly which team I would be interviewing with, but I figured I'd get it cleared up at the onsite (because hopefully at least some of my interviewers would be on that same team). I worked with the scheduler and the new recruiter to set up the onsite for the following week (now almost 3 weeks after my phone screen, but that was fine with me; I wasn't in any rush).

The scheduler gave me the schedule, the names of everyone I would be meeting with, and a brief description of the format of each interview. The onsite was a total of 8 hours (not in order):

• 1-hour lunch
• 1-hour all-around / experience / behavioral
• 1-hour mobile design / architecture
• 2x 1-hour whiteboard coding problems
• 2-hour hands-on coding of an app which was provided at the interview (on my own laptop, which I was asked to bring so that I would have access to the coding environment and tools I was most comfortable with)
• 30-min wrap-up where I was given a chance to ask all my questions
• The remaining half hour was basically just 15 mins of padding at the start and the end to absorb any slips in the schedule

My assumption that some of my interviewers would be on the team I was interviewing with turned out to not be correct. Aside from the all-around interviewer, who was an engineering manager, everyone else was an engineer and about half were mobile engineers (or had been at one time), but they were all on different teams. Only the last person I talked with (the one who did the wrap-up) knew anything about the specific position I was interviewing for and was actually the manager for that team. That was a little unfortunate because it meant I didn't really have a chance to meet the people who would have been my teammates. But everyone I did meet was friendly, engaged, and professional. Also, the office was amazing, particularly the cafeteria and the food.

The recruiter emailed me the next morning to set up a follow-up phone call, which we scheduled for the following Monday (the onsite was Thursday). The phone call was just a few minutes to ask how I thought things went and to let me know they should have a decision by the end of the week. I got the decision Friday, along with the option of another phone call to go over feedback (which I took). I always appreciate when people are willing to take the time and share feedback! Overall, the interview process could have been a bit more organized, but it also wasn't the worst I've seen.

Given a folder in a file system, return a list of file duplicate lists. Duplicates are determined by comparing file contents, but files may have different file names and/or extensions.

Duplicates may also appear at different levels under the given folder; all subfolders should be searched.