IDrive Interview Questions
& Process

I applied to iDrive online near post-graduation with my M.S.E.E but less experience. The HR manager contacted me via email, asking for salary requirements and to schedule an in-person interview; there was no phone screen. I replied tactfully to an email mix-up. The interview was an in-person analytical programming interview, non-interactive, to test independent problem-solving. I was given puzzle questions on paper, typical for fresh graduates, which might seem a bit tough initially. One was the bridge-solving problem, which I'd solved before. This was followed by analytical puzzles needing written answers. My interest in PHP and JavaScript led me to apply. After the 1-hour written part, the VP of technology gave me two questions (JavaScript and PHP) to answer on a desk computer in his office. I had plenty of time. This was to assess problem-solving, program construction, and verbal explanation. When he returned and saw my solution and explanation, his non-verbal cues suggested my approach wasn't quite up to par. He took the paper back, and I was shown out, concluding the interview. I did note down the questions and my answers afterward.

The whole process took 2 days. On Day 1, there was an on-call interview. Day 2 involved an interview at IDrive in Bengaluru back in April 2018. The interview process consisted of 6 rounds in total. There were 2 technical rounds (one of which was on-call), a written test, a system test, a managerial round, and an HR round. The technical rounds covered topics like memory management, threading, concurrency, and the app lifecycle, lasting about 45 minutes. The written test focused on aptitude, logical reasoning, verbal ability, and data interpretation, taking around 45 minutes to an hour. The system test required fetching data from an API and displaying it in a tableview, with details navigating to a next controller upon cell tap, and it lasted for 1 hour. The managerial round involved process discussions and design patterns. Finally, the HR interview was primarily for salary discussions.

This was a technical round. There were 2 panel members. They didn't ask me to write any programs. It was purely based on WPF and OOPS concepts. I answered most of the questions with examples. I don't know what they were expecting. They didn't select me. I attended twice, and both times they did the same thing, even though I answered most of the questions. They are not ready to select me. They wasted my time. They didn't even give proper feedback. It was really a waste of my time since the questions were also very frequently asked questions.

The interview process started 40 minutes late. It felt like I was in the wrong place upon entering, and the office gave a poor impression, reminding me of bus stand employees rather than a tech company. The process included a face-to-face interview, a system test with two questions, and then another face-to-face interview. Although the third round was expected to be the last, a final telephonic round with the US team was added. The HR promised an update the next day but never followed up.