My process was mostly two live Zoom checkpoints plus a take-home component. I first met over Zoom for about an hour and a half to dig into a personal project in depth. After that, I completed a home assignment centered on recommendation systems, with coding and implementation work in a lit-code style format.
A couple days later, I joined another Zoom session that lasted about two hours where I discussed the assignment. The whole arc felt like they wanted to see not just whether I could code, but whether I could explain my choices and reasoning clearly.
6 months ago
Average Positive Israel
I went through a structured, fairly thorough loop. It started with an HR conversation about the role and what they expected, then I had a short introductory call with the interviewer. After that, I did an in-person on-site segment with the team lead and another team member, where the focus was technical problem-solving and questions that felt geared toward how I think under constraints.
Once the on-site rounds were done, I was assigned a home assignment. When I came back for the final stage, I had another technical discussion with the team lead and a colleague where we went deeper into what I delivered. The earlier interview round included a “project-first” feel for me too: I described a project I’d worked on, and then it moved into hands-on coding/problem-solving. There was also at least one live question that felt oddly disconnected from their business, which threw me off a little because the rest of the process felt targeted.
7 months ago
Average Negative Ramat Gan
The hardest part of my process was the take-home assignment. It involved designing and implementing something Taboola-like, and it took me several day…
10 months ago
Difficult Positive Israel
My experience centered on an AI-focused test. It was essentially a build-style task where I used an IDE and an AI tool as part of completing the work.…
> 1 year
Average Neutral Israel
My process started with a longer working session where I joined for a couple of hours to build something on their computer. After that, we sat togethe…
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 & Stages
The interview process typically includes multiple stages, starting with an HR screening, followed by technical interviews, a home assignment, and often a final review of the assignment. Candidates should expect a structured flow with various checkpoints that build on each other.
HR screeningTechnical interviewsHome assignment
Technical Focus Areas
Candidates should prepare for a strong emphasis on technical problem-solving, particularly around recommendation systems and coding assignments that require clear explanations of their thought processes. Expect to demonstrate both coding skills and the ability to articulate decisions.
The take-home assignments are often extensive and can take several days to complete, focusing on practical implementations relevant to the company's work. Candidates should be prepared for detailed discussions about their submissions in subsequent interviews.
Take-home assignmentImplementationDetailed review
Communication & Feedback
Candidates frequently report inconsistent communication regarding feedback and next steps, with some experiencing long waits without updates. It's advisable to follow up proactively after submissions to ensure clarity and closure.
CommunicationFeedbackFollow-up
Interview Atmosphere
The interview environment is generally described as friendly and professional, with interviewers showing a genuine interest in candidates' backgrounds and projects. However, some candidates noted a disconnect between positive interactions and final outcomes.
Many candidates expressed frustration over unclear or abrupt rejection decisions after significant time investment, indicating a need for better transparency in the evaluation process. Candidates should be prepared for the possibility of not receiving detailed reasons for decisions.