After a recruiter touchpoint, I went through a multi-round process that felt very QA-oriented but still heavy on fundamentals. Roughly a week later I had an online technical screen that combined a few programming problems with MCQs. The timing pressure stood out: the coding problems felt extremely hard for the time they gave, unless I was really comfortable with competitive-programming style problems. The MCQs mattered a lot, and when I focused there it felt like it helped more than I expected.
Next came hands-on website work. I was given a test website and asked to debug it—basically to examine what wasn’t working and record the issues I found. After that, I had another technical coding round where I was asked to build a small Python-based system idea (more like implementing basic classes / components than a full app), and the prompt emphasized reading the requirements carefully. Then the process shifted into a couple technical interviews that leaned on OS and networking foundations, plus a system-design question that wasn’t really software architecture deep-dive so much as explaining the approach.
> 1 year
Average Negative India
I went through a pretty standard campus-style pipeline that began with an online test and then moved straight into QA-style evaluation. The first round was an online assessment with several sections, including aptitude and core CSE MCQs, and it also included code questions where I had to answer outputs or solve small prompts. The structure gave me a clear sense that they were filtering for fundamentals early.
After that, I did a debugging round where a website was provided and I had to find bugs through testing and note what wasn’t working. That felt like the most “day-to-day QA” part of the process: I wasn’t just answering questions, I was trying to reason about symptoms and what might be wrong. Following the debugging work, I had a set of technical interviews where one round included OS-based questioning, and I also had a more direct system discussion where the expectations were still rooted in QA thinking.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Online Assessment Structure
The interview process begins with a timed online assessment that includes sections on aptitude, pseudo-code, and Python coding questions, all under strict time constraints. Candidates should be prepared for a mix of MCQs and coding problems that test computer science fundamentals and reasoning skills.
Online assessmentPythonComputer fundamentals
Debugging Round
A hands-on debugging round follows the initial assessment, where candidates are tasked with identifying issues on a provided test website. This round emphasizes practical QA skills and the ability to reason through problems, reflecting day-to-day responsibilities in the role.
DebuggingQA skillsPractical assessment
Technical Interviews Focus
Subsequent technical interviews delve into operating systems and networking concepts, with an emphasis on applying knowledge rather than rote memorization. Candidates should expect in-depth discussions that assess their understanding of system behavior and testing principles.
Technical interviewsOSNetworking
Progressive Intensity of Rounds
The interview process is designed to increase in intensity, with each round building on the previous one. Candidates should be ready for a variety of question formats and to demonstrate their problem-solving abilities under pressure.
An HR interview typically concludes the process, allowing candidates to discuss their experiences and fit within the company culture. This step is important for assessing alignment with the company's values and expectations.
HR interviewCultural fitBehavioral questions
Preparation Insights
Candidates noted the importance of focusing on core QA principles and system fundamentals rather than traditional coding puzzles. Familiarity with Python and the ability to articulate testing strategies are crucial for success.