J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Glovo (Barcelone) en avr. 2025
Entretien
Leetcode-style question with a clever twist, incorporating unique constraints and edge cases. The solution includes thorough unit test coverage and insightful discussions on multi-threading, concurrency control, synchronization techniques, potential race conditions, and performance trade-offs in real-world, production-grade scenarios.
Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez Glovo
Had a call with the HR manager, he introduced the company and its plans, asked about my motivation and experience. The conversation was friendly and polite. I received clear answers to all my questions. However, I didn’t feel any particular interest in me as a candidate. One of the questions seemed a bit suspicious, what would I do if a production issue occurred on a Friday evening.
The response from the company came the next day, automatically, from a no-reply address. That made it impossible to ask for immediate feedback or any follow-up questions.
To me, receiving an automatic response from a no-reply sender is somewhat telling about the internal culture.
Questions d'entretien [1]
Question 1
what would I do if a production issue occurred on a Friday evening
J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez Glovo en janv. 2025
Entretien
I had a two-step interview. The first was a casual chat about my background and what I’m looking for. The second was a live coding session with a medium problem, followed by questions on time and space complexity and how a HashMap works under the hood
Questions d'entretien [2]
Question 1
What is the time and space complexity of your solution?
