J'ai postulé via un recruteur. J'ai passé un entretien chez JFrog (Toulouse) en déc. 2020
Entretien
I first met my future line manager (also tech lead) on Zoom. He asked me to talk about myself. He then asked me a couple of technical questions about Go and we went deep into details. We talked in french; this interview was quite casual, I enjoyed it.
The second interview was with an engineering manager based in Israel, also on Zoom. The interview was in English. I was told to go through my curriculum; the interviewer now and then asked me to "go deeper" and to try to teach him something he does not know. I could feel he was bored or uninterested with what I was saying; I constantly tried to adjust what I was saying by reading his facial expression but I could feel I wasn't going to make it. Then, after telling me to "drop it" since (and I quote) I was "not answering what was expected", I proposed to open a project I had worked on in my editor; he followed up with "can you explain me how goroutines are implemented". I tried my best to explain and he shut me down once again. He then asked me to describe what is the concept of connection pool. I opened an editor and started writing some pseudo-code but he seemed to be losing patience; he was expecting a specific answer and I couldn't give it the way he wanted.
I wish the second interviewer had been more patient (less elistst?) and help me through the process of finding a solution instead of constantly saying that "I should not focus on the connection pool, it could be anything like an object"; it confused me so much that I ended up saying that I can't do it. His lest word were that "this is a simple problem of consumer-producer, you must have studied this at school, this is an easy problem".
I guess I'm not a 10x engineer (or "superstar" as written on his Linkedin profile). Five minutes after hanging up the solution popped up in my head :-(
Questions d'entretien [1]
Question 1
- How is implemented the generic map in the Go runtime
- What is the average and worst-case complexities (big O notation) for accessing an element in a Go map
- Describe a specific thing you had to implement in one of your projects and go into throughout details
- How do goroutines are implemented
- What is a connection pool, can you draw a diagram on-screen (on a Zoom whiteboard)
- Open an editor and write the pseudo-code of a connection pool
J'ai postulé en ligne. J'ai passé un entretien chez JFrog en mai 2026
Entretien
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.
Questions d'entretien [1]
Question 1
Why did you leave your last previous job?
Salary expectations?
Hybrid 3 days a week is suitable for you?
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.
Questions d'entretien [1]
Question 1
In the system design interview, they asked me: "How would you design a scalable real-time chat application that supports millions of users?"
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez JFrog (Tel Aviv-Yafo) en sept. 2025
Entretien
(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.
Questions d'entretien [1]
Question 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.