Indus Valley Partners(IVP) Interview Experience for Associate Software Engineer(On-Campus)
Interview Experience
There were 4 rounds:Online Test:This round includes three sections:Quantitative Ability: 15 Questions: Purely based on aptitude (calculating the distance between train...
Full Details
There were 4 rounds: Online Test: This round includes three sections: Quantitative Ability: 15 Questions: Purely based on aptitude (calculating the distance between trains, interest, ratio-based problems, profit and loss, etc.) Technical Section: 18 Questions: A code snippet was given based on which correct options were supposed to be selected (correct output or detect an error in code), some basic coding concepts, and some basic concepts of DBMS. Coding Section: 2 questions (1 based on DSA, 1 based on SQL) The coding question was pretty easy. It was based on hashing, or you can use any logic for the same. Question: ( Find unique numbers till the index in the array ) The second question was about SQL queries, It had medium level difficulty if you do not know SQL queries.
Verdict To the
next round
Technical Interview The technical interview lasted for 30 minutes. Introduction, followed by questions about OOPS. (What are the four pillars of OOPS?) What are different SQL commands ( reference )? Why are interfaces used in OOPS? Questions about the final year project. She told me to write a SQL query that was mainly based on joins. I knew the logic behind it. I took help from the internet to verify the query I wrote, as she gave me permission to use the query to check on the database. At the end of this interview, she told me your tech stack is really good as feedback, as I had some good projects to showcase. If you know about your project really well, it is a plus point. 95% of my selection process was done as I knew every small part of my projects, which I mentioned in my resume. If you introduce yourself really well in this round, it will be a short interview.
Verdict To the
next round Director Round: Director asks questions in this round. This round is mainly based on projects. Some of my friends got caught as they were faking about their projects. People say this round includes little grill. But in my case it really went opposite. Director was pretty chill. He just wanted to know about my technical level through projects. But as I mentioned some of my major skills in my introduction for this round as well he got impressed. He did not asked me question related to my project as he liked my projects. But he was interested whether I have some knowledge about financial terms like SIP, mutual funds,etc. as company deals with this on daily basis. If you don not have any knowledge don't try to fake. Fumbling in interview may cause bad impact rather try to redirect it as you have eager to learn about it. After my interview got over I asked few questions which I had doubt about.
Verdict To the
next round
HR round This round is easy to crack if you know which skills you have learned. She asked me to introduce and tell which skills I learned from internships, projects, teams, committees, etc., which basically include soft skills. Your vision to join the company should be reflected in your confidence during the interview. Ask questions to the interviewer every time, as it will let you know where you stand. Don't hesitate to ask questions. You should have knowledge about higher authorities in the company (CEO,CTO, etc.). It is critical to understand the company's goal or what the company actually does (Google about it). If you have financial knowledge, it will bring impact.
Verdict Selected
About This Question
This is a candidate experience report from a indus valley partners interview for a data science role (intern level) during the oa round reported in 2025.
It covers the following topics: Stack, Sql, Arrays, Stack Queue .
Difficulty rating: Easy
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.