My process started with a quick HR intro, then I went into a technical round focused on Swift and SwiftUI. That section felt more like random questions than a structured problem, and it left me trying to piece together what level of depth they expected.
After that, I hit a behavioral round centered on everyday use-case scenarios—practical situations where I had to talk through how I’d handle the work. Next came a face-to-face coding-style round described as DSA, and that’s where things got weird: I was told it would be DSA, but then the interaction didn’t align with that framing, and I was later informed there was effectively no DSA involved.
6 months ago
Easy Neutral San Diego, CA
I started with a short HR screening call, about 10–15 minutes, and then moved quickly into a more focused interview with a hiring manager and another engineer. The conversation stayed pretty resume-based—there weren’t many behavioral questions, and it felt like they were trying to map my background to the role rather than test specific interpersonal stories.
In the next round, the format shifted slightly into a technical discussion, but it still didn’t feel like a coding contest. I was asked question-and-answer style, with an emphasis on explaining my thinking clearly. One part that stood out was how they leaned on communication: I had to describe technical terms in the chat, and the interviewers wanted confidence and follow-through as they drilled down on my answers.
9 months ago
Average Negative Bengaluru
I had one virtual screening call, and from there the process moved into in-office interviews. I ended up with two face-to-face rounds at the location,…
10 months ago
Average Negative India
I went into the process thinking I’d get a clear roadmap, but that never really happened. The recruiter told me expectations for each round were essen…
11 months ago
Difficult Neutral Singapore
My experience felt distinctly technical, and it started with the kind of questioning that really dug into specific terminology. One of my rounds pulle…
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 typically begins with a recruiter screen followed by a series of technical and behavioral interviews, but candidates report inconsistencies in scheduling and communication, leading to confusion about the timeline and expectations.
Recruiter screenInterview sequenceCommunication
Technical Evaluation
Candidates experience a mix of technical discussions, including coding challenges and design conversations, but the focus often varies, with some interviews emphasizing communication and practical application over traditional algorithmic problem-solving.
Behavioral interviews focus on real-world scenarios and past experiences, assessing how candidates handle collaboration and conflict, which is seen as crucial for long-term fit within the team.
Candidates frequently report a lack of clear communication throughout the process, including delayed feedback and unclear expectations, which can lead to frustration and uncertainty about their standing.
FeedbackCommunication gapsExpectations
Interview Difficulty & Engagement
The overall difficulty of interviews is perceived as above average, with some candidates feeling that interviewers were engaged and interested, while others encountered disorganization and disengagement from interviewers.
Interview difficultyEngagementDisorganization
Outcome & Reflection
While many candidates did not receive offers, they often left with valuable insights about the company's culture and expectations, although some felt burned by the process due to its disorganized nature.