Asked about the basics of Android App Architecture, Dependency Injections, Inheritance, Writing Unit Test cases, Different kinds of Patterns, Offline Data storage in Android (Ex:Room), and many other Scenario based questions. I have answered most of the questions, but ended up getting rejected.
Conversational style interview. Technical discussion around QA processes and strategies/ automation approach/strategies.
Rate yourself on how familiar with different skills.
java, oops, testing questions, behavioural questions
Do you have experience with API development? How many years of iOS experience?
Introduce yourself. Can you work under pressure?
What are the differences between const and final?
What do you think about this code (they provided)?
The interview went very well, the first one was a telephonic call just to discuss my CV, the second one was via teams with some team members and team lead, there was a technical test as part of that. It was fairly easy. And the last Interview was in person at the Johannesbugh office with the cio, digital development manager and an HR consultant. The interview was fun, we discussed about everything, The questions were mostly about knowing me as a person and my interests, to see if i'd be a match. It was more of a chat to get to know each other than an interview.
Screening - availability, reason for applying big O - Leetcode medium, maybe a bit easier than that. It's one of those exercises that has multiple phases where each builds on top of your solution to the previous one. In my case, it had 4 and it was required that I complete 3. I was informed of this beforehand although in an unnecessarily misleading way imho, as I was told 70% was the minimum "grade" to pass, while each step awards you with a score of up to 25%. Manager interview - Conflict resolution, addressing bringing up process improvements as well as my way of improving others System design - Design a system where you can show a list of transactions made by a user. The problem statement was a little misleading imho because it turned out that they wanted me to design the API endpoints and not do a client HLD, which is opposite to every other mobile design interview I have ever done, and that includes Meta, as well as what's stated on resources provided by the company themselves ahead of the interview, but maybe you can give them the benefit of the doubt and pin this on me not having clarified a seemingly-already-clear point instead.
Viewing 4131 - 4140 interview questions