At the beginning, I thought things were moving normally—until communication fell apart. I was asked to confirm my availability for an interview and I responded quickly, followed up, and still got no real response. Instead, the process went quiet after that, and I eventually received a rejection weeks later without actually making it to an interview.
That same kind of disorganization showed up elsewhere in my experience with their scheduling. I had been set up for a phone screen at a specific time on Google Meet, but the recruiter never joined and didn’t reply to my emails afterward. Even where I did move through multiple interview steps with other people and then waited, getting a final disposition required repeated follow-ups, and the process felt long and repetitive before anything was clarified. Across it all, what stayed with me was how the lack of follow-through made the whole search feel disrespectful of my time.
11 months ago
Easy Neutral Austin, TX
After I reached the stage where a phone interview was scheduled, it felt fairly straightforward. The call focused on my past experience and why I was interested in the role, and I also talked through strengths and weaknesses. There was a clear, normal back-and-forth, and I remember having time at the end for my questions.
A later interview step leaned more technical and language-specific. I had a basic phone conversation about my background and prior work first, then moved into a hiring manager interview where the questions stayed centered on C++—from syntax-level details to how to apply data-structure thinking in real scenarios. The overall vibe was a direct, focused deep dive into the language and my background rather than a generic “leetcode-style” prompt set. I didn’t get selected, but the questions were still presented as reasonable given what they wanted.
12 months ago
Average Positive Gurgaon, Haryana
My process started with three technical rounds. The first one was a DSA-focused interview, where the core expectations were algorithmic problem solvin…
> 1 year
Average Positive San Francisco, CA
I went through a multi-step process that mixed managerial conversation with several interview types. I started with an HR reachout, then had a manager…
> 1 year
Average Positive United States
After coordinating through HR, I ended up in a longer sequence of interviews that felt more “managed” than casual. The conversations started by going …
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 & Flow
The interview process typically begins with an HR screen followed by multiple technical rounds, often including coding challenges and discussions about past experiences. However, many candidates reported disorganization and a lack of clear structure, leading to confusion and frustration.
HR screenTechnical roundsDisorganization
Technical Focus Areas
Candidates experienced a range of technical interviews that included algorithmic problem-solving, object-oriented programming, and language-specific questions, particularly in C++, Java, and Python. The emphasis was on practical applications rather than generic coding challenges, though some candidates felt the technical depth was lacking.
Algorithmic problem solvingOOPLanguage-specific
Communication & Follow-Up
Many candidates expressed frustration with poor communication throughout the process, including delays in scheduling, lack of updates, and unresponsive recruiters. This often left candidates feeling in limbo and undervalued.
Poor communicationDelaysUnresponsive recruiters
Behavioral & Cultural Fit
Interviews frequently included behavioral questions aimed at assessing cultural fit, though the focus on this varied significantly across candidates' experiences. Some felt that the behavioral components were overshadowed by technical assessments.
Behavioral questionsCultural fitInterview balance
Interview Difficulty & Atmosphere
The difficulty of interviews varied, with some candidates finding the technical questions manageable while others described the atmosphere as intense or even hostile. This inconsistency contributed to differing perceptions of the overall experience.
Interview difficultyIntense atmosphereHostility
Outcome & Offer Process
Candidates reported a range of outcomes, with many not receiving offers despite positive interactions during interviews. The offer process was often described as opaque, with discrepancies between initial expectations and final offers, leading to disappointment.
Offer processExpectations vs. realityDisappointment