first interview was more of a "tell about yourself" kind of interview, that is, less technical. second one involved technical questions in android(basic ones, such as best examples of causes of memory leaks in android, difference between activity/fragment, etc.) an in algorithms, such as: how would you implement an auto-complete algorithm given a certain list of words/strings.
How to solve conflicts, managment decision, persuasion ability
Fragments, Oops, Multi threading.
easy questions on android technology
1st rounds HR questions, a little bit about tech stacks to try to find out whether it aligns. Screening HR interviewer very knowledgable though, very well prepared and to the point. 2nd round hiring manager, how would you handle situation XYZ. Did you have failures, how you handle feedback, etc. More attitude oriented, want to see how you learn etc. 3rd was coding assignment for which negative feedback contained points like: - unused classes in structure (which I left there on purpose; I'm not shipping production code)
I had to code the fizz buzz game while sharing the screen and cover it with the unit test. The preferred approach is TDD, but they are quite open and understandable if you prefer not to.
Write an image loading library without help of any other library.
basic android questions
How are activities different than fragments.? What are the steps involved in submitting to play store? How do you unit test your application?
Perché mi stessi spostando su una realtá piú grande.
Viewing 3611 - 3620 interview questions