Android Applications Developer Intern - Summer 2027
Posted Aug 24, 2026 · We last checked this listing on Oct 6, 2026
Likely interview questions for this role
Written from this job description, not a generic list. Each one notes what the interviewer is really checking.
About your past
Tell me about a mobile app you've built, even a small one for a class or side project. What did it do and what was your role in it?
What they are checking: whether the candidate has actually shipped working Android code versus only studied concepts
Tell me about a time you had to figure out a requirement that wasn't clearly spelled out for you. How did you go about clarifying it.
What they are checking: comfort with the ambiguity of requirements gathering, which is explicitly part of this role
Tell me about a group project where you worked in short sprints or had regular check-ins. What was that rhythm like for you.
What they are checking: exposure to and comfort with Agile-style team cadence
Why does this role, working on apps for public safety customers like police and fire, interest you specifically, compared to building a consumer app.
What they are checking: genuine motivation and whether they understand the mission-driven nature of the work versus applying broadly
What would you do
Suppose you need your app to connect to a back-end service over a RESTful API and handle a slow or failed network response. How would you structure that so the app doesn't freeze or crash.
What they are checking: practical understanding of asynchronous work and error handling, not just theoretical API knowledge
Say you're partway through building a feature and discover the design won't scale well once real usage picks up. What do you do, and who do you talk to first.
What they are checking: judgment about escalation and whether they default to silently pushing forward or flagging risk
If a teammate's code review left several comments on your pull request that you disagreed with, how would you handle that conversation.
What they are checking: how they handle feedback and disagreement without becoming defensive or dismissive
About the work
Walk me through the difference between an Activity and a Fragment, and when you'd choose one over the other.
What they are checking: basic fluency with Android's core building blocks, since this is foundational to any app work here
Have you worked with Kotlin, or mostly Java? If Kotlin, what's one feature of the language you found genuinely useful compared to Java.
What they are checking: honest self-assessment of the specific language skill called out in the posting, and depth versus buzzword familiarity
Have you used any Android framework components like Bluetooth, sensors, or background services? Tell me about a time you had to work with one.
What they are checking: real exposure to the specific device-level components public safety apps often depend on
What do you know about how Android handles app permissions and data security, and why that might matter more for an app built for police or fire departments than for a typical consumer app.
What they are checking: awareness that this is a public safety context with higher security stakes, not generic app development
Have you used Git in a team setting? Describe a time a merge conflict or branching issue came up and how you resolved it.
What they are checking: real collaborative version control experience versus solo project use
What does object-oriented design mean to you, and can you give an example of a class or interface you designed and why you structured it that way.
What they are checking: whether OOP is understood as a design tool rather than a term memorized for interviews
Practice this interview out loud.
Offer builds a real interview for this exact role at Motorola Solutions from your resume and this job description, asks the questions one at a time, and tells you what landed. The first one is free.
Practice this out loudThe full job description
As published by Motorola Solutions.