I applied online and was contacted by a recruiter. The first phone screen with the recruiter went fine. She mainly asked about my experience and two technical questions. She also explained the next steps for the second technical phone interview.
Within a few days, I was scheduled for the second interview with a newly joined QA from NY. This position was SF-based.
The interviewer mentioned at the beginning that he had no clue about the team or the role I was being interviewed for, so he wouldn't be able to answer any questions I might have regarding that. He began with QA philosophy questions and then moved on to scenario-based questions, asking me to list test cases for every scenario.
The interview went very well, or so I thought. I was expecting to hear back from them and followed up with both recruiters, but there was no response.
After more than a week, I received an automated response of rejection. I requested feedback, since the email didn't provide any information, but I never heard back from them.
How do you test
Why QA?
Why are you looking to move?
The following metrics were computed from 1 interview experience for the Dropbox Senior QA Engineer role in San Francisco, California.
Dropbox's interview process for their Senior QA Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Dropbox's Senior QA Engineer interview process in San Francisco, California.