I started with a recruiter call that was straightforward and mostly about my background. Not long after, I had an online coding assessment on HackerRank. The platform test ran for about 75–90 minutes and had two medium-style questions, the kind that felt like LeetCode data structures and algorithms rather than anything company-specific.
One of the problems involved string/array style manipulation, while the other leaned into hash map thinking and edge-case handling. In my case the overall difficulty felt more brutal than expected too—one question I hadn’t seen before pushed into a tougher pattern (two-pointer style) and another involved an approximation approach with bit manipulation, which threw me off.
4 months ago
Average Negative Bengaluru
My experience wasn’t very transparent, and the HR communication could’ve been smoother. Even though I applied for a Software Engineer role, the test I was asked to do leaned heavily toward data engineering.
The assessment included one DSA problem and two SQL questions. It felt mismatched to the role I was pursuing, and that uncertainty made the whole stage harder to take confidently as I was working through it.
4 months ago
Difficult Neutral Boston, MA
My process stretched across multiple rounds and felt pretty structured, like other big tech workflows. After an initial screening, I moved into a sequ…
4 months ago
Average Neutral Boston, MA
The timeline confused me from the start because it felt like they kept moving through interviews first and only decided later. I passed an initial scr…
4 months ago
Average Negative Bengaluru
I went through a longer, high-touch interview sequence that took around a month and a half of my time. It started with an online coding test and then …
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
The Loop & Timeline
The interview process typically involves an initial HR screen followed by an online coding assessment, then multiple technical interviews covering coding, system design, and behavioral aspects. Candidates noted confusion and frustration due to rescheduling and lack of clear communication regarding timelines.
Interview structureTimelineCommunication
Technical / Coding Screen
Candidates undergo a coding assessment on HackerRank focusing on data structures and algorithms, often with medium-difficulty problems that can include edge cases and require efficient solutions. The coding rounds are generally perceived as challenging, with some candidates feeling unprepared for the specific types of questions asked.
HackerRankDSACoding problems
System / Application Design
Later rounds include system design interviews that assess candidates' ability to architect scalable solutions and handle application design topics. These discussions often emphasize real-world scenarios and can be more challenging than earlier coding rounds.
System designApplication designArchitecture
Behavioral & Values Fit
The behavioral interviews focus on past experiences and situational responses, typically using the STAR method. Candidates reported that these rounds were generally easier compared to technical assessments, but they still play a crucial role in evaluating cultural fit.
BehavioralSTARCultural fit
Communication & Follow-Up
Many candidates expressed dissatisfaction with the communication throughout the process, citing a lack of updates and closure after interviews. This often left them feeling uncertain about their performance and the outcome of their applications.
CommunicationFeedbackClosure
Difficulty & Outcome
The overall difficulty of the interview process is perceived as high, particularly in technical and design rounds, with many candidates not receiving offers despite feeling they performed well. The experience often leaves candidates feeling drained and frustrated due to the lack of clarity and feedback.