
Cabify Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 36 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Cabify.
Software Engineer
Medium complexity technical test (car-pooling challenge), with ambiguous requirements, at least 4 days to complete it. They give you 2 weeks to do it, but it took them almost 3 weeks to give feedback, which I think is disrespectful, because if you are in other selection processes it can condition you whether to continue or not. If they take more than 1 week to give you feedback, forget them! they are probably interviewing another candidate that suits them more and they don't bother to give you feedback just in case the other one falls through.
- Technical test: car pooling challenge.
- Then an algorithms test (yes, in 2026 they still do that) and system design.
Software Engineer
I was contacted on Linkedin. Had a first call with the recruiter, then a code challenge that was quite long (around 15-20 hours). The gitlab pipeline has to pass, otherwise, they don't even call you back. After that, there were 3 interviews, each an hour long. These included 30 minutes of questions about principles and 30 minutes of technical case studies, like 'How would you build a blog quickly? And if you had to choose technologies, which ones? How would you do it?' or 'How to set up a cache? Potential problems?'. They expect answers that show you share the company's values.
- Can you share an instance where you had to make a choice with incomplete information?
- Have you ever offered support to a coworker, either in their work or personal life?
- Tell me about a time you encountered opposition after making a decision.
Software Engineer
The process was quite long. First, I had to complete a coding challenge that took me several days of full-time work, likely the most extensive one I've ever done. Following that, I had three one-hour interviews back-to-back. This part was engaging as it focused on topics I enjoy discussing. Unfortunately, the process concluded with a standard rejection email offering no feedback. I dedicated significant time to this interview and had hoped for constructive criticism to improve future applications, both within this company and elsewhere. This experience exemplifies how HR and engineering teams can alienate potential hires and negatively impact the company's image.
- Can you share an instance where you made a significant error at work?
- Describe your approach to designing and implementing a cache.
- When have you introduced an innovation at your company that benefited others?
Cabify Software Engineer Interview Questions
Quoted word for word from Cabify interview reports.
“What happens when you type a URL into a browser and press Enter?”
Read reports →“What happens when you type a URL in your browser and hit enter?”
Read reports →“Which data structure would be suitable for optimizing a slow process, such as using a cache?”
Read reports →“How would you go about implementing a cache for a database that is slow?”
Read reports →“Can you describe the journey of a request from the browser through the network?”
Read report →“Could you write a production-ready API using Go? It needs to include features and endpoints based on a vaguely defined PDF document.”
Read report →“What other useful resources can be added to better understand the approach, design, or implementation?”
Read report →“Could you implement an e-commerce checkout system that handles products and various discount types?”
Read report →“What methods did you use to measure the success of that innovation?”
Read report →Formats, difficulty and experience
Across all 36 Cabify interview reports.