Intern· BengaluruAverageno offer
It was smooth and well structured, which consists of 2 rounds. The first round was the technical round which consisted of some coding questions, and also some aptitude questions. The questions abt the project was also asked
Sample questions
- Swapping Number wihtout 3rd variable
swe summer internship· BengaluruAverageaccept offer
There were 3 rounds, 1st was just basic DSA round, in the second round they grilled me about my projects and went all in into any project of my choice, there were also some basic LLD scenarios, handled them well. Last round just seemed like a formality, it was HR round and everyone who cleared round 2 cleared this as well.
Sample questions
- Round1 : some question related to NSE / NGE (monotonic stack)
Round2 : major data structure used in my project, its advantages over others for that use case
Associate Consultant· MumbaiEasyaccept offer
I got this opportunity in campus round
It was a 3-round interview
1st Round: Resume based Questions + DSA
2nd Round: Project Based Questions
3rd Round: HR round( Q like Location, Further Studies, etc )
Sample questions
- First round, Its all about tech stack you have in your resume. They asked about very basic Questions like 4 pillars of OOPS or New functions or methods in java8.
2nd Round was around projects i have built and they check my depth in the Framework that i used
and lastly 3rd round was simple and HR round
Software Engineer· IndiaDifficultno offer
No information was provided before the technical screen about the interview structure or what would be assessed.
I was told it would be a coding round, but the question required writing code within a large existing Java project rather than solving a standalone programming problem. I was not informed beforehand that familiarity with a specific project structure, framework, and libraries would be required, nor was I given the option to use my preferred programming language.
A significant portion of the interview was spent understanding an unfamiliar codebase, navigating project files, figuring out dependencies, and interpreting framework-specific code instead of demonstrating problem-solving or coding ability. Success depended heavily on prior exposure to that particular ecosystem rather than on universal software engineering skills.
Technical interviews should assess transferable skills such as logical reasoning, coding ability, debugging methodology, and algorithmic thinking. If expertise in a specific language, framework, or project setup is expected, candidates should be informed in advance so they can prepare accordingly.
Sample questions
- * Code Review: Review existing code (“Sort Unique”), identify bugs/issues, and explain improvements.
* Coding: Implement transaction validation in an existing Java Spring banking application (beneficiary validation with the 5-minute rule).
Software Developer 5· IndiaDifficultno offer
Initial phone call from HR explain the process.
Scheduled round 1 with Senior member from US he asked about work i am doing and then a system design question. question is describe below
Sample questions
- Interview-1: System design interview: Design distributed rate limiter. Provide LLD and code for same. How it interacts with backend services. Will API gateway be integrated in DRL or not?
Questions reported by interview candidates on Glassdoor; edited for clarity. Not guaranteed to match your exact interview.