This position was for Mumbai (India) location. I received a call from a recruitment agency.
The first interview was on November 23, 2014, and the final F2F rounds were on January 7, 2015, so it was quite a long interview process. I got an offer after two weeks of F2F interviews.
Overall, the process was a bit slow, and communication could have been better. A small, one-line email saying, "We will get back to you..." also makes a difference sometimes.
Everything was good about this opportunity except the salary part. I was not looking for a job change when I got this call, nor did I prepare. But when the recruitment agency told me about the team and said salary would not be a problem, I thought, "Why not give it a try?" Finally, salary became the only problem.
However, I have no regrets. I learned several things during the interview and became hungry to learn again. I definitely missed the opportunity to work with excellent people. Hope they find a better candidate than me, and I will get a better job/offer than them. Wish them good luck. :)
Round 1 (Skype): Areas covered included language-specific basic questions, puzzles, data structures, test case design, and writing small functions.
Round 2 (Telephonic): Test case design, processes, Jenkins, and testing concepts.
Round 3 (Coding Assignment): Given a Web API, I was asked to come up with test cases using any framework or language and integrate with Jenkins. This involved coming up with test cases that covered different types of testing.
Round 4 (F2F): Before the interview started, they provided an introduction to the product, their work, and their challenges. This helped me understand their expectations and focus accordingly. It was a pure technical round covering various areas of testing, coding, and logic.
Round 5 (F2F): Same as Round 4.
Round 6 (F2F): Same as Round 4.
Round 7 (F2F): Same as Round 4.
Round 8 (F2F): A problem-solving round where I was asked 3 puzzles. By this point, I was exhausted, and my brain wasn't working as expected. However, I was able to solve the problems with hints.
That was it, pack up for the day and return to my home city. Overall, I wouldn't say I performed excellently in the interview. When I did my self-evaluation afterward, I understood that I could have answered a few questions better, especially the coding questions.
The following metrics were computed from 1 interview experience for the OpenTable Senior Test Automation Engineer role in Mumbai, Maharashtra.
OpenTable's interview process for their Senior Test Automation Engineer roles in Mumbai, Maharashtra is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for OpenTable's Senior Test Automation Engineer interview process in Mumbai, Maharashtra.