
Mobiquity Android Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 8 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mobiquity.
Android Developer
So I went through 6 rounds for this Junior Android Developer role at Mobiquity. The first round was just a basic screening with background questions. Then came the first technical phone interview where I got hit with a rapid fire of CS questions covering Java, Data Structures, Web Services, and Agile. Round 3 was the Android coding challenge – designing a Dropbox API with specific features. Round 4 was another technical interview, tougher than the first, focusing on Android classes for solutions and testing my knowledge and thinking. This part took about 1.5 weeks. After that, things got a bit drawn out. They said the next interview was the final one, but round 5 was a mix of HR and technical, with deeper technical questions than before, which threw me off since I expected only HR. It took two weeks for them to get back, and instead of a decision, they scheduled another technical interview. Communication became clunky, citing mail issues. Round 6 was scheduled two weeks later, and it was again technical plus HR, but the technical part was easy, asking previous questions. The HR part focused on leadership. Finally, this concluded the process, and it took another two weeks to hear back. I get that hiring takes time, but the lack of timely responses and constant follow-ups were frustrating, especially stretching 2 interviews over 1.5 months.
- Tell me about your background.
- Can you answer some basic Computer Science questions?
- Do you have any questions about Java?
Senior Android Engineer
The interview process had 4 steps and it took 3 weeks. I applied for Mobiquity Amsterdam. It started with a phone screen with some behavioral questions. the second part was a code challenge and then two technical interviews. All interviewers were nice and friendly without any strange questions.
- What makes you want to join our company?
- What is your reason for leaving your current role?
- Would you be open to working on different platforms?
Android Developer
It took a little over 2 months to go through the 5 interviews. A coding assessment was part of it, which was pretty difficult because of all the requirements and the time they wanted it back in. I didn't manage to finish everything on the assessment.
- The coding assessment involved creating a dropbox application using the new Api.
- How do you consume a REST api?
- What are your data structures?
Mobiquity Android Engineer Interview Questions
Quoted word for word from Mobiquity interview reports.
“What's the difference between onStop() and onPause() in Android?”
Read reports →“What is a Binary Search Tree?”
Read reports →“Explain the difference between LinkedList and ArrayList.”
Read reports →“What is a Service in Android?”
Read reports →“In a certain scenario, which is more efficient: LinkedList or ArrayList?”
Read report →“What is daily scrum?”
Read report →“What is the Activity lifecycle in Android?”
Read report →“How do you consume a REST api?”
Read report →“How would you design an MP3 player that stops when a call comes in?”
Read report →Formats, difficulty and experience
Across all 8 Mobiquity interview reports.