Indmoney Interviews

(Applied through referal)

✅ Profile Shortlisted

Total 3 Round

One thing I really liked about the interview process at INDmoney is that they have senior team members take the interviews, regardless of the role — whether it's for an intern, fresher, or mid-level position. In my case, the technical round was conducted by a Senior Manager, which showed that they take hiring seriously and want to assess candidates thoroughly. It also made the conversation more insightful and focused on real-world problem-solving.

Round 1 – Rejected ❌

Type: Technical

Interview was to good and cooperative. Topics Covered: Resume walkthrough Data Structures & Algorithms

DSA question : Rotate matrix 90 degree anticlockwise in the nested manner until k hits.(Not able to tell the proper approach)

DBMS: Query related to joins (Solved)

Round 2 & 3 – --

Overall the experience was good. Also the Hr team is too supportive.❤️

Current: Salesforce LMTS. Tier-1 college. 11+ yrs of exp.

Here is the process. (no coding rounds)

1. HR - 1.25 hr.
2. SD 1 - 1.5 hr
3. SD 2 - 1.5 hr
4. SD 3 - 1.5 hr
5. SD 4 - 1.5 hr
6. PM director call - 1 hr
7. finance round - 1.25 hr
8. CEO round - 2.5 hours (2 SD)

Total: ~12 hours

There were 2 SD questions in each SD round, total - 10 SDs. Every round was elimination for next to be scheduled. The focus was majorly on scaling services with exact partition keys, etc and capacity estimations. I quickly covered functional requirements. The judgement was on tech tradeoffs taken and scoping of problem, completeness of design and communication effeciency

The tech team leadership is really great and so is their CA.

1. HR - tell me how will you brin impact to IND money, latest industry development in trading & Gen AI. Infra automation, ost optimization, value creation concepts. How I wil drive the change. Test of engineering strength estimation required to support their scale for Infra. Where to save costs, etc.
2. with CTO - design a top K hotel predection with 5k hotels depedning on clicks on detail page and their scale for 30 min window(configurable). Solved using redis and 2 leading-lagging kafka consumer groups.
   
   Follow up design question on this.
3. with VP of stocks - 2 sub designs
   a. design IndMoney real time ticker.
   b. Portfolio management - real time & passive user for stocks, passive for MF, etc
   c. Manage orders
   
4. with VP of Stocks - multiple SDs - 1.5 hr
   a. Real time stock trading latency in <500 micro-sec (under a millisecond)
   b. Real time Stock trading & order settlement
   c. Real time leaderboard of stocks as in IndMoney app.
   
   In this round there was a choice b/w Design UPI and real time stock trading of full indMoney app. I chose trading to have an deep & challanging conversation with his expertise.
5. With CTO - 2 SDs
   a. Variant of top K topics on twitter, but with NLP filters, word filters, always high scale topics should not be trndeing and prediction of topics as trending
   b. Design a duplicate JSOn checking for large size JSONs
   
6. With Director PM - Leadership, conflict resolution, hiring, management, etc
   a. How do you manage low/high performers.
   b. What attributes you look when hiring engineers.
   c. How do you break requirements.
   d. How do I plan.
   e. Examples of conflict resolution inside team, cross engineering team, cross function PM, cross levels leaders/directors/VPs.
   f. Strategy of execution.
   g. Drawing boundries.
   h. And some of stress testing too and created a high conflicting and irritating environment to test.
7. With CA
   Learnt about their unit economics. Differen leaders and areas. Understand where cost and revenue lie sin product. Understtod unit economics and user aquisition cost and cost return period - 18 months. Then asked about ideas to creat more profit, i shared NRIs stock trading - high value , less qty more profit. How do i make decisions, prioritizations. Examples from prev work ex how do i include cost in decision making, etc. I also had some queries on value system and appraisal sysyetm driven by this person.
8. with CEO - 2 SDs (not deep)
   a. Portflio management - duplicate question.
   b. Tax calculation & reposting system like zerodha for India & US stocks, MD, etc for ind Money.
   c. time to execute, estimation of engineering strength, evalyated in decision made for traedeoffs for Product, value, cost, time to market.
   d. Then had a long discussion for upcoming work and ideas like Gift city to implement.
   e. Handling stakeholders cross functional, etc.
   

Overall it was a good deep dicsussion with Technical leaders & CA, but i declined due to offer from Meta London.

Overview

This was an off-campus opportunity where a recruiter reached out to me directly via LinkedIn to inquire about my internship experience and availability for a 6-month onsite internship. After expressing my interest, my first round was scheduled for the very next day. There was no Online Assessment.

Round 1: Technical Interview

The first round began with introductions. The interviewer then outlined the flow: my experience, system architecture/Core CS questions, and finally, the DSA part. He was very helpful and polite. I explained my previous internship work and projects in detail. He asked me about the Producer Consumer problem, which I explained, but I struggled to provide the most appropriate real-life analogy.

Next, we discussed system architecture and API flow for an e-commerce order placing system, followed by questions based on REST APIs mentioned in my resume. I wasn't very proficient here, and he helped me understand some concepts.

For DSA, he presented a problem: "Given 'n' people and 'm' transactions between them, where each transaction represents an amount of money one person owes to another, minimize the number of transactions required to settle all debts so no one owes anyone else in the end." I quickly recognized it as a graph problem solvable with a greedy in-out degree approach with certain conditions. We discussed time and space complexities; I proposed an O(m) solution, and he challenged me to reduce it to O(n). After trying a few approaches, I landed on a logic, and he clarified that he wasn't expecting code for all test cases as it was an NP-Hard problem, but asked me to code my approach. I coded it in 10-15 minutes (he gave me 30), and we discussed edge cases, where I, with his help, identified negative weighted cycles. My code worked for all other cases.

He then asked some questions related to an ER-Model for a student report card, where I wasn't fully prepared but tried my best. Finally, there were situation-based questions like, "How would you cope with a fast-paced environment?" and "Which code would you prefer, your own or the 'correct' one, considering scalability?" My response was that my code would solve 90% of the problem, and for the remaining 10%, we would handle specific cases and apply algorithms like Bellman-Ford, checking my exception handling skills. This round, scheduled for 60 minutes, lasted about 90 minutes.

Round 2: Technical Interview with Director of Engineering

The next day, I received a call from the recruiter confirming my selection for the next round. In this round, the Director of Engineering (DOE) immediately moved to DBMS questions:

1. What is Indexing, with detailed complexities (as I mentioned it in my resume)?
2. Where to use Indexing, the logic behind it, and real-world applications.
3. Normalization.
4. Normalizing a given table (I couldn't complete it entirely, but normalized about 90% of the three tables in 3NF).
5. How I optimized API calls in my previous internship.
6. Some basic GET and POST methods.
7. API status codes and their uses, such as 200, 400, 500, 505 (I missed 400).
8. Design APIs for adding two numbers.
9. A variation: if we want to get data from a third party through integration.

For the DSA problem, he asked: "Given a binary tree, calculate the sum of the minimum distances between all pairs of nodes and return the total sum." He noted it was a variation of Sum of Distances in Tree but for a binary tree and with no re-routing allowed. I started with a brute-force BFS, but it was inefficient. My optimized approach used DFS with DP and LCA. I used DFS to calculate and store the depth of each node in a DP array to avoid redundant calculations, and then calculated the Lowest Common Ancestor (LCA) for each pair of nodes for efficient distance computation. Except for the approach, there was no feedback during coding and design questions. He asked how long it would take to code, and I said 15 minutes. He requested a working code within that time, which I delivered, and it passed the test case he provided. This round lasted 65-70 minutes.

Round 3: CTO Round Technical

The recruiter called me for a final technical round with the CTO the following day. I prepared for DBMS and other core concepts based on the recruiter's feedback. The CTO was very cool and humble. He started by asking about my past work and then gave me a MongoDB aggregation-based problem, allowing me to use the internet.

Next, he asked about my comfort with DSA and requested me to prove the time complexity to find the distance between two nodes in a perfectly balanced binary search tree, which I did. Finally, he gave me a variation problem of the spiral matrix and allowed 20 minutes to code and run it for a given test case. While debugging, we discussed competitive programming in depth, which made the atmosphere lighter. My code eventually worked. He also allowed the use of macros and templates for CP and shortcuts. This concluded my third round.

Verdict: Selected

The next day, I received a call from the recruiter confirming my selection.

Overview

I interviewed for the SSE Backend role at INDMoney in Bangalore. My journey included 5 intensive technical rounds, followed by a final HR managerial round, ultimately leading to a successful offer. I have 2.5 years of experience, primarily working with multiple startups.

Round 1 (Virtual): Data Structures & Algorithms and Golang Basics

My first round was with an SSE. He was very friendly and provided a detailed introduction to the product, highlighting its technical potential and scalability. Following this, I was given a LeetCode medium question:

• Populating Next Right Pointers in Each Node.

Round 2 (Virtual): Database Design and Queries

This round was with an Engineering Manager. I was tasked with designing a database schema for an application similar to Splitwise. The discussion covered aspects of user management, groups, expenses, and settlements. I also had to write various read and write queries for different scenarios based on my design.

Round 3 (Virtual): Advanced System Concepts

The third round was highly technical, conducted by the SVP Engineering. This round delved into several advanced system concepts:

• Redis Pipelining: We discussed how it works and its benefits.
• Postgres Master-Slave Data Replication: I was asked about its architecture and implications.
• Kafka Internals: The conversation focused on components like the group coordinator and its role in managing consumer groups.

Round 4 (Virtual): CTO Round - System Design and DSA

In this round with the CTO, we started with an introduction about my previous company, my role, and the projects I worked on. Following that, there was a database design discussion involving analytics-type queries. A key part of this round was a logical design problem on handling deduplication of payloads at scale within a Kafka environment. I also encountered a string-based DSA question, though no specific details were provided.

Round 5 (Virtual): Team Matching & DSA Variation

This round was with another VP Engineering and felt more like a team matching discussion. We had a general introduction and exchanged interests outside of work. Additionally, I was presented with a variation of the Zig-Zag traversal problem for binary trees.

Round 6 (Virtual): HR Managerial Round

The final round was with the HR Manager. The conversation centered on culture fit and other work-related topics, ensuring alignment with the company's values and team dynamics.

I am delighted to share that I received an offer and have since joined INDMoney.