I went through the Women’s Day hiring drive, and the whole interview happened on the same day. The process felt really structured—there was very little dead time between rounds, and the recruitment team kept communication clear from start to finish. The panel was professional and supportive, and that made the experience feel less tense than I expected.
Round-to-round, it mostly had the vibe of an efficient check-in and progress through scheduled stages rather than a drawn-out process. I left feeling good about how smoothly everything was handled and honestly appreciated that the workflow seemed designed to be candidate-friendly. I didn’t end up with an offer, but the overall tone stayed positive and I didn’t feel like I was being kept in limbo.
2 months ago
Average Positive Boston, MA
After a recruiter call, the next step landed quickly: I had about a 20-minute phone screen where we discussed my background and then moved into the process. A short time later I went into two longer technical interviews, each around an hour.
In those technical rounds, I worked through a mix of coding and behavioral questions. The interviewers stayed professional and asked thoughtful follow-ups, and when I got close but not fully there, they would nudge with a bit of guidance rather than leaving me completely stuck. What stood out to me was that the questions weren’t just thrown at me—they were explained well, and the conversation felt like it had a logical flow. They also clarified the role and team expectations.
3 months ago
Easy Neutral Budapest
My process started with an HR screen, followed by a team-fit round. Then I moved into a technical discussion focused on frontend architecture and how …
3 months ago
Average Positive Pune
I had a face-to-face interview that was oriented around Java for a PLM-focused role. It covered a broad set of programming fundamentals, including DSA…
4 months ago
Average Positive Pune
After initial shortlisting, I was asked to complete an OA that included aptitude, DSA, code debugging, and an English component. Once that came back, …
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 & Timeline
The interview process is generally structured and can be completed in a single day or spread over multiple days, with clear communication throughout. However, some candidates experienced inconsistencies in the number of rounds and scheduling, which affected their overall experience.
StructuredTimelineScheduling
Technical Rounds
Technical interviews often focus on a mix of coding, data structures, algorithms, and specific technologies relevant to the role, with varying levels of difficulty. Candidates reported a blend of problem-solving questions and discussions about their past projects, emphasizing both theoretical knowledge and practical application.
CodingDSATechnical
Behavioral & HR Rounds
Many candidates encountered HR rounds that assessed cultural fit and communication skills, often following technical evaluations. These rounds typically involved discussions about the candidate's background and motivations for joining the company.
BehavioralHRCultural Fit
Assessment Tools
Some candidates were required to complete online assessments (OAs) that included aptitude tests, coding challenges, and debugging tasks before moving to interviews. This initial filtering step was seen as a way to gauge baseline competencies.
Online AssessmentAptitudeDebugging
Feedback & Communication
Candidates appreciated clear communication regarding their progress and feedback, though some reported frustrations with delays in final decisions or lack of clarity about role availability. Positive experiences often highlighted the constructive nature of feedback during interviews.
FeedbackCommunicationClarity
Interview Difficulty & Expectations
The overall difficulty of interviews varied, with some candidates finding them moderate to difficult, particularly in technical areas. Candidates noted that expectations were often high, especially regarding specific technologies and problem-solving skills.