Indus Valley Partners Interview Experience | On-Campus Internship 2020
Question Details
IVP visited our campus in September. They had a cutoff of 7.
Round 1 Coding RoundThis round comprised of 2 coding questions, 25 Quantitative Apitude MCQ questions and 15 T...
Full Details
IVP visited our campus in September. They had a cutoff of 7.
Round 1 Coding Round This round comprised of 2 coding questions, 25 Quantitative Apitude MCQ questions and 15 Technical MCQ's. Coding questions: 1.Given a number "A" and some power "N" what is the last digit of A raised to N. Refer:https://www.geeksforgeeks.org/dsa/find-last-digit-of-ab-for-large-numbers/ 2. You are given an array of integers. Find the length of the longest increasing subsequence. Refer:https://www.geeksforgeeks.org/dsa/longest-increasing-subsequence-dp-3/ Technical MCQ's were based on OOPS, Operating Systems and Java.
Round 2 Tech Interview-1 Firstly I was asked to introduce myself. Then I was asked questions based on my CV and projects that I had done. Next, I was asked to define concepts of OOPS like encapsulation, abstraction, modularity, polymorphism etc.. Next was a SQL query involving sum() along with inner join of 2 tables. And at last I was asked about aggregate functions in SQL like sum, avg, count, min and max.
Round 3 Tech Interview-2 + HR Again, this round began with introduction. This round focused on my CV and OS. From OS, he asked about kernel, types of process scheduling and some more general definitions. At last, he asked me what is the difference between Left join and Left outer Join. I instantly said that they are the same. He asked me whether was I sure about it and told me to think again. I got confused by this and ended up saying they were different and added few wrong points to my answer; to which he laughed and said that they really are the same ! So never lose confidence in an interview. The interviewer may try to confuse you but you should be firm with your answer. The HR section included questions like: Why do you want to join us? Would you leave us if you are
hired by a better company? etc.
About This Question
This is a reported interview question from a indus valley partners interview for a quant role (intern level) during the phone screen round reported in 2025.
It covers the following topics: Arrays, Dynamic Programming, Sql, Os .
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.