I started with a face-to-face written test in Bangalore. It felt very structured: 38 multiple-choice questions covering aptitude, Python, Linux, and networking basics, followed by 12 more questions that focused on shell scripting and Python coding. For those coding items, they gave question paper and an answer sheet, and I had to write the code by hand. I had 90 minutes total, which made pacing important.
After I finished the written portion, the rest of my process didn’t end up happening in a way that I could describe beyond that first round. Overall, that test was the main thing that set the tone—practical topics, but with a difficult constraint since everything for the code section was handwritten under time pressure.
6 months ago
Average Positive Bengaluru
The process kicked off after a recruiter outreach, and I ended up doing the first steps on the same week. The scheduling was a little annoying because the timing depended on my interviewer’s timezone, so I had to adjust my availability.
From there, it moved quickly through a series of interviews. There was an aptitude-style screen that mixed aptitude-style questions with some coding-focused MCQs. After that, I went into a technical discussion that lasted about an hour with multiple interviewers. The conversation was grounded in my resume: they asked technical questions tied to what I had worked on, and they also threw in some generic digital design questions.
> 1 year
Average Positive Gurgaon, Haryana
My onsite process in Gurgaon had a very particular flow. It started with a one-hour written test filled with basic aptitude and networking multiple-ch…
> 1 year
Average Positive Bengaluru
My first touchpoint was an online assessment, and it felt pretty manageable. After that, the real interviews came as virtual rounds. The technical por…
> 1 year
Average Positive Bengaluru
My interview started with an offline, on-premises assessment, and it was very C/C++ heavy. The first stage was essentially a written test on C and C++…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Written Assessment
The interview process typically begins with a written assessment that includes multiple-choice questions focused on aptitude, Linux, networking, and programming fundamentals, often requiring handwritten coding responses under time constraints.
AptitudeLinuxHandwritten coding
Technical Interview Rounds
Following the initial assessment, candidates engage in multiple technical interviews that cover a range of topics, including C/C++, networking, and practical coding scenarios, often tied closely to the candidate's resume and past experiences.
C/C++NetworkingResume-based questions
Scenario-Based Questions
Later technical discussions often shift to scenario-based questions that require applied thinking and problem-solving, moving beyond basic definitions to assess real-world reasoning skills.
Scenario-basedApplied thinkingProblem-solving
HR and Managerial Rounds
The interview process typically concludes with HR and managerial discussions, which focus on general fit, previous project experiences, and compensation, often feeling more formal and less technical than earlier rounds.
HR roundManagerial discussionGeneral fit
Interview Flow and Communication
Candidates noted a generally structured flow to the interview process, but some experienced issues with scheduling and communication, leading to frustration and a perception of disorganization in certain cases.
Interview flowSchedulingCommunication issues
Overall Difficulty and Experience
The overall difficulty of the interview process is often described as average, with candidates feeling challenged but not overwhelmed, although experiences varied significantly based on individual interviewers and specific rounds.