
IDrive Analyst Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 6 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at IDrive.
Programme Analyst
First, I got a call from a consultancy, and we discussed my notice period and current salary. They mentioned the role was for a Mac App, and learning it would be sufficient, not mandatory. The first round was a tech interview with a senior dev focusing on basic and advanced iOS concepts, specifically memory management and ARC. The second round delved deeper into iOS, covering design patterns and memory management again. Then came the assignment round where I had to develop a Mac OS app, mainly fetching data from an API and populating the UI, focusing on best practices. It took me two days to learn and build it since I'm experienced with iOS but not Mac apps. The fourth round was with the project lead, who asked about MVC's advantages over functional programs. After this, I decided not to proceed further. The interviewer seemed to lack knowledge of design patterns and app architecture. I was rejected without a given reason. The fifth round, as per the recruiter, involved some basic MCQs from HR. It felt like a complete waste of time with 4 technical rounds, and the pay didn't seem great. They should have at least provided feedback.
- Can you explain the difference between structs and classes, and discuss ARC, access specifiers, design patterns, memory management, and retain cycles?
- Could you describe some use cases for implementing an image downloader and explain protocols?
- What is the advantage of MVC when compared to functional programs?
Programme Analyst
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.
- Could you elaborate on all the memory management related questions, specifically concerning Retain, Release, and Copy?
- Can you explain multi-threading, covering dispatch queues and nsoperation queues?
- Are you able to solve very simple data structure questions, like reversing a string?
Programme Analyst
The whole interview process spanned 5 days, and it took an additional 2 days to get the offer letter. It included 2 technical rounds, an aptitude test, a techno-managerial interview, and an HR round. The difficulty was medium, and all interviewers were super helpful and patient with me.
- Questions were asked regarding Core Java.
- Questions were asked regarding Java Spring.
- Questions were asked regarding React concepts.
IDrive Analyst Interview Questions
Quoted word for word from IDrive interview reports.
“What is the hierarchy of UIView?”
Read reports →“How does a filter work in Servlets?”
Read reports →“What is the advantage of MVC when compared to functional programs?”
Read reports →“What are the main and global queues?”
Read reports →“How would you go about stopping a background thread?”
Read report →“Could you explain the difference between valueForKey and objectForKey, and provide your reasoning?”
Read report →“Can you explain the servlet life cycle?”
Read report →“How do these libraries work?”
Read report →“Is it possible for you to alter the navigation stack?”
Read report →Formats, difficulty and experience
Across all 6 IDrive interview reports.