The vibe of my interview experience swung hard depending on the interviewer. One round felt like it was barely engaged with me—the questioning was light, with just a few puzzles and questions, and the overall tone made it feel less like a serious evaluation and more like a confrontational attempt to provoke.
For contrast, I also had a round where the interviewer came across as genuinely good and the session ran smoothly. That one lasted about forty-five minutes and combined DSA with a basic system-design problem tied to server optimization, plus some math that was algorithmic in nature. The discussion felt structured: I worked through the coding/algorithm pieces while the interviewer stayed focused and responsive.
2 months ago
Difficult Positive India
After a recruiter step, the process took me through a long sequence that felt closer to events than interviews. I ended up in multiple rounds—there was a big hackathon-style track early on, with later technical and systems-style evaluation. In the first hackathon stage, I did a live coding problem while a developer explained the prompt and stayed engaged as I tried to solve it. The judging centered on how I wrote code and handled the engineering work while the problem unfolded.
As I progressed, the later discussions pulled in fundamentals like DBMS, computer networks, and operating systems, and I also had to go deeper into technical topics through system-flavored questions. One portion included a server-optimization style angle and covered both algorithmic thinking and systems concepts, and I remember it feeling pretty demanding, with hard technical questions mixed with conceptual ones. I also went through a stage that required changing and extending the same kind of codework from the earlier hackathon portion, essentially continuing the engineering task and addressing new requirements.
2 months ago
Average Positive Bengaluru
The first part of my journey centered on a hackathon discussion rather than a traditional interview. I worked on an engineering-focused task and then …
3 months ago
Average Positive Bengaluru
On campus, my process started with a DSA-focused set of questions—three problems in the first round. It was followed by an MCQ round that covered a wi…
3 months ago
Difficult Positive India
My first step was an online assessment with a fixed set of questions—there were lots of MCQs plus one subjective prompt. I remember receiving a datase…
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 Screening & Online Assessments
The interview process begins with online assessments that include multiple-choice questions (MCQs) covering computer science fundamentals, followed by coding challenges focused on data structures and algorithms (DSA). Candidates should prepare for a mix of theoretical and practical questions, as passing these rounds is crucial to moving forward.
MCQDSAOnline Assessment
Hackathon Rounds
Candidates participate in hackathon-style rounds that require them to solve complex problems, often involving tree structures and multithreading. Expect to demonstrate not only coding skills but also the ability to optimize and explain your solutions under pressure.
HackathonConcurrencyOptimization
Technical Interviews
Following the hackathon, candidates face technical interviews that delve into DSA, system design, and core computer science concepts. The interviews are rigorous, with an emphasis on reasoning, problem-solving, and the ability to articulate thought processes clearly.
Technical InterviewSystem DesignProblem Solving
Evaluation Pressure & Performance Standards
The interview process is structured with high expectations for consistent performance across various rounds, including both coding and theoretical questions. Candidates should be prepared for a demanding pace and the need to maintain composure throughout the evaluations.
Performance PressureConsistencyPace
Interviewer Engagement & Feedback
The experience can vary significantly based on interviewer engagement; some candidates report supportive interactions while others felt the interviews were more performative. Additionally, feedback post-interview can be limited, leaving candidates uncertain about their performance.
The entire interview process can feel lengthy and exhausting, often spanning several weeks or even months with multiple rounds. Candidates should be prepared for a marathon-like experience that tests not only technical skills but also endurance and mental stamina.