I applied through a recruiter. I interviewed at Glovo (Barcelona) in Sep 2023
Interview
I was initially contacted by a recruiter through LinkedIn. The process started with an HR screening interview, followed by a technical interview. The technical round involved opening an IDE and solving coding problems while demonstrating live coding and problem-solving skills. The overall process was straightforward and not particularly difficult. Unfortunately, I was rejected due to perceived communication issues during the technical interview. I felt there was a language barrier, as the interviewer’s English proficiency was limited, which made it harder for us to stay aligned during discussions. Despite the outcome, I had a positive impression of the company and would be happy to apply again in the future.
Interview questions [1]
Question 1
Implement a solution to a coding problem in a live IDE while explaining your thought process.
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.
Interview questions [1]
Question 1
what would I do if a production issue occurred on a Friday evening
I applied online. The process took 1 week. I interviewed at Glovo (Barcelona) in Apr 2025
Interview
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.
I applied through a recruiter. The process took 1 week. I interviewed at Glovo in Jan 2025
Interview
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
Interview questions [2]
Question 1
What is the time and space complexity of your solution?
