I went through three interviews: a coding challenge testing algorithms, a system design session focusing on scalability and trade-offs, and a behavioral interview where I shared experiences about leadership, problem-solving, and working effectively within cross-functional teams.
Preguntas de entrevista [1]
Pregunta 1
In the system design interview, they asked me: "How would you design a scalable real-time chat application that supports millions of users?"
Envié una solicitud electrónica. Acudí a una entrevista en JFrog en may 2026
Entrevista
Very bad experience. Just had one call with the recruiter, the call was constantly disconnecting like a bad signal and couldn't hear the recruiter most of the time. I kept saying I can't hear you and she kept saying "Now better"?
Eventually in the end I said yes better now and she continued. Communication was so bad.
In the end she told me she will check if I'm a good fit and contact me back. As expected she contacted me back with rejection.
Preguntas de entrevista [1]
Pregunta 1
Why did you leave your last previous job?
Salary expectations?
Hybrid 3 days a week is suitable for you?
Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en JFrog (Tel Aviv) en sept 2025
Entrevista
(It was for JFrog Acquire Qwak)
The interviewer created a "gotcha" situation that doesn't reflect real engineering scenarios. Very poor experience.
This kind of confusing setup tests interview skills more than engineering skills, which isn't fair.
Preguntas de entrevista [1]
Pregunta 1
The question provided specific URLs to execute, which created confusion about whether pagination was expected - a small list of URLs and a limited time.
Git API handling rate limiting & pagination.
