R Systems Android Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at R Systems.
R Systems
Android Developer
Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Technical Behavioral
Worst interview process ever. Cleared all rounds. Asked HR for feedback, was told selected and it's in progress. A month later, still no reply for onboarding. They just wasted my time.
Confirmed questions1 question
- What is the dependency concept in Android development?
R Systems
Senior Android Developer
Senior Difficult Positive experience Accept offer 4 rounds
Interview process
Technical screen Technical screen Onsite Recruiter call
Interview formats
Technical Coding Behavioral Other
It was a 4 round interview process. There were 2 technical rounds, 1 round with the VP, and 1 HR round. The interview was a bit difficult, so you need to have a strong grasp of fundamental concepts. No need to study new technologies. Focus on Dagger2, Coroutine, Solid Principle with examples, and DSA (you can skip DP, graph, and Tree). Prepare for Recursion, Linked List, Arrays, Stack, and String.
Confirmed questions4 questions
- General questions about Kotlin and Android, not too difficult, followed by a challenging DSA question involving Map and Recursion (specifically, the Reconstruct Iternary problem).
- Started with a simple Kotlin question, then delved into Coroutines in depth, and covered Dagger2 extensively (focusing on the builder pattern, parameter passing, and annotation processing). Strong Dagger2 knowledge is crucial.
- A non-technical round designed to assess your confidence level.
R Systems
Senior Android Developer
Senior Average Negative experience No offer 6 rounds
Interview process
Technical screen Take home Technical screen
Interview formats
Technical Coding
It was a long interview process, with 6 technical interviews. They ended up not selecting anyone. There were 5 technical interviews and 1 test. I got rejected in the 6th round. The last round was very deep into DSA, which I think should have been in the earlier rounds.
Confirmed questions4 questions
- Tell me about Kotlin basics.
- What do you know about coroutines?
- How would you approach DSA problems?
R Systems Android Engineer Interview Questions
Quoted word for word from R Systems interview reports.
“Write a Kotlin program to count character occurrences.”
Read reports →“What is ProGuard and what is its purpose?”
Read reports →“What are coroutines in Kotlin?”
Read reports →“What are coroutine builders?”
Read reports →“What is the dependency concept in Android development?”
Read report →“Can you explain the differences between MVP and MVVM architectures?”
Read report →“Tell me about Kotlin basics.”
Read report →“What do you know about coroutines?”
Read report →“How would you approach DSA problems?”
Read report →Formats, difficulty and experience
Across all 5 R Systems interview reports.