I applied through a recruiter. I interviewed at Revolut in Jun 2026
Interview
Four very challenging stages in all, but you'll be guided. The System Design bit posed quite a challenge because it's a bit open-ended, and interviewers try to get a feel for your approach to solving problems. Also, a rigorous technical interview for the Android stack tailored towards what you'll use on the job.
Interview questions [1]
Question 1
1. Technical interview (Android) XML views, Coroutines/RxKotlin, RecyclerView
2. Implement a design for an ATM task manager
I applied through a recruiter. I interviewed at Revolut (Passos) in Apr 2026
Interview
This was my second application process with Revolut, and this time I made it through.
In my interview process there were 5 main steps:
- Screening call
- Android technical interview
- Mobile system design interview
- One team-fit interview
- Offer call
Before each interview I had a preparation call with the recruiter. It's important to take notes of everything and study on every subject suggested cause they'll be important.
I applied through a recruiter. I interviewed at Revolut (Buenos Aires) in Sept 2025
Interview
En la primera entrevista de screening hablamos todo el tiempo en inglés. Me preguntó sobre relocarme a otro país y sobre mi experiencia en años como desarrollador y como contribuí últimamente, le conté bastante sobre eso pero no pareció serle de mucho interés en comparación con lo que siguió.
Luego pasó a hacerme preguntas técnicas. Cosa que no esperaba de una persona de recursos humanos por lo tanto no me había preparado. Hubo una pregunta final sobre idempotencia que no pude responder y al día siguiente me avisaron que no quedé.
Interview questions [4]
Question 1
Peor tiempo para obtener un valor de un hashmap. Y como funciona.
Esta me la pasó por escrito a través del chat: Can you explain how a mobile app should interact with a backend when performing operations that must be idempotent (e.g., sending a payment or submitting a form)? Please include how idempotency keys are generated, stored, and reused across retries.