I went through a very compressed but structured process that ultimately felt extremely efficient. After an initial recruiter interaction, I arrived at what effectively became six interviews, all condensed into two intense days. The sequence stayed pretty consistent: rounds that blended coding with deeper discussions about system design and architecture, then I spoke with a manager and finished with a fit-style conversation.
What stood out to me was how deliberate the flow was—each step felt clearly connected to the next, and the whole experience was very informative. I’d done solid prep beforehand, and that preparation helped me feel grounded during the technical and architecture conversations. Even though it was a lot to handle in a short window, the pacing and organization made it easier to keep my footing.
> 1 year
Difficult Positive Tel Aviv-Yafo
My process started with a review with HR and then moved into a scheduled discussion with a team leader for what was described as an assignment. The thing that threw me off was that the first assignment didn’t feel aligned with the junior-level description. It resembled more advanced work than what I expected from the role, and the tasks felt comparable to LeetCode-style problems even though the framing suggested something more appropriate for junior candidates.
After that early mismatch in level, I didn’t move forward to an offer. The recruiter and HR parts of the interaction didn’t feel hostile, but the overall experience left me feeling that the role’s expectations weren’t communicated accurately up front.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
