My process started with a recruiter-style step, and then I moved into rounds that felt very DSA-forward. The first technical round was basically data structures and algorithms—mostly easy to medium questions. I then reached a more thorough technical grilling in a later round that felt tightly grounded in what was written on my resume.
At the deeper end, I experienced multiple technical interviews where the format stayed consistent: first aptitude plus coding, then more normal data structures and algorithms, and later a backend-heavy discussion with focus on things like Java and a Spring/backend angle. There was also an HR round after the technical parts, and overall it came across as difficult enough to require solid recall rather than just high-level knowledge. I didn’t end up with an offer, but the interviews still had a clear structure and expectations.
> 1 year
Average Positive Rehovot
I went through an initial recruiter touchpoint, and then the process moved into a sequence of technical conversations. I had two technical interviews, and the second one leaned into system design. After that, I met with HR and eventually got a recommendation stage involving managers. Overall the difficulty felt average, but the experience was tense enough that it didn’t feel smooth or celebratory; it was more like being put through the expected mold.
What stuck with me was how narrow the focus was compared to how I’d expected the process to evaluate real software work. During the panel there was a senior interviewer who mostly stayed quiet, while another interviewer drove the questions. The questions were very technical and largely centered on areas like DSA and system design, with the junior interviewer actively looking up what to ask as they went. I remember leaving with the feeling that the process didn’t fully measure hands-on ability, even though I did understand what they were trying to test.
> 1 year
Average Positive Chicago, IL
My first step was pretty standard: I talked with a recruiter, and then I did a take-home assignment that took about one to two hours. After submitting…
> 1 year
Difficult Neutral Israel
My experience started off feeling uncomfortable right away—there was an awkward introduction and even basic audio issues that made it hard to follow. …
> 1 year
Average Neutral United States
I came in through a staffing channel, which shaped the early tone of the experience. First, there was a recruiter conversation where I walked through …
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 starts with a recruiter call, followed by a series of technical interviews that may include coding challenges, system design discussions, and HR rounds. Candidates reported varying timelines, with some experiencing quick turnarounds while others faced prolonged waits without feedback.
Recruiter callTechnical interviewsHR round
Technical Focus Areas
Candidates encountered a strong emphasis on data structures and algorithms (DSA), with interviews often featuring coding problems that required solid recall and practical application of concepts, particularly in Java and backend technologies. System design questions were also common in later stages.
Data structuresAlgorithmsSystem design
Coding Assessments
The interview process often included coding assessments, which could be live coding sessions or take-home assignments. Candidates noted that take-home assignments were sometimes more time-consuming than expected, and the coding tests often featured multiple-choice questions covering various programming topics.
Live codingTake-home assignmentMultiple choice
Behavioral & Communication Rounds
Behavioral interviews were a part of the process, with some candidates required to record video responses to prompts or complete written communication tasks. The focus was on assessing interpersonal skills and cultural fit, though some candidates found the format challenging due to time constraints.
Candidates reported mixed experiences regarding the overall tone of interviews, with some finding the process respectful and organized, while others felt it was tense and lacking in engagement. A common concern was the lack of feedback after interviews, leaving candidates uncertain about their performance.
Candidate experienceFeedbackEngagement
Outcome & Closure
The outcome of interviews varied, with some candidates receiving offers quickly while others faced abrupt endings with little explanation. Many expressed a desire for clearer communication and closure regarding their candidacy status after completing the interview process.