The hiring process
| Round | Format | What's tested |
|---|---|---|
| Online Assessment | ~60–90 min | Screening MCQs and coding |
| Coding / DSA Interview | ~60 min | Algorithmic problem-solving |
| Machine Coding | ~90 min | Building a working system |
| High-Level Design | ~60 min | Scalable, finance-grade system design |
Process and cutoffs vary by drive/team and change over time — confirm on the official careers page.
Round-by-round: exactly what's asked & how to prepare
Online Assessment
~60–90 minA screening test typically combining around 10 MCQs on CS fundamentals with one coding problem. The coding question is usually medium and pattern-based. Clearing it reliably requires both breadth on fundamentals and a solid coding foundation.
- CS fundamentals MCQs (OS, DBMS, networks)
- One medium coding problem (DP or greedy)
- Complexity reasoning
- Careful problem parsing under time
- Revise OS, DBMS, and networking MCQ topics
- Solve LeetCode mediums in DP and greedy
- Practice quick, accurate MCQ recall
- Use GeeksforGeeks fundamentals sheets
- Neglecting MCQ fundamentals while over-focusing on coding
- Skipping edge cases on the coding problem
- Solid MCQ accuracy plus a passing coding solution
- Efficient time split across sections
Coding / DSA Interview
~60 minA live round with roughly two LeetCode-medium problems, occasionally a small third or extra CS questions. Interviewers evaluate approach, edge cases, and complexity, and expect you to reason aloud. Clean, correct code within the hour is the goal.
- Arrays, strings, and hashing
- Trees, graphs, and BFS/DFS
- Dynamic programming and greedy
- Binary search and two pointers
- Complexity and edge-case discussion
- Grind LeetCode mediums across core patterns
- Practice solving two problems in one timed hour
- Rehearse explaining trade-offs while coding
- Use NeetCode 150 for structured coverage
- Missing edge cases and off-by-one errors
- Not finishing both problems due to slow starts
- Correct, clean solutions with clear reasoning
- Good pace across two problems
Machine Coding
~90 minA hands-on round, often led by an SDE-2, to build a small but complete system with clean, extensible object-oriented design. A common style is an expense-sharing or settlement system with users, groups, and split logic. They grade working functionality, structure, and why you chose each data structure.
- Modeling entities with clear class responsibilities
- Split/settlement or transaction logic
- Justifying data-structure choices explicitly
- Extensibility and clean interfaces (SOLID)
- Handling edge conditions in a running build
- Practice Splitwise, parking-lot, and cart katas
- Master SOLID and core design patterns
- Rehearse a working build inside 90 minutes
- Prepare to justify every data-structure choice
- Choosing a data structure without a clear reason
- Leaving the build non-functional at time
- Working, extensible code with justified choices
- Clean class boundaries and readable structure
High-Level Design
~60 minA design round on a scalable system, frequently themed on trading or market-event handling (buy, sell, stop-loss) via queues under SLA requirements. Expect deep discussion of throughput, consistency, latency, and failure handling. Requirements-clarification and trade-off reasoning drive the evaluation.
- Event-driven design with queues and workers
- Handling order types under strict SLAs
- Consistency, idempotency, and reliability for money flows
- Scaling, caching, and data-store choices
- Latency and throughput trade-offs
- Study event-driven and queue-based architectures
- Practice designing a stock/order-matching system aloud
- Learn idempotency and consistency patterns for payments
- Use the free System Design Primer on GitHub
- Skipping requirement and SLA clarification
- Ignoring reliability and consistency for money-critical flows
- Structured, trade-off-aware design under SLAs
- Attention to reliability and correctness for financial data
What to master
- Data structures and algorithms
- Dynamic programming and greedy
- Machine coding / low-level design
- Object-oriented design and SOLID
- High-level and event-driven system design
- Queues, consistency, and SLAs
- CS fundamentals (OS, DBMS, networks)
- Complexity analysis
Eligibility
Role-based: SDE roles span junior to senior; juniors need strong DSA and CS fundamentals, while SDE-2 and above face heavier machine-coding and design rounds. Specifics vary by team and level.
Groww salary & compensation (2026)
Indian fintech unicorn; strong startup comp + ESOPs, aggressive for senior talent.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| SDE 1 | 0–2 yrs | ₹18–30 LPA | — | base + ESOPs |
| SDE 2 | 2–4 yrs | ₹30–50 LPA | — | ESOP grant scales |
| Senior SDE / SDE 3 | 4–7 yrs | ₹50–80 LPA | — | equity a large share pre-IPO |
| Staff / EM | 7–11 yrs | ₹80 LPA–1.3 Cr | — | bigger ESOP grants |
| Principal / Director | 11+ yrs | ₹1.3–2 Cr | — | leadership; heavy equity |
How the package is structured
- Comp = base + ESOPs; post-IPO/late-stage liquidity makes equity more real.
- Among the better-paying Indian fintech startups, competitive with FAANG-India cash at senior levels.
- ESOP upside tied to valuation growth and liquidity events.
- Fast-track promotions common; senior hires negotiated aggressively.
Indicative 2026 market ranges aggregated from public sources (levels.fyi, Glassdoor, AmbitionBox, candidate reports). Compensation varies widely by location, team, level calibration, and negotiation — use these as directional benchmarks, not guarantees.
Your prep plan
- Day 1–3: Grind LeetCode mediums across core patterns
- Day 4–5: Revise OS, DBMS, and networking for MCQs
- Day 6–8: Practice machine-coding katas (Splitwise, cart)
- Day 9–11: Study event-driven and finance system design
- Day 12–13: Mock DSA and machine-coding rounds under time
- Day 14: Mock HLD on a trading system and review weak spots
Want this plan dated to your interview?
Upload your resume and tell Whis your interview date — get a personalized, day-by-day plan built around your gaps, then run Whis live in the interview.
Get my personalized planFrequently asked questions
How central is machine coding at Groww?
Very. The build round, often run by an SDE-2, is a key filter, and justifying your data-structure choices is explicitly evaluated.
Are the design rounds finance-specific?
Often yes. Prompts frequently involve trading, orders, and market events under SLAs, so understand queues, consistency, and reliability for money flows.
How many rounds should I expect?
Usually four (OA, DSA, machine coding, HLD). Senior candidates may see an extra design deep-dive or HR round.