I started the first interview by introducing myself, and then we jumped into resume-based questions. They asked about details from my background, including follow-ups on the programming language and topics I’d listed, and they also included scenario-style questions tied to the projects I’d worked on and my specific role in them.
The DSA portion showed up as well, but it was paired with web-development concepts—enough that it didn’t feel like a generic coding screen. In the discussions, I got the sense they were checking whether I could connect fundamentals back to how I’d actually built things, not just recite answers. The overall vibe from the interviewers felt friendly and collaborative, and the experience stayed grounded in projects rather than being overly theoretical.
2 months ago
Average Positive Hyderābād
My process started with an online aptitude test, and then I moved into technical rounds. The first tech round covered a spread of topics: DSA, SQL queries, and Python questions, and it also pulled in MERN stack. The difficulty felt moderate to hard, mostly because it blended algorithms with full-stack familiarity rather than staying in one lane.
After that, the rest of the loop stayed similar in spirit—more structured technical evaluation across coding and concepts—rather than a pure discussion-based interview. What stood out to me was how broad the coverage was, from algorithmic fundamentals all the way to SQL and the kinds of MERN stack components I’d worked with. I felt prepared for fundamentals, but the breadth still made the rounds harder than I expected, and I didn’t receive an offer.
2 months ago
Average Positive Hyderābād
I had a longer, technical-heavy interview journey that basically ran like three rounds: Tech1, Tech2, and then HR. The technical questions ranged from…
5 months ago
Average Positive India
My interview loop had four rounds: a coding round, two technical rounds, and an HR discussion at the end. I remember it being a pretty thorough mix of…
6 months ago
Average Neutral New York, NY
One round I did felt more like a fundamentals check than a coding interview. I didn’t write code at all; instead, the interviewer fired off rapid, con…
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
Interview Structure & Rounds
The interview process typically consists of multiple rounds, including a phone screen, technical coding sessions, and an HR discussion. Candidates can expect a structured approach with clear communication about the timeline and expectations.
Phone screenTechnical roundsHR discussion
Technical Assessment Focus
Technical interviews cover a broad range of topics, including data structures and algorithms (DSA), SQL, and specific programming languages like Python, C#, and Java. Candidates should be prepared for both theoretical questions and practical coding challenges that integrate web development concepts.
DSASQLWeb development
Behavioral & Fit Interviews
Behavioral interviews are integrated into the process, focusing on past experiences and cultural fit. Candidates should be ready to discuss their background and provide examples using the STAR method to illustrate their problem-solving skills and teamwork.
BehavioralSTARCultural fit
Problem-Solving Emphasis
Interviewers prioritize clear problem-solving and logical reasoning over rote memorization. Candidates may face rapid-fire questions that assess their understanding of core concepts and their ability to articulate their thought process.
Problem-solvingLogical reasoningCore concepts
Feedback & Communication
While the interview experience is generally friendly and professional, candidates often report a lack of meaningful feedback or closure after the process. It's advisable to follow up for feedback but be prepared for generic responses.
FeedbackCommunicationClosure
Difficulty & Expectations
Candidates describe the difficulty of the technical rounds as moderate to hard, with a mix of easy to medium coding problems. Preparation should include a solid understanding of both fundamental concepts and practical applications across the tech stack.