Interview experience
Groww Interview Questions
Overview
Section titled “Overview”Groww’s interview loop splits by entry path - a DSA-heavy Online Assessment for campus SDE hires versus a take-home assignment for off-campus/intern roles - before converging on two technical rounds and a Culture/HR close.
Groww interview process at a glance
Section titled “Groww interview process at a glance”| Round | Duration | What they test |
|---|---|---|
| Online assessment (campus) | 60-90 min | 1 medium + 1 hard DSA problem, ~12 MCQs on CN/DB/OS |
| Take-home (off-campus intern) | 24-72 hrs | Working demo, edge cases, stack fit |
| Technical 1 | ~60 min | More DSA + CS fundamentals / projects |
| Technical 2 / EM | ~60 min | Projects, light design, more DSA or stack depth |
| Culture / HR | 20-30 min | Why Groww, Bengaluru, how you get unstuck |
Online assessment / take-home
Section titled “Online assessment / take-home”Campus hires get a DSA-first OA - 1 medium (typically worth around 50 marks) and 1 hard problem (around 100 marks) plus roughly a dozen MCQs on computer networks, databases, and OS. Off-campus web/app intern tracks often swap this for a take-home assignment - a working demo or APK judged on completeness, not just DSA.
Common questions
- One medium and one hard DSA problem (arrays, trees, graphs, hash maps)
- MCQs on computer networks, databases, and operating systems
- Take-home track: build a small feature or app with a working demo, README, and edge-case handling
Technical interviews
Section titled “Technical interviews”Both tracks converge here: more DSA under time pressure, CS fundamentals, and a real deep-dive into your internship or project work. Off-campus candidates on web/React Native tracks get stack-specific machine-coding questions layered in.
Common questions
- Additional DSA problems (interviewers often re-probe the same topics from the OA)
- Backend/SQL/OS/OOP deep-dive tied to an internship project
- Rebuild Redux (or a similar state-management pattern) from scratch
- Design handling for multiple concurrent WebSocket connections
- Light system/feature design - trade-offs and why you chose them
Round-by-round breakdowns are on the Groww interview experience page.
Culture / HR round
Section titled “Culture / HR round”A closing 20-30 minute conversation on motivation and fit - candidate write-ups consistently flag “why Groww” (naming a real product surface, not “fintech unicorn”), willingness to join in Bengaluru, and a genuine story about debugging without help.
Common questions
- Tell me about yourself?
- Why Groww?
- Describe a feature or issue you owned end-to-end, from the first line of code to it running in production.
- Tell me about a time you chose a simpler design over a fancier one - what trade-off did you accept, and why?
- How do you get unstuck on a problem when there’s no senior engineer around to ask?
Sample answer frameworks for each of these are on the Groww HR interview questions page.
Frequently asked questions about Groww interviews
Section titled “Frequently asked questions about Groww interviews”What is the Groww interview process for freshers?
Groww’s process depends on the track: campus hires usually start with an Online Assessment (60-90 minutes - 1 medium and 1 hard DSA problem plus around 12 MCQs on CN/DB/OS), while off-campus intern applicants often get a take-home assignment (24-72 hours) instead. From there it’s two technical rounds (around 60 minutes each) covering DSA, CS fundamentals, and project/stack depth, followed by a Culture/HR round (20-30 minutes).
What questions are asked in Groww interviews?
Groww interviews cover competitive-programming-adjacent DSA (arrays, trees, graphs, hash maps), take-home coding assignments testing a working demo and edge-case handling for off-campus roles, project deep-dives (especially internship work), and questions on ownership (features you drove end-to-end) and simplicity in design trade-offs, reflecting Groww’s product-simplicity culture.
How many rounds are there in the Groww interview?
Groww typically runs 4 rounds: an Online Assessment or take-home assignment, two technical/engineering-manager rounds, and a Culture/HR round. Exact structure varies by whether you’re a campus or off-campus/intern candidate - some off-campus loops report an extra machine-coding or low-level-design round.
Does Groww’s interview process differ for web/app intern roles?
Yes. Off-campus web and React Native intern tracks often start with a take-home assignment (a working demo or APK, sometimes graded on TypeScript code quality) instead of a DSA-only OA, then move into a stack-heavy technical round - JS/TypeScript output questions, Redux-from-scratch, or multi-WebSocket design - before culture fit. Campus SDE hiring is closer to a standard DSA-first loop.
How should I prepare for Groww interviews?
For Groww, practice medium-to-hard DSA (arrays, trees, graphs, hash maps) under time pressure, be ready to build and explain a small working project if you’re on the take-home track, prepare a clear story with a real metric about a feature you owned end-to-end, and think through why you’d choose a simpler design over a more complex one.