I was given a weekly homework-style coding test where I built a calculator CLI in Java. The assignment itself was straightforward enough to focus on fundamentals, and it set up what came next: after submitting my work, I had an hour-long interview where I presented the solution and talked through how I’d extend it when new logic was added.
The tricky part wasn’t just explaining the code as it existed, but thinking out loud about how I’d organize changes over time—how to keep the structure clean if requirements evolved. That conversation felt like they were testing my ability to make maintainability a first-class concern rather than an afterthought.
3 months ago
Average Neutral India
My first step was an interview with a manager, and that was followed by a work-from-home task. The homework focused on data-driven modeling: I had to generate insights and build a Tableau dashboard, then use a model of my choice to produce predictions related to Headquarters, including hiring and termination outcomes.
Once the home work was done, I went into a discussion stage to walk through what I’d built—how I interpreted the data, what the dashboard communicated, and how I approached the modeling piece. The whole flow felt like they cared about end-to-end thinking, not just model math.
3 months ago
Average Positive Gurgaon, Haryana
My rounds focused less on algorithms and more on the ad-tech domain. The process was structured and the interviewers were professional and supportive,…
5 months ago
Average Positive Israel
I went through a pretty standard multi-stage sequence that started with a recruiter call, then moved to a team lead call. After that, I had a first te…
5 months ago
Average Positive Tel Aviv-Yafo
I went through a process that leaned heavily on a take-home recommendation systems assignment. It started with a Zoom discussion where I talked about …
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
Initial Screening & HR Interaction
The interview process typically begins with a recruiter or HR conversation that sets expectations and provides context about the role, often described as pleasant and organized, but some candidates reported a lack of engagement or preparation from HR.
HRRecruiterExpectations
Take-Home Assignments
Candidates often complete a take-home assignment that varies in complexity and time commitment, with expectations for thoroughness; however, some found the review process for these assignments to be rigid and focused more on correctness than exploratory discussion.
Take-homeAssignmentsCoding
Technical Interviews & Problem-Solving
Technical interviews generally include coding questions and system design discussions, emphasizing problem framing and reasoning over raw coding skills; candidates noted a mix of LeetCode-style questions and domain-specific challenges related to ad-tech.
TechnicalCodingSystem Design
Communication & Feedback
Communication throughout the process varies, with some candidates appreciating regular updates while others experienced long gaps of silence, leading to frustration; feedback after interviews is often minimal or lacking clarity.
CommunicationFeedbackUpdates
Interview Structure & Flow
The overall interview structure is described as multi-stage and cohesive, with a clear flow from initial screening to technical discussions; however, some candidates felt the process was overly lengthy and cumbersome, with repetitive questioning across multiple rounds.
StructureFlowMulti-stage
Candidate Experience & Reflection
Candidates reflected on their experiences with a mix of positive impressions and frustrations, particularly regarding the alignment of interview content with the actual role and the perceived respect from interviewers; many noted the importance of feeling valued throughout the process.