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.
7 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 like a typical technical screen where they mix fundamentals across areas, but what stood out was how much more attention the discussion put on Java compared to the rest.
The scope included DSA, Java, Spring Boot, SQL, and system concepts. I remember walking through Java-related ideas while the interviewer also checked my understanding of the supporting pieces—how DSA connects to coding logic, how Spring Boot fits into building services, and where SQL and system concepts show up in real designs. It wasn’t described as overly tricky, but it wasn’t purely coding either; it was more of a rounded technical conversation.
7 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…
9 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, …
9 months ago
Average Negative India
My process for Ciena felt longer and more stressful than the actual technical content, even though the rounds themselves were about DSA and Java/Sprin…
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.