Vivino Interview Questions
& Process

The interview process consisted of three rounds. One round was with HR, another with the manager, and the final one with the CEO. Everything went smoothly, with no unexpected questions. The people were very pleasant, had a good attitude, and everyone was nice.

It was a great positive experience meeting the team and learning about Vivino's QA processes. I was very impressed with their advanced automation implementations. The interview mainly focused on core QA automation skills. I really enjoyed the process and got to the second round. My performance in the second interview was impacted by a release at my current company. I hope to get another chance to interview for QA roles at Vivino and will come back better prepared. Thanks again for the wonderful experience.

I applied on the company website and got a call a few days later for an interview that lasted an hour with two senior iOS engineers. We talked about my resume and past experience, and it ended with a short coding test that wasn't too difficult. It was a good experience overall, and the interviewers were nice. They seemed to be looking for someone with more experience than I had, especially since I'd been out of the field for a bit. They called afterward to give me the decision and feedback respectfully.

I applied online and the head of QA reached out for a screening interview. The whole process had 3 parts: a screening call, an assignment, and a technical interview. The first call was with the head of QA, where we talked about my experience, skills, and day-to-day tasks. The next day, I got an assignment to build an automation framework from scratch using Appium, Ruby, and Cucumber for their Android app. The requirements included using the Page Object Model, BDD with Cucumber, good Ruby coding practices, passing Ruby cop, and passing all tests with features like scrolling and swiping. The project also needed to be submitted on Github. This assignment took a lot of time and effort. The third round was a technical interview via Google Meet with two interviewers, though one mostly stayed silent, likely for feedback. This round felt more like an interrogation than an interview. The interviewer, who seemed arrogant, skipped introductions and immediately started firing questions covering a wide range of testing topics, from manual to automation. He would ask a question and move on to the next while I was still answering, with a smirk. It was very stressful. I answered about 90% of the 25+ questions correctly. Then, I had to solve a coding problem online, which I did in about 10 minutes, but the interviewer seemed unsatisfied, wanting a specific solution. Five hours after the interview, I received an email stating they weren't moving forward. When I asked for feedback, the head of QA mentioned a mismatch in skills on 3-4 questions. It's unreasonable to expect perfect answers to all 25+ questions, especially exactly what they're looking for. The entire process took about two weeks and left me feeling cheated and exhausted. I'd advise job seekers to be cautious and look for companies with more conversational and less robotic interview processes.