What is ADB and what are two common commands you use?
Tests your hands-on familiarity with the core Android toolchain. Define ADB's client-server architecture, then explain adb install for APKs and adb logcat for logs. A red flag is being unable to name specific commands or only knowing IDE buttons.
What's really being asked
This question tests your practical, hands-on experience with the Android toolchain. Interviewers want to see that you can operate efficiently outside the GUI of Android Studio. Your ability to use ADB is a proxy for your debugging skills and your fundamental understanding of how the development environment interacts with a physical or virtual device. It separates candidates who only click buttons from engineers who understand the tools they use.
The full answer
A strong answer covers three main points in order. First, define ADB as a versatile command-line client-server tool that facilitates communication between a development machine and an Android device. Mentioning the three components (a client on your machine, a server that manages communication, and a daemon running on the device) shows deeper knowledge. Second, provide your first command example, like adb install [path/to/app.apk], and explain that it pushes and installs an Android application package onto the connected device. Third, provide your second command, like adb logcat, and explain that it streams the device's log output to your console, which is essential for real-time debugging and crash analysis.
The mistakes people make
A common red flag is a vague, high-level answer like "it's for debugging" without providing any specific commands. Another is only being able to describe the actions of IDE buttons (e.g., "I use it to run my app") without knowing the underlying commands. Candidates who confuse the roles of ADB (device communication) and Gradle (building the project) also raise concerns. Simply giving incorrect syntax or mixing up what commands do (e.g., saying adb shell installs an APK) is a clear sign of inexperience.
What usually comes next
Expect follow-up questions that probe deeper practical knowledge. For example: "How would you use ADB to connect to a device over Wi-Fi?" (Answer: adb tcpip 5555 followed by adb connect <device_ip>). Or, "Your device is showing as 'offline'. What are your troubleshooting steps?" (Answer: Check physical connection, ensure USB debugging is enabled, and finally run adb kill-server followed by adb start-server to reset the ADB server).
A concrete example
To show senior-level experience, frame your answer with a scenario. For instance: "In a previous role, we had a bug that only reproduced on a specific Android 11 device in our QA lab. To avoid a full rebuild, I used adb push [local_file] [remote_path] to hot-swap a specific configuration file on the device, then adb shell am force-stop com.example.app to kill the app, and restarted it to test my fix. This allowed me to iterate on a solution in minutes instead of the full 10-minute build and deploy cycle."
Interview question
After a developer builds an APK, what is the primary function of the Android Debug Bridge (ADB) in the development workflow?
- a.To open a remote shell and manually create the app's data directory before installation.
- b.To provide the graphical user interface for managing devices within an IDE.
- c.To compile the application's source code and resources into the APK file.
- d.To facilitate communication with a device for transferring and installing the APK.Correct
Why? this is the answer
ADB is a command-line tool that enables communication with a device. Its primary role after a build is to install the APK using `adb install`. Compiling the APK is the job of a build tool like Gradle, not ADB.
Just read this? Test yourself on what you have been reading.
Read the original → developer.android.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on android — each one lists the topics its interview covers.
See open roles