1. 30 minutes with Tech Recruiter
2. 1 hour technical round with 3 Mobile Developers

Interviewers were very ill-mannered and lacked judgmental skills. I believe HSBC gave the interview task to a bunch of mid-level developers who had no idea how to interview candidates.

They asked a question about LiveData and Compose. They don't go together; it's actually not a recommended approach in Android. The interviewer didn't even know what they were asking. They should learn how to ask correct questions.

Android has thousands of APIs. A developer cannot know all APIs at their fingertips just because it is being implemented in the Zing App. Rejecting based on that shows poor decision-making skills from the interviewers.

Interviewers should check for a candidate's ability to learn and adapt to new tech, which was missing.

They still haven't transitioned to Jetpack Compose and are using Jetpack components. Pathetic state of affairs; no wonder such a poor interviewing experience.

Why can't we use LiveData instead of State in Jetpack Compose? Why do we even need State? Can't we pass LiveData directly? How Fragment Navigation works: passing data between different fragments. Dark/Light mode questions: Does the screen refresh again? Use case inside another use case approach for retrieving different values from different repositories. Deeplink and why do we need to open Home to open another TAB or fragment from DeeplinkHandler? What happens if I go back? Will Home show up? LiveData vs. ViewModel. MVVM architecture: Why do we need it? What is Usecase? Why do we need it? What is the Domain layer? What does it have in Android? Why is it used? What is the repository pattern? Various Android Components. Using which component can we open another application?