Groww Interviews

Round 1: Resume Shortlisting

I applied for the SDE Intern (React Native) position at Groww in November 2025 through a Google form shared by HR on LinkedIn. My application was successfully shortlisted.

Round 2: Assignment

Following the shortlisting, HR provided me with an assignment. The task involved building a stock broker application using React Native. I completed and submitted the assignment.

Round 3: Technical Discussion Round

A technical discussion round was scheduled with an SDE-2. This round involved various questions and a live coding exercise:

• We discussed React internals, covering topics such as hooks, class components, and memoization.
• There was an in-depth discussion on React Native internals, including the differences between the Old Architecture and New Architecture, how the bridge works, how to write a JS bridge over native modules, an overview of the new architecture, strategies for optimizing React Native apps, the use of Expo, and secure storage mechanisms.
• I also participated in a live coding session on Codesandbox, where I was asked to build a todo list with features like adding new items and searching existing ones.

Round 4: Hiring Manager Round

The next day, I had a hiring manager round with an SDE-4. This discussion focused on my prior experience and behavioral aspects:

• We talked about my internship experience, specifically what projects I had worked on and my experience using Expo.
• We briefly revisited the New Arch vs. Old Arch discussion.
• I was asked questions about why I considered myself a good fit for Groww and the specific role.
• The manager also inquired about my strengths and weaknesses.
• We discussed my motivations for joining Groww.
• Finally, I was asked about how I handle management interactions and approach various tasks.

Verdict

I was selected for the SDE Intern role. However, I decided not to join Groww because the offered stipend was less than my current internship's compensation, and I also have a Pre-Placement Offer (PPO) at my current company. Despite not accepting, it was a great learning experience for me.

I received an interview opportunity at Groww for an SDE intern role focused on AI/LLM, thanks to a referral from an employee. All the interview rounds were scheduled for the same day.

Round 1 — DSA (1 hour): This round focused on core data structures and algorithms. I was given two LeetCode problems: "Single Element in an Array" and "Container With Most Water." For both problems, I first presented a brute-force solution and then discussed an optimized approach. After solving, the interviewer briefly asked about my projects. I felt this round went quite well.

Round 2 — DSA + AI (1 hour, back-to-back): The first half of this round involved a deep dive into my AI/GenAI projects and my understanding of LLMs. This seemed to be aimed at gauging my interest and knowledge in the field. In the second half, I faced a design-style problem, which was not a typical DSA question. The task involved forming pairs (specifically, 3 girls and 2 boys) based on certain priorities. I had to write pseudocode and explain my reasoning for the solution. Overall, this round also seemed to go fine.

HR Round & Outcome: An HR round was initially planned, but just before it could start, I was informed that the feedback from the previous rounds wasn't positive. Consequently, the HR round did not take place, and I did not move forward in the process.

I recently got the opportunity to interview for the SDE Android Intern role at Groww.

I had applied through a Google Form on 13th May 2025, and on 25th June 2025, I received an assignment to build a stock display app using Kotlin (everyone who applied received the same assignment). I submitted it on 4th July 2025, and got an interview call from HR on 22nd July 2025.

During the interview, most of the discussion revolved around the assignment. I began by explaining the app, its architecture, and why I chose the MVVM pattern with Repository. I was asked: • What is MVVM architecture? • What happens when the user rotates the screen? • What are lambda functions and their use cases? • How did I implement the bottom navigation bar? • What is dependency injection? • How does my ViewModel help retain data across screen rotations? • What is the Activity lifecycle?

I was also given a scenario: If a screen shows a RecyclerView with payment options like PhonePe and Cash on Delivery, how would I ensure that only one card is selected at a time? I had to explain how I would manage selection and persist the user’s choice.

There were also several questions around data handling. I explained that I implemented caching — if data is in the cache, I use it; otherwise, I make an API call. I was asked where I handled the logic to validate the cache and how I structured my API calls.

The interviewer also asked me about the numbers mentioned in my resume — how I calculated them and what they represented.

There were some Kotlin-specific questions too: • What is a data class? • Can a data class be empty? • How is it different from a regular class?

In terms of feedback, I was told that I could have gone deeper into how things actually work under the hood, which is something I’ll definitely work on moving forward.

Although I wasn’t selected (HR informed me the next day), it was a valuable learning experience.

I’m sharing this because while preparing for my interview, I struggled to find real Android interview experiences online. Hopefully, this helps someone else who’s preparing for theirs.

🚀 Hey folks! After sharing my SDE-2 interview experience at Amazon (and receiving some really positive feedback 🙌), I thought I’d drop another one here — this time from a recent interview with Groww.

Hope you find it helpful — and as always, would love to hear your thoughts and feedback! Let’s dive in 👇

🎓 Background: B.Tech in Mechanical Engineering from one of the Top 10 IITs 10 months at a Big Service-based MNC 3 years in a Product-Based Company Current Role: SDE-II in Product Based Company

🧠 Round 1: DSA Duration: 1 Hour Problem: Topological sort — Jobs represented as strings, Graph was disconnected and had cycles. Goal: Print all jobs to be done before a given job. ✅ Solved in 45 mins ✅ Ran multiple test cases — all passed 🎯 Smooth ride.

💻 Round 2: Machine Coding Duration: 2 Hours Task: Build a scalable cache (end-to-end) only this statement was the problem & I was supposed to assume things by myself. Implemented features:- add, contains, invalidate, validate, setMaxSize, fetchSize, printMap, Eviction logic via queue (FIFO). Hardcoded test data to verify functionality.

🔍 After 1.5 hrs, the interviewer joined. Code worked fine, but...

💬 Feedback:

“This isn’t scalable. FIFO isn’t enough — what if we want different eviction logic?”

✅ I explained how to make it scalable using interfaces 😕 Still didn’t seem impressed.

🏗️ Round 3: High-Level Design Duration: 1 Hour Task: Design a Stock Market System to handle: Events: buy, sell, stop-loss Incoming via queue, with 10ms SLA & we have to place the order within that time. 📌 Discussed:- Sharding, Indexing, Partitioning, Caching Happy flows, retries, failure handling, schedulers

👎 Feedback (a week later):

“Basic implementation — didn’t extend to multi-exchange/segment support. Needed more focus on scalability.” It seemed the Machine Coding round didn’t fully meet the interviewer’s expectations, which may have impacted the final decision during the debrief.

😅 Verdict: Rejection #13 in the past year 🥲 Added proudly to my growing “Hall of Fame: Close but No Offer” wall 😂

Still learning. Still building. Still growing. 💪 If you’ve faced something similar — you’re not alone. Let’s keep pushing!

Link for my Amazon SDE-II Experience :- https://leetcode.com/discuss/post/6654251/amazon-l5-sde-ii-april25-hyderabad-by-a2-umh1/comments/2959468/

Hello All,
I gave Groww SDE3 interview in December 2024. Sharing the questions and process.

Round 1
Machine Coding

Duration - 2 hour
Question - Design a stock exchange platform. Buyers and sellers can place bids for stocks. Buyer can buy at an amount lower or equal to the bid. Seller can sell at an amount higher or equal to the bid.
Outcome - Expectation was to implement a working solution. I was able to implement it and demonstrate working on examples provided by the interviewer.
Verdict - Positive

Round 2
HLD

Duration - 1 hour
Question - Design a system to monetize an API-based service (e.g., Google Maps) with subscription plans. The system should:
1. Track incoming API calls per user.
2. Enforce usage limits based on subscription tiers.
3. Proactively notify users as they approach their usage limits.

Outcome - Was able to provide a near-satisfactory solution.
Verdict - Positive

Round 3
LLD

Duration - 1 hour
Question - Design system to create, store, update SIPs. Create and schedule transactions corresponding to the SIPs.
Outcome - Interviewer grilled a lot around some concepts like versioning, DB schema, concurrency. But finally, he seemed satisfied with the answers.
Verdict - Positive

Round 4
HM

Duration - 1 hour
Question - Standard HM questions around past project discussion, ideation to deployment cycle, behavioral questions.
Outcome - Interviewer was happy.
Verdict - Positive

Round 5
HR

Duration - 1 hour
Question - Standard HR questions.
Outcome - Interviewer was happy.
Verdict - Positive

Final verdict was hired.

I applied for the SDE Intern (Frontend) position at GROWW in March 2024 as a fresher from a Tier-3 college with about 5 months of prior internship experience. The role offered a 12-month internship with a PPO opportunity and a competitive stipend and CTC. The entire hiring process consisted of four rounds, though I only made it through the first two technical rounds.

Round 1: Resume Shortlisting
I applied through a Google form that was shared on LinkedIn by an SDE-2 at GROWW. My resume, likely due to my existing internship experience, got shortlisted.

Round 2: Assignment Round
This round was a take-home assignment. I was tasked with developing a complete checkout experience. This included building a CART page with coupon functionality, a PAYMENT DETAILS page supporting UPI and card payments, and a RANDOM PAYMENT CONFIRMATION page that could show success, failed, or pending statuses. Additionally, the application needed to support dynamic theme configuration fetched from an API. I was expected to use Next.js, TypeScript, Zustand/Redux, and Tailwind for the implementation.

Round 3: Technical Round
This round began with my basic introduction, followed by an in-depth discussion about the assignment I had built, including several follow-up questions. We then moved on to a detailed discussion of the projects listed on my resume and my past work experience. The interviewer also asked several basic theoretical questions about React, such as the differences between hooks and functional components, and the distinctions and use cases for useMemo and useCallback in a production environment. Other theoretical questions covered the differences between ~ and ^ in package.json files, any vs unknown in TypeScript, and interface vs type.

The actual deciding factor came down to a couple of problem-solving questions. First, I was given a deeply nested JavaScript object and asked to write a function that could access a property using a string path like "user.config.details.name.first". Second, I was asked to provide polyfills for Promise.any and other Promise methods. There were also some low-level DSA questions, like identifying the sorting algorithm used in C++ STL's inbuilt sort and explaining priority queues for min/max heaps, though no LeetCode-style coding problems were asked.

Round 4: HR Round
Unfortunately, I couldn't clear the technical round and didn't make it to the HR round. I assume it would have involved typical HR questions and wouldn't have been overly difficult.

Verdict:
I was ultimately rejected because I wasn't familiar with implementing polyfills for Promises and got stuck on the deeply nested object access question.

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.