I started with a proctored, online OA. The questions were mostly multiple-choice, centered on basic engineering design ideas in Python plus cloud and database topics. After that, about a week later, I had a recruiter screen, and then a technical interview chat with no whiteboarding.
The technical discussion leaned toward ML frameworks, and it felt like more of a conversational deep dive than a coding session. The whole process moved quickly after the recruiter stage, and I ended up getting an offer soon afterward. Overall, the experience felt structured and fair, and I could tell they were checking not just whether I knew ML tooling, but whether I could talk through engineering tradeoffs behind it.
3 months ago
Average Neutral India
A recruiter reached out to me and set up interviews about two weeks later. The process started with a DSA round where I was asked two classic data-structures problems: one involving strings and another involving a linked list.
I managed to solve the string question, but I couldn’t get to a working solution for the linked list problem. The interview difficulty felt medium overall, but the miss on the second problem clearly mattered. I didn’t move forward after that, and the rejection felt direct and tied to that gap.
5 months ago
Average Negative Hyderābād
My interview started with a JavaScript-focused round. I was asked to implement a set of tasks using vanilla JavaScript, and a lot of it was practical …
6 months ago
I went through a problem-solving round for an SDE role that was basically two coding problems. The setup felt like a focused session where I had to st…
6 months ago
I got pulled in by a recruiter and the interview was scheduled to happen fast—two rounds were set for the same day, with a total of three rounds in th…
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 Assessment
The interview process typically begins with a recruiter call followed by an online assessment that includes multiple-choice questions on engineering design, Python, and cloud/database topics. Candidates should be prepared for a structured assessment that tests their foundational knowledge.
Recruiter callOnline assessmentEngineering design
Technical Interviews Focused on Data Structures & Algorithms
Candidates can expect multiple technical interviews that focus heavily on data structures and algorithms, often including classic problems like strings and linked lists. It's important to be well-versed in DSA concepts and able to solve problems live during the interview.
DSACoding problemsLive coding
Project and System Design Discussions
Some interviews involve discussions about personal projects and system design, where candidates are expected to articulate their thought processes and technical decisions. This requires a solid understanding of engineering trade-offs and practical applications of their work.
The interview process often includes behavioral and managerial rounds that assess cultural fit and alignment with team values. Candidates should prepare to discuss their experiences and how they relate to the role and team dynamics.
Behavioral questionsCultural fitManagerial round
Interview Structure & Communication
Overall, the interview process is described as organized and structured, with a clear timeline and consistent pacing across rounds. However, some candidates noted issues with communication and follow-up, particularly after interviews, which can lead to frustration.
Structured processCommunicationFollow-up
Interview Difficulty & Outcomes
The difficulty of interviews is generally medium, with candidates reporting a mix of straightforward and challenging questions. While many candidates did not receive offers, the feedback often emphasized a fair evaluation process rather than trick questions.