I interviewed on campus, and it felt pretty direct from the start. I sat for about an hour with two interviewers. The first interviewer asked me to solve DSA using LeetCode, and I also had SQL questions to work through. The second interviewer then went deeper—dynamic programming came up, along with how a database connects to the backend, API concepts, and microservices. They even pulled questions from things I had mentioned on my resume, including slightly modified versions of my own coding rounds.
The overall difficulty felt manageable, but the second round covered a lot of ground, which kept me on my toes. One moment that threw me off was the interviewer’s attitude—he seemed distracted and didn’t always give me the attention I needed while I was answering. Even so, I moved through basic DSA topics like merge sort, trees, and graphs, and also covered resume and project-related areas such as React and MERN plus HTTP methods. By the end, I felt like the interview was testing breadth more than tricking me, even though the experience wasn’t always fully smooth.
1 week ago
Average Neutral Pune
My interview started with a technical discussion that was heavy on Java and Spring Boot, along with SQL. It expanded into cloud and tooling topics too—Azure and Terraform showed up—before shifting into scenario-style, project-based questions. I had to walk through my project experience and problem-solving in a way that showed how I thought, not just what I built.
I remember it getting interactive fairly quickly. They had me introduce myself, then went into the details of my project: how it was implemented, the approach I took, and what my individual contribution was. After that, the discussion moved into DSA where I explained a brute-force approach first and then optimized it. The later part broadened into core CS fundamentals like operating systems, OOP, computer networks, and DBMS, and there were a few SQL questions mixed in.
1 week ago
Easy Positive India
My process was pretty straightforward and leaned strongly on fundamentals. I was asked basic object-oriented programming concepts and had to explain c…
1 week ago
Difficult Neutral Dubai
My first round was a technical interview that leaned into web and server-side basics. I was asked about JavaScript fundamentals and Node.js, and then …
1 week ago
Average Negative India
My interview process started through connections from job portals, and the timeline felt messy from the beginning. I had an HR call where the person s…
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 / Coding Screen
Candidates can expect a mix of coding questions primarily focused on data structures and algorithms (DSA), with some interviews incorporating SQL queries and practical coding tasks related to their resume. Common topics include basic algorithms, object-oriented programming, and database operations.
DSASQLObject-Oriented Programming
Project and Resume Discussion
Interviews often include a detailed discussion about candidates' previous projects and experiences, requiring them to articulate their contributions and problem-solving approaches clearly. This aspect emphasizes the importance of being familiar with one's own resume and the technologies listed.
ResumeProject ExperienceTechnical Discussion
Behavioral & Values
Candidates should prepare for behavioral questions that assess their thought processes and decision-making in project scenarios. Interviewers focus on understanding how candidates approach problems and communicate their reasoning.
BehavioralProblem-SolvingCommunication
Interview Atmosphere & Interviewer Conduct
The interview environment can vary, with some candidates experiencing a friendly and supportive atmosphere while others noted distractions or unprofessional behavior from interviewers. This aspect can significantly impact the overall experience.
Candidates have reported mixed experiences regarding the organization and communication of the interview process, with some noting delays, unclear timelines, or lack of follow-up from HR. This can add stress to the overall experience.
Process ManagementHR CommunicationTimeline
Difficulty & Outcome
The overall difficulty of the interviews is generally perceived as manageable, with a focus on foundational knowledge rather than overly complex questions. However, candidates have noted that the outcome does not always reflect their technical readiness.