Zerodha’s interview process for software engineers usually starts with a resume screen that looks for markets curiosity, side projects and a readable Git history, then a 60-90 minute HackerRank test and/or a 90-120 minute take-home build that must run and come with a README. One or two 45-60 minute technical rounds ask you to defend your design, trade-offs and production thinking, and a culture round on ownership, simplicity and fit with Zerodha’s bootstrapped model weighs as heavily as the technical rounds.
Round-wise process at a glance
| Round | Typical format | What clears you |
|---|---|---|
| Resume screening | Async review | Fintech/markets curiosity, side projects, readable Git history |
| OA / take-home | HackerRank 60–90 min and/or 90–120 min build | Correct, runnable solution + README |
| Technical × 1–2 | 45–60 min each | Defend design, trade-offs, production thinking |
| Culture / HR | 30–45 min | Ownership, simplicity, alignment with bootstrapped model |
Timelines of 2–6 weeks between stages are commonly reported - keep one owned project warm for deep follow-ups.
A published Zerodha take-home assignment
Source: GitHub, navneet35371/zero (a public repo labelled as a Zerodha assignment)
There are few detailed public accounts of Zerodha engineering interviews; this repo shows the shape of one take-home brief.
- Data script: download the Equity Bhavcopy zip that BSE publishes daily, extract and parse the CSV, and store code, name, open, high, low and close in Redis using suitable data structures.
- Web app: a small CherryPy app with an HTML5/CSS3 page that shows the top 10 entries from Redis in a table, plus a search box that finds entries by name. The brief asks for the page to look good.
Key takeaways: The brief is script + datastore + minimal UI, a useful practice template. Expect to defend your Redis key design and how the daily refresh works if you submit something similar.
Sample answers for high-frequency questions
Technical
Q. Simple order-book mental model.
A. Bids and asks sorted by price-time priority; matching pairs compatible orders; emit trades and update holdings. Mention partial fills, cancellation, and idempotent order submission if retries exist.
Q. How do you show ownership in an interview?
A. Narrate design → implementation → testing → deploy → post-launch fix with one metric (latency, error rate, users served). Say which decisions were yours vs the team’s.
Q. Rate limiter in one minute.
A. Token bucket for bursts; fixed window is easier but unfair at boundaries; distributed setups use Redis with TTL; discuss 429 responses and client backoff.
Q. Stock price service sketch.
A. Ingest ticks via Kafka (or similar), fan-out with pub-sub, WebSockets to clients, handle slow consumers with backpressure and reconnect state - you do not fan-out every tick through a relational DB.
Culture / HR
Q. Why Zerodha?
A. Tie to correctness when moving money, learning on a lean team, and one concrete thing you read (engineering blog, product behavior on Kite during market open). Avoid salary-first framing.
Q. What would you change if you had more time on the assignment?
A. Pick one: integration tests, observability, input validation, deployment script - and say what you deliberately skipped for scope.
Dense prep checklist
Before you apply
- Use Kite and read at least two posts on Zerodha’s tech/engineering blog
- Prepare one end-to-end project story with GitHub link and honest README
Assignment / machine coding
- Build a mini order book or rate limiter in Go or Python; add a Makefile or docker-compose for reviewer sanity
- Write
DESIGN.mdwith assumptions, non-goals, and failure modes
Technical rounds
- Drill SQL window functions, EXPLAIN plans, and DECIMAL money types
- Draw the order state machine until you can do it without notes
Culture round
- Three STAR stories: ownership, failure/learning, disagreement resolved
- Rehearse “Why not Flipkart/Groww?” with respect - compare operating model, not trash talk
Sources
- Zerodha Software Engineer Interview - SpaceComplexity
- Zerodha System Design Interview - SpaceComplexity
- Zerodha SWE questions - InterviewEra
- Public Zerodha-style assignment (BSE bhavcopy + Redis) - GitHub
Confirm stages with your recruiter. For the hub and HR prompts, see the Zerodha hub and Zerodha HR page.
Similar companies
Groww · Razorpay · PhonePe · CRED
Ready to prepare? Ship one small fintech-adjacent service, defend it out loud, and read Zerodha’s primary sources - not recycled interview lists alone.