Indus Valley Partners (IVP) Interview Experience for ASE (On-Campus)
Question Details
I applied for IVP on campus for the role of Associate Software Engineer. The eligible branches are CSE, ECE, IT, ICE, and EE.The selection process has 4 rounds:Online Asse...
Full Details
I applied for IVP on campus for the role of Associate Software Engineer. The eligible branches are CSE, ECE, IT, ICE, and EE. The selection process has 4 rounds: Online Assessment Technical Interview DAD round (with either a Director or Associate Director)
HR round Online Assessment The OA round has 65 questions that are divided into 4 sections: C# (20 questions), JavaScript (15 questions), OOPs (15 questions), and SQL (15 questions). I did not have any prior experience with C#, but the code snippets were similar to C++, so I was able to find the right answers for most of the questions. The remaining sections consisted of standard and a few hard MCQs. Technical Interview(30 min) The technical interview lasted for 30 minutes. The interviewer introduced herself and asked me to introduce myself as well. The first question was why I was interested in a software engineering role even though I was graduating in Instrumentation and Control Engineering. I explained that I was interested in software technologies and had used some softwares in my previous projects. The interviewer then asked me to define 5 or 6 data structures, such as arrays, dynamic arrays, trees, linked lists, stacks, and queues. She asked me to write a code for implementing a linked list and then convert it into a circular linked list. I was also asked to write a code for removing duplicate elements from an array without using any extra space. The interviewer then asked me a few standard OOPs questions. Finally, she asked me a few SQL queries, such as how to find the third highest salary from an employee table. DAD Round The DAD round was with an Associate Director. He started by scanning my resume and then asked me to give a detailed explanation of one of the projects mentioned in my resume. I explained the project in detail, avoiding using too much technical jargon. He then asked me a few questions about OOPs, data structures, databases, and SQL. He also asked me about some of the skills mentioned in my resume, such as React. I told him that I had very little hands-on experience with React. The interviewer then asked me a few questions on association, aggregation, and composition in OOPs. He also asked me to explain a few other OOPs concepts with examples. Next, he asked me to write a code to find two numbers in an array whose sum is equal to a given number. I wrote the code and explained it to him. He then asked me if I knew anything about operating systems. I told him that I had just started preparing for it. The interviewer also asked me a few aptitude questions and a puzzle. The puzzle was to cut a cake into 8 equal pieces using only 3 cuts. I explained the solution to the puzzle. Finally, he asked me a few SQL questions, such as how to find the top 5 customers with the highest order amount.
HR Round The HR round was with a friendly HR manager. She asked me to introduce myself and then asked me a few questions about my previous interviews. She asked me to tell her about my strengths and weaknesses. I told her about my strengths and avoided talking about my weaknesses. She then asked me what I would do if I was offered the same salary by another company in Hyderabad. I told her that I would definitely choose IVP Noida because I thought I would be able to establish myself better there. The HR manager then asked me to tell her about IVP and its CEO. I answered her questions and finally, I was selected for the role.
About This Question
This is a reported interview question from a indus valley partners interview for a swe role (junior level) during the oa round reported in 2023.
It covers the following topics: Arrays, Linked List, Trees, Sql, Os .
Difficulty rating: Hard
Topics
More Indus Valley Partners Interview Questions
About Indus Valley Partners Interview Reports
This question was reported by a candidate who interviewed at Indus Valley Partners. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Indus Valley Partners are the higher-signal extractions to take from this report.
For broader preparation context, the Indus Valley Partners interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Indus Valley Partners reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Indus Valley Partners Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Indus Valley Partners reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.