Motorola Mobility Interview Experience | Set 1 (For Android Developer, Bangalore)
Question Details
I have 2 yrs of experience in android domain.I have applied for Motorola in May.Process spanned for 1 month long.I could not find much info about their interview process o...
Full Details
I have 2 yrs of experience in android domain.I have applied for Motorola in May.Process spanned for 1 month long. I could not find much info about their interview process on net.So i am sharing my experience here.Hope it helps others.:)
Round 1 Interview Street (1 hr) 1)WAP to get maximum number from the digits of a given number 2)Parse a string and return if it is valid or not based on given patterns.It should contain only "1" or "12" or "122" ONLY Round 2-Google Hangout(1 hr) -General Intro -Few basic android questions on localization and resource configurations 1)Code for Longest common prefix from a list of strings. 2)There is a device driver that reads from a camera and writes a stream of bytes (captured frames) into a buffer. There also is a viewer that reads from this same buffer. The device driver and viewer do not communicate with each other other than through this buffer. Design and code this scenario. You may choose the data structure of the buffer per your liking. Please note that there may be multiple viewers. Round 3-Google Hangout(1 hr) 1)Code for moving zeroes to starting in a random integer array 2)Given a binary search tree of positive integers, if all the nodes are multiplied with -1 then is it still a BST? If not, reconstruct to one.(Mirror tree code) Round 4-Google Hangout (1.5 hr) 1)Given an array of random unique integers, find the indices x,y,z such that a[x]
About This Question
This is a reported interview question from a motorola mobility interview for a android role during the phone screen round reported in 2016.
It covers the following topics: Trees, Strings, Binary Tree, Binary Search, Arrays .
Difficulty rating: Easy
Topics
About Motorola Mobility Interview Reports
This question was reported by a candidate who interviewed at Motorola Mobility. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Motorola Mobility are the higher-signal extractions to take from this report.
For broader preparation context, the Motorola Mobility interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Motorola Mobility reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Motorola Mobility Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Motorola Mobility reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.