Groww Interview Questions and Answers
Last updated 2026-11-19
Groww is an investing platform, so its engineering interviews commonly mix data structures with design problems that look like real fintech systems: order handling, wallets and ledgers, price alerts and real-time market data. This page offers practice questions on those themes, with worked answers.
They are practice questions on the commonly reported topics, not real papers. For timed problems see Groww coding round questions, and for the design approach read how to crack the system design interview.
Rounds as commonly reported
Candidate accounts describe an online coding test or DSA round, a machine-coding round where you build a small working system in a fixed time, a system design round for experienced roles, and a hiring-manager or culture round. Groww has not published a fixed process, so use this as a rough pattern and rely on your recruiter's instructions.
Machine coding in practice
In a machine-coding round you are given a spec, such as a stock exchange order book or a wallet, and are judged on working code, extensibility, naming and handling edge cases, usually in 90 minutes or so. Start with entities and interfaces, then the core flow, then validation; avoid spending time on frameworks.
Hiring status
We hold no sourced hiring dates, numbers or process facts for Groww and no /hiring page exists for it on this site, so none are stated. For current roles, use Groww's own careers site.
Groww Interview Questions and Answers: questions with worked answers
1 Design a simple stock order book with price-time priority.
hardKeep a max-heap of buy orders keyed by price (then arrival time) and a min-heap of sell orders. For an incoming buy, while the best ask is at or below the buy price, match at the resting order's price, reduce quantities, emit trades, and remove filled orders; leftover quantity rests in the book. Matching on arrival time within a price level ensures fairness. Cancel orders with lazy deletion. Use integer prices and quantities to avoid rounding errors.
2 Design a wallet with transfers that never lose or create money.
hardUse a double-entry ledger: every transfer writes two immutable entries, a debit and a credit, in one database transaction, and balances are derived or maintained as a projection. Protect against concurrent transfers by locking the rows in a fixed order (by account id) to avoid deadlocks, or with optimistic versioning. Make the API idempotent with a client-supplied key stored with a unique constraint, so retries do not double-post. Store money as integer minor units.
3 Why should money never be stored as a float?
easyBinary floating-point cannot represent most decimal fractions exactly, so 0.1 plus 0.2 is not exactly 0.3, and rounding errors accumulate across many operations. Use integers in the smallest unit (paise) or a decimal type with an explicit rounding mode. Define the rounding rule once and apply it consistently, for example when splitting a charge.
4 Design a price alert system for millions of users.
hardUsers set alerts like "notify when stock X crosses price P". Index alerts per stock in sorted structures (one for above-thresholds, one for below), so on each price tick you only inspect the alerts between the old and new price. Triggered alerts are removed and sent to a notification queue. Shard by stock symbol, process ticks from a partitioned stream, and make notifications idempotent. Keep alerts in a database for durability and rebuild the in-memory index on restart.
5 How would you stream live prices to a mobile app?
mediumMaintain a persistent connection with WebSocket (or server-sent events for one-way data). A gateway tier holds connections; clients subscribe to symbols, and the gateway subscribes to a pub-sub feed for those symbols and fans out updates. Reduce load by throttling or conflating updates to a fixed rate per client (keep the latest price), compressing messages, and dropping slow consumers. Reconnect with a snapshot followed by deltas so state stays consistent.
6 Explain database transactions and the problem of lost updates.
mediumA transaction groups operations that succeed or fail together. A lost update happens when two transactions read the same balance, both compute a new value and the second write overwrites the first. Fix it by locking the row with SELECT ... FOR UPDATE, using an atomic update such as balance = balance - x with a check, or optimistic locking with a version column and retrying on conflict.
7 How do you make a Kafka consumer process each message effectively once?
hardKafka delivers at least once to consumers that commit offsets after processing. To make the effect exactly-once, make the handler idempotent: store a message id (or a business key) with a unique constraint, or use an upsert, so reprocessing has no effect. Where the output is also Kafka, transactions can commit offsets and produced messages atomically. Handle poison messages with a dead letter topic after a bounded number of retries.
8 Write SQL for each user's total invested amount and the number of orders in the last 30 days.
mediumJoin users to orders with a date filter in the join condition, not the where clause, so users with no recent orders still appear with zeros. Use COALESCE to turn nulls from SUM into 0. Date functions differ by database; the idea is the same.
sqlSELECT u.user_id, COALESCE(SUM(o.amount), 0) AS invested, COUNT(o.order_id) AS orders_30d FROM users u LEFT JOIN orders o ON o.user_id = u.user_id AND o.created_at >= CURRENT_DATE - INTERVAL '30 days' GROUP BY u.user_id;9 Compute the future value of a monthly SIP.
easyWith monthly contribution P, monthly rate r and n instalments paid at the start of each month, the future value is P times ((1 + r)^n minus 1) divided by r, times (1 + r). If paid at month end omit the last factor. The annual rate is converted to monthly by dividing by 12 for a nominal rate, which is the convention to state. This is an illustration of the formula, not investment advice.
pythondef sip_future_value(monthly, annual_rate, months, start_of_month=True): r = annual_rate / 12 if r == 0: return monthly * months fv = monthly * ((1 + r) ** months - 1) / r return fv * (1 + r) if start_of_month else fv10 Design a rate limiter for an order placement API.
mediumLimit per user and globally. Use a token bucket in a shared store such as Redis with an atomic script so concurrent requests cannot both take the last token. Return 429 with Retry-After. For order APIs, never silently drop a request: respond with a clear rejection, and combine rate limits with idempotency keys so a retry after a timeout is safe.
11 Tell me about a time you owned something critical end to end.
easyPick a project where you handled design, build, rollout and monitoring. Describe a risk you identified early (for example a data migration), how you tested and rolled out gradually, and what you did when something went wrong. Quantify the outcome and stress what you learned about operating software, which matters in finance.
12 Why Groww?
easyConnect it to the product and the engineering: building for first-time investors at scale, where reliability and clarity matter. Name a specific problem, such as keeping prices fresh during market-open spikes, and why it interests you. Avoid commenting on investment returns.
Frequently asked questions
Does Groww have a machine-coding round?
Candidate accounts commonly mention one for engineering roles. Practise building small systems such as an order book or wallet in 90 minutes.
Which language should I use?
Java, Kotlin, Python and Go all appear in fintech stacks. Use the language you know best unless the role specifies one.
Is finance knowledge required?
Not usually, but knowing order books, ledgers and SIP basics helps in design discussions.
Where can I find openings?
On Groww's own careers site. This site has no sourced hiring data for the company.
Related guides
More in Company Interview Questions
- HCLTech Coding Round Questions with Solutions
- HCLTech Interview Questions for Freshers
- Hexaware Coding Round Questions with Solutions
- Hexaware Interview Questions for Freshers
- Honeywell Coding Round Questions with Solutions
- Honeywell Interview Questions and Answers for India Engineering Roles
- HSBC coding round questions with solutions
- HSBC interview questions with answers (technology graduates)
- IBM coding round questions
- IBM interview questions and answers
- Info Edge (Naukri) Interview Questions with Answers
- Info Edge Coding Round Questions