Media.net SDE-2 Android Interview Experience
Summary
I had an interview for an SDE-2 Android Developer role at Media.net in Bangalore. I successfully navigated through the DSA and Android Fundamentals rounds but was ultimately rejected after the Hiring Manager round due to challenges in designing an Android application's high-level and low-level design.
Full Experience
My interview experience for the SDE-2 Android Developer role at Media.net in Bangalore consisted of three technical rounds followed by a culture fit round. Unfortunately, I was rejected after the hiring manager round.
Round 1 – DSA (60 mins)
This round focused on Data Structures and Algorithms. I was given two medium-level problems to solve within 60 minutes. I successfully implemented solutions for both and cleared this round.- Unique Paths II: This was a dynamic programming problem involving a grid with obstacles.
- Lowest Common Ancestor of a Binary Tree: This was a classic tree traversal question.
Round 2 – Android Fundamentals (60 mins)
This round delved deep into core Android concepts. The interviewer asked detailed questions on several topics. I felt confident in my answers and cleared this round successfully.- The lifecycle of Activity, Fragment, and ViewModel.
- The internal working mechanisms of ViewModel.
- Dependency Injection principles and practical applications in Android.
- Various Activity launch modes and their use cases.
- General Android concepts and best practices.
Round 3 – Hiring Manager (60 mins)
This final technical round started with a discussion about my previous experience, current projects, and responsibilities. Following that, I was asked to pick a favorite Android application and design its High-Level Design (HLD) and Low-Level Design (LLD).I chose the Google Search App due to its widespread utility. I spent a significant amount of time detailing the HLD, perhaps covering too many non-core features, which unfortunately left me with limited time to adequately discuss the LLD. This round concluded with a rejection.
My key takeaways from this experience are to keep the HLD focused on core functionality, especially when time is a constraint. It's crucial to prioritize clarity and discuss trade-offs rather than trying to detail every possible feature. Practicing structured design answers under timed conditions would definitely improve performance in such rounds.
Interview Questions (4)
Discussion covered various core Android concepts including the lifecycle of Activity, Fragment, and ViewModel, the internal workings of ViewModel, Dependency Injection principles, Activity launch modes, and general Android best practices.
I was asked to choose a favorite Android application and design its High-Level Design (HLD) and Low-Level Design (LLD). I selected the Google Search App.