Well, from the recruiting side about me and my experience, with the other interviews about the android framework, how to handle certain situations, more android related questions, coding challenge in real time, more technical questions and in my final interview a little bit of my experience what are my plans and a few more questions of that type.
Are you the kind of person who enjoys working at a startup, or the kind of person that enjoys working at a big company? Are you OK with working with other people to define a process for a startup? Tell me about a time you disagreed with another engineer on their work and yours. Tell me something you do to keep up with technical trends As an ever evolving ecosystem, where do you see android headed later?
A lot of high level questions: Pros and cons of doing contract work, how would I go about managing new features, spec out the requirements.
Nothing extraordinary overage interview, a bit boring. They are lazy, the whole process is 3-4 weeks, and they will waste your time.
Typical for an Android type role with IOT items
- update solution of my THA according to changed requirements - overall approach towards Android app development - tools, libraries, arch design decisions
Android architecture
Why viewModel in Android? Why coroutine and how it is working
Design patterns and fundamentals Android questions Mobile architecture Clean architecture
Part of the interviews were behavioural, and the second part was more related to the tech domain.
Viewing 191 - 200 interview questions