I walked into an offline session for a Software Engineer 1A role in Gurugram that lasted from about 12:30 to 5:30. The whole thing centered on my background and how well I could explain the technical choices behind it. I had to walk through my projects in depth, including the design patterns I used and why I used each one—what problem I was trying to solve and how the solution took shape.
A big part of the interview dove into low-level fundamentals: stack and heap behavior, along with pointers and function pointers. I remember spending time clarifying how those concepts fit together, and the interviewer kept steering me back to the mechanics rather than just high-level descriptions. It felt like a test of whether I truly understood what I had implemented, not just that I had heard the terms.
4 months ago
Easy Negative Ottawa, ON
My experience started with a recruiter conversation and then moved into a team interview. The interviews themselves felt straightforward; the technical question didn’t come across as difficult, and the overall vibe was fine.
What threw me off was everything around scheduling and communication. Getting to the interview took far too long, and the contact process was messy—emails weren’t answered normally, my recruiter got changed midstream, and I even had one call land after 5 pm. After the interviews, I still had questions I was encouraged to ask, but I didn’t receive a response.
4 months ago
I interviewed for an SDE-1 (Java Developer) role in Gurgaon, and my first technical round was a blend of DSA plus Java-heavy topics. The format felt l…
4 months ago
Average Positive Ottawa, ON
My interview wasn’t too bad overall. The difficulty landed around the average range, and the questions were mostly basic C and Python, especially arou…
6 months ago
Easy Positive Ottawa, ON
The first thing that stood out was that the technical and behavioral parts were combined into a single interview. Most of it was Python and C basics, …
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
Technical Rounds Focus
Interviews typically include multiple technical rounds with a strong emphasis on low-level programming concepts, particularly around C, C++, Java, and Python, as well as data structures and algorithms (DSA). Candidates should be prepared for detailed discussions on pointers, memory management, and object-oriented programming principles.
CJavaDSA
Behavioral and Values Assessment
Behavioral questions are integrated into the technical interviews, focusing on candidates' past experiences and problem-solving approaches. Expect to discuss your projects and the reasoning behind your technical choices in depth.
BehavioralSTARProject Discussion
Interview Process and Communication
Candidates report mixed experiences with the interview process, including issues with scheduling and communication. Some found the process smooth and efficient, while others experienced delays and lack of follow-through from HR.
SchedulingCommunicationHR Experience
Assessment Format
The interview process may include a mix of online assessments and in-person or virtual interviews, with initial assessments focusing on fundamentals and multiple-choice questions. Expect to demonstrate coding skills through pen-and-paper tests or whiteboard coding.
Online AssessmentPen-and-PaperWhiteboard Coding
Difficulty Level
The overall difficulty of the technical questions tends to be moderate, with a focus on fundamental concepts rather than complex algorithms. Candidates should be ready for both straightforward and slightly challenging questions.
Many candidates describe the interview atmosphere as friendly and supportive, with interviewers encouraging open discussion and providing chances to correct mistakes. However, some report instances of feeling rushed or cut off during responses.