How to Answer: "Why Do You Want to Work at Zerodha?"

The answer must show that you understand an unusual company, not just a large one. Zerodha is one of India's largest retail stock brokers, it was bootstrapped by its founders, and it states publicly that it does not give stock tips or trade on behalf of clients. The technology team is small, builds in Go and PostgreSQL, self-hosts its systems, and publishes its engineering work in public. A strong answer proves three things: that you use or have studied the products, that you want autonomy with real responsibility, and that you accept that much of the work is routine and heavily regulated.

What the Interviewer Listens For

1. Real product knowledge. Zerodha builds Kite for trading, Console for reporting, Coin for mutual funds, Kite Connect for trading APIs, and Varsity for education. Kite Connect is a set of HTTP APIs with a WebSocket stream for live prices, and a WebSocket is a long lived connection that pushes updates without repeated requests. Naming the product that you actually used proves real research.

2. Interest in the engineering choices. The company runs Go services, very large PostgreSQL databases, and its own infrastructure, and it has written publicly about logging, monitoring, and moving its mobile app to Flutter. Curiosity about one of those choices is stronger evidence than praise for the brand.

3. Comfort with unglamorous work. Interviewers say plainly that a large part of the work is processing files and meeting regulatory requirements, so an answer that describes only exciting problems suggests a mismatch.

4. Fit with a small team. The team is small by choice and hires rarely, and the company has stated that skill alone does not make up for being difficult to work with. Show that you have worked well with few people and little process.

A Three Part Structure

Part 1: The opening (2 to 3 sentences). Name the Zerodha product that you know and say what you noticed about it as an engineer.

Part 2: Your proof (2 to 3 sentences). Describe one system that you built and owned completely, and include a number that shows its size or its reliability.

Part 3: The direction (1 to 2 sentences). Say what you want to work on at Zerodha, in the company's own terms.

Sample Answer

"I have used Kite for years, and I started reading the Zerodha engineering posts after I reached the rate limits while building on Kite Connect. I built a portfolio tracker that consumed the WebSocket feed and stored ticks in PostgreSQL. I owned it end to end, including the reconnection logic and a nightly job that rebuilt positions from the day's ticks. It now serves about 60 users with no manual repair work. That project taught me how strict correctness has to be when the data represents money. Zerodha does that at national scale with a small team and no outside funding pressure. I want to work on the order and reconciliation systems where that correctness matters most."

This answer works because every claim is supported by evidence: the product interest by something the candidate built, the ownership by a number, and the direction by a named system.

Where the Question Appears

Expect the question in the recruiter call first, and expect it again in the final fit conversation in a deeper form that asks for evidence rather than for more enthusiasm. Keep the same core answer both times, because consistency is itself a signal, and add one new detail in the later conversation, such as a point from an engineering post that you read.

Common Mistakes

• Praising the brand only. Cheap pricing and a popular app describe the company to a customer, not to an engineer, so the answer has to name something technical.
• The services to product answer, told badly. Many candidates arrive from an IT services job, so do not frame the move as an escape, and instead name the specific ownership you want and point to work where you already took it.
• Promising only interesting work. Interviewers state that routine data work is a large part of the job, so an answer that ignores this suggests a poor match.
• Asking for a narrow role. A small team expects engineers to cover several areas, including operations and support for what they built.
• No product contact. The products are free to use and the documentation is public, so arriving without having opened either looks unserious.

How to Prepare

• Learn the full path first. Read what the Zerodha interview process is like so that your motivation story matches the real stages.
• Use the same research twice. The product knowledge you gather also serves the Zerodha system design interview, where the same systems return as design questions.
• Know the waiting times. How long it takes to hear back after a Zerodha interview explains when to expect a reply and when to follow up.
• Write the story down. Draft the three parts, then cut every sentence that contains no fact.
• Practice the delivery. Grokking Modern Behavioral Interview teaches evidence-first answers for every company.