groww logo
Groww· SDE 2

Groww | SDE 2

Result
Rejected
Location
Bangalore
Experience
3.5 years
Posted
16 Apr 2024
762 reads

Summary

I recently interviewed for an SDE 2 role at Groww in Bangalore. The interview process consisted of problem-solving, a machine coding challenge for an expense-sharing application, and a system design round. Although I performed well in most aspects, I was ultimately rejected after the system design round.

How it went

I secured an interview opportunity at Groww for an SDE 2 position after receiving a referral through LinkedIn, which was followed by an HR call. The entire interview process was structured with elimination rounds.

Round 1: Problem Solving
This round involved two coding questions. The first was a medium-difficulty LeetCode problem based on Linked Lists, for which I was able to provide a fully functional and correct solution. The second question was a hard problem involving Trees, specifically requiring the use of Lowest Common Ancestor (LCA). I thoroughly discussed my approach and outlined how to reach an optimal solution, but unfortunately, I couldn't complete the coding implementation due to time constraints.

Round 2: Machine Coding
For this round, I was tasked with building an expense-sharing application, similar in functionality to Splitwise. I successfully created all the necessary class DTOs (Data Transfer Objects) and implemented several important APIs. A crucial aspect of this round was continuous discussion and communication while coding, ensuring the interviewer was aware of my architectural choices—whether it was MVC or another pattern—and my progress.

Round 3: System Design
The system design round was tailored to my resume, focusing on the High-Level Design (HLD) of one of my past projects. I used an online editor, like draw.io, to illustrate and explain everything in detail, and the interviewer appeared satisfied with my explanations. However, I was rejected after this round because I failed to adequately explain the functionality of a specific, random queue system the interviewer inquired about. Other than that particular question, I felt the round went quite well.

Questions asked (1)

  1. 01

    Machine Coding: Expense Sharing App (Splitwise Clone)

    Data Structures & Algorithms

    Design and implement a machine coding solution for an expense-sharing application similar to Splitwise. The implementation should include necessary class DTOs and core APIs. The process emphasized continuous discussion and communication of architectural choices (e.g., MVC) while coding.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Groww recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!