The hiring process
| Round | Format | What's tested |
|---|---|---|
| Application & Screening | ~30 min | Relevance and fundamentals |
| Technical Assessment / Coding | ~60–90 min | Practical coding and problem-solving |
| Technical Deep-Dive | ~45–60 min | Depth of knowledge and system thinking |
| Culture / Founder-Style Fit | ~30–45 min | Ownership and long-term fit |
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
Application & Screening
~30 minA recruiter or engineer reviews your background and interests, sometimes with a short technical chat. The filter is strongly on demonstrated ability to build things and clarity about what you have shipped. Open-source or side projects help a lot.
- Walkthrough of a project you built end-to-end
- Your comfort with the language and stack you claim
- Why Zerodha and fintech
- Basic CS and web fundamentals
- Tighten your resume around things you actually built
- Have a public repo or demo ready to show
- Be able to explain one project's architecture in two minutes
- Read about Zerodha's tech culture on their Tech blog
- Listing skills you cannot demonstrate
- No shippable project to point to
- Being unclear about your own contribution
- Evidence of building and shipping
- Clear, honest self-assessment
- Genuine product curiosity
Technical Assessment / Coding
~60–90 minA coding test or take-home-style task emphasizing algorithm design, data structures, and debugging. Zerodha leans practical, so a task may resemble a real feature rather than a contest puzzle. Clean, working, readable code is the goal.
- Parsing and transforming market/CSV-style data
- Building a small API or CLI feature correctly
- Debugging a subtly broken function
- Efficient use of data structures on realistic inputs
- Practice medium DSA plus small 'build a working feature' tasks
- Sharpen debugging: read code, find the bug, fix cleanly
- Get fluent in your primary language's standard library
- Solve a few HackerRank/LeetCode problems end-to-end in one sitting
- Over-engineering a simple task
- Leaving code messy or untested
- Getting stuck on cleverness instead of shipping something correct
- Working, readable solution
- Pragmatic choices
- Solid debugging instinct
Technical Deep-Dive
~45–60 minA deeper discussion on your projects, language internals, databases, and how you would handle scale and correctness during market hours. Interviewers value applied knowledge and how well you articulate complex ideas. Design questions are grounded and practical.
- Handling concurrency and race conditions in trading-like flows
- Database indexing and query performance
- Idempotency and correctness in money movement
- Trade-offs in a design you shipped
- Review concurrency, transactions, and ACID properties
- Understand DB indexing and when queries get slow
- Prepare to defend design decisions with reasoning
- Study a lightweight system-design primer for grounded questions
- Textbook answers with no applied context
- Ignoring correctness/consistency in a fintech setting
- Unable to justify past design choices
- Applied, first-principles reasoning
- Awareness of correctness and edge cases
- Clear communication of complex ideas
Culture / Founder-Style Fit
~30–45 minA conversation about how you work, your motivation, and whether you thrive in a lean, high-ownership environment. Zerodha values people who stay and build, not resume-hoppers. Expect honest, no-frills questions.
- How you operate with minimal supervision
- A time you owned something end-to-end
- Why a bootstrapped, product-first company appeals to you
- How you keep learning
- Prepare stories showing autonomy and ownership
- Have a sincere reason for wanting Zerodha specifically
- Reflect on how you handle ambiguity
- Prepare grounded questions about the team and stack
- Coming across as needing constant direction
- Generic 'big brand' motivations
- Overselling instead of being genuine
- High ownership and self-direction
- Authentic fit with lean culture
- Long-term intent
What to master
- Data structures & algorithms
- Practical / machine coding
- Databases & indexing
- Concurrency & transactions
- Web fundamentals & APIs
- System design (grounded)
- Debugging
- Fintech correctness
Eligibility
open — role-based (strong bias toward demonstrable builders)
Zerodha salary & compensation (2026)
Bootstrapped and profitable; pays competitive-to-strong cash but with no ESOPs (private, no external funding) — comp is all cash.
| Role / Level | Experience | India — total CTC | US — total comp | What to know |
|---|---|---|---|---|
| Engineer (new grad) | 0–2 yrs | ₹18–30 LPA | — | all-cash; no ESOPs |
| Software Engineer | 2–4 yrs | ₹30–48 LPA | — | cash-only comp |
| Senior Engineer | 4–8 yrs | ₹48–75 LPA | — | strong cash bands |
| Lead / Staff Engineer | 8–12 yrs | ₹75 LPA–1.2 Cr | — | scope-driven |
| Principal / Head | 12+ yrs | ₹1.2–1.8 Cr | — | rare; small senior team |
How the package is structured
- Comp is entirely cash — no equity/ESOPs — so the fixed number is effectively the full package.
- Lean, high-ownership engineering culture; individual impact is large and rewarded in cash.
- Profit-sharing/bonuses can boost total comp in strong years.
- Since there's no equity upside, benchmark the cash offer directly against ESOP-inclusive peers.
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
- Week 1: revise medium DSA plus 3–4 realistic 'build a feature' tasks
- Week 1: polish one public project you can demo and defend
- Week 2: study concurrency, transactions, and DB indexing deeply
- Week 2: practice explaining a design decision with trade-offs
- Prepare ownership-focused STAR stories
- Read Zerodha's tech blog to understand their pragmatic culture
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
Does Zerodha ask hard competitive-programming problems?
Generally no. It leans toward practical, buildable tasks and applied fundamentals. Being able to ship correct, readable code matters more than solving contest-level puzzles.
Do side projects or open source really help?
Yes, strongly. Zerodha's builder culture rewards visible evidence that you ship, so a solid public project can carry real weight in the screen.
How many rounds should I expect?
Usually 2–3 core rounds after screening, though it can extend to 4–5 depending on the role and level. The process is comparatively short and grounded.