Questions were stick to basics only. -Android components -oops concept -Threading -activity lifecycle -Fragment lifecycle -Singleton - Other Design Patterns - Jetpack components - Dagger 2 - Coroutine - val vs var - Adbstact class vs interface - Pipelining No question were asked in depth.
They have asked me about my graduation and 12 grades. Even I am post graduate but they did not consider it.
Nothing special, the interviewers are really experienced in making it a discussion rather than interview.
Questions related to Hilt
What would you use similar to a thread in java?
Q2) What is activity and it's lifecycle ?
Q1) Tell me about yourself, higher education, total experience and relevant experience
Cuales son los Dispatchers en Kotlin?
Esta me la pasó por escrito a través del chat: Can you explain how a mobile app should interact with a backend when performing operations that must be idempotent (e.g., sending a payment or submitting a form)? Please include how idempotency keys are generated, stored, and reused across retries.
They asked me to walk them through the single most important question I was given during the entire process. They wanted to know exactly what the question was, why it mattered, how I approached it, and what my thinking looked like as I worked through it. In other words, they were trying to understand not only the content of the question but also the way I reasoned about it and explained my thought process.
Viewing 6351 - 6360 interview questions