Telephonic round : - Briefed about the company. - ArrayList vs LinkedList in java - How to sort an array of integers - quick discussion on sorting strategies - HashMap implementation - Given an array of integers and an integer 'k', find all the pairs that add up to 'k'. No testing questions were asked. Got a call from recruiter within half an hour that I have been shortlisted for F2F round. F2F round 1: - Given an array of characters, find frequency of each character. - Given an array of integers and an integer 'k', find all the pairs that add up to 'k'. - Given a String and an array of Strings - for each entry in the array, find if it occurs in the given String Was asked to optimize each solution and write code Interviewer was helpful F2F round 2: - You have doc to pdf converter. The convert button is not working. Debug all possible scenarios. - A bug you reported which was hard to find. - A bug that slipped into production and how you managed it. Round with product manager How would you manage the following situations: - ecommerce app - new feature going live is 'recommended products'. You have joined today, release is after 2 days. - QA is not complete but you are under pressure to give sign-off. - Managing tight deadlines - Your biggest achievement and mistake - QRcode scanning feature for employee attendance - discuss test cases

The very first thing you should be prepared for is wasting a lot of your time. Generally in every interview it happens that you might have to wait for 30-40 minutes but here it's a different level. Rivigo interviewers are the busiest of all. Got the call through a consultancy. 1st round was TCON. It was rescheduled twice. The interview was good though and the interviewer was friendly too. So I thought it might be a good company. 2nd round was F2F in Bangalore on weekend. It was a really poor experience. First they made me wait for 2 hours. Then they told no interviewer had come to office so they took the interview over Skype. The interviewer was okay but looked a little less experienced. He wasn't able to understand my project and it's complexities. This happens when someone has worked on only one type of project and hasn't explored other technologies and tools. He asked very trivial questions from Java and Automation. It was one the easiest interview but I didn't like their overall process of interviews and their culture so didn't go forward for other rounds.