The interview process was part of an on-campus recruitment drive and consisted of multiple rounds conducted in a single day.

It began with a shortlisting based on resumes and academic performance, followed by an online coding test. The test included 2–3 coding questions of medium to hard difficulty, primarily based on data structures and algorithms.

After clearing the test, selected candidates went through two rounds of technical interviews.

In one of the rounds, I was asked to debug a given LeetCode problem (Reorder List), where I had to explain my approach and fix logical issues in the code.

The other round involved a system design discussion (basic level) where I was asked to design a simple scalable system (like a file storage or URL shortener). They also asked about OOP concepts, OS basics, and concurrency.

The final round was a brief HR/behavioral round, focused more on my interest in the company, past project work, and communication skills.

They asked this question for debugging: https://leetcode.com/problems/reorder-list/

Also, they inquired about system design, specifically how to design a scalable file storage system. They delved deeper into consistency models, replication strategies, and handling large file uploads.

In the coding round, in addition to the debugging problem, they presented a couple of medium-hard Leetcode-style problems involving trees and concurrency control. One problem focused on implementing a lockable binary tree, and the other involved multi-threaded synchronization, such as the readers-writers problem or ensuring thread-safe access to a shared resource.

The behavioral round included typical questions like "Tell me about a challenge" and "How do you prioritize tasks." The interviewers seemed to emphasize the problem-solving approach, code clarity, and how one considers edge cases.

Overall, the interviewers were professional and helpful, providing hints when necessary. The process felt fair and focused on real-world problem-solving rather than obscure puzzles.