Technical interview portions were all pretty standard Android development in Kotlin. If you know your stuff you should be fine. I learned RxJava like 2 weeks earlier, and that was definitely helpful. Non-technical portions mainly focused on my past and personality. They really are looking for good culture-fit; that's a huge part of their focus. They want collaborative people driven to help each other and the users.
All about programming language details, syntax and multithreading
Explain the android activity life cycle with examples.
Difference between ng-if and ng-show
Most of the questions were related to standard memory management/app submission process (explain the app distribution process, what are pointers, questions about arrays vs sets, etc. )
What do you know about erajaya
Code an app authentication screen and functions, search function by calling api, and details screen of the searched term. cache result to display during offline condition
What Flutter state management you have used?
Behavior questions included a lot of the classic ones: "Why should we hire you?" "Tell us about a weakness of yours." Technical included defining HTTP request methods and reading a snippet of HTML for errors
About previous experiences and scenarios given how would react to it
Viewing 3241 - 3250 interview questions