I applied online and received a call from HR about two weeks later. The usual behavioral and resume questions came up.
I scheduled a technical phone interview, which asked about the general Java, OO, and data structures questions you can find anywhere.
I was then invited to an in-person interview in downtown Chicago. It consisted of a sit-down with an engineer where he/she thoroughly questioned my background and asked me to demonstrate some pseudo-SQL, coding, and Git.
Then, another engineer sat down with me as I coded up a more involved Java question.
Next was lunch with developers to feel me out. Afterward, I met with the project manager to get to know me.
Finally, there was one last meeting with a developer to ask some quick coding questions.
The bad part of the interviewing process was the waiting around for an answer and being constantly ignored by HR and the developers. The entire process of scheduling, etc., was relatively quick.
The whole waiting for an answer portion took two to three months, only to receive an auto-generated email stating I did not receive an offer. None of the individuals I reached out to ever responded.
It was a complete letdown to such a positive experience.
Implement a Parking Lot in Java, which utilizes interfaces.
Implement a program to check for the uniqueness of a 16-digit credit card number.
Show us the Singleton design pattern.
The following metrics were computed from 1 interview experience for the Motorola Mobile Developer role in Chicago, Illinois.
Motorola's interview process for their Mobile Developer roles in Chicago, Illinois is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Motorola's Mobile Developer interview process in Chicago, Illinois.