Me postulé a través de un reclutador. Acudí a una entrevista en Revolut en nov 2023
Entrevista
The interviewing process consisted of 3 stages:
- Test on a web platform
- Technical Android interview with an interviewer
- System Design interview, where (surprise-surprise) a *backend* system had to be designed, including covering all backend-specific technologies and approaches. Android technologies weren't in the scope of this interview. The interviewer confirmed this is a usual thing and many people are confused during the actual interview. So there was not mistake.
This last peculiarity wasn't mentioned before the interview.
Preguntas de entrevista [1]
Pregunta 1
The test had several multi-choice questions and one coding challenge. This test had a time constraint.
Technical Android interview had usual and mandatory questions about Android development. Nothing special.
The System Design interview demanded designing a backend for a certain functionality of a mobile app. Yes, given the target position is Android dev, exactly the backend skills were assessed during this session.
Me postulé a través de un reclutador. El proceso tomó 3 semanas. Acudí a una entrevista en Revolut (Passos) en abr 2026
Entrevista
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.
Me postulé a través de un reclutador. Acudí a una entrevista en Revolut (Buenos Aires) en sep 2025
Entrevista
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é.
Preguntas de entrevista [4]
Pregunta 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.
Me postulé en línea. Acudí a una entrevista en Revolut en mar 2025
Entrevista
Unfortunately, I found the interview process outdated and unnecessarily rigid.
The live coding session required me to disable all Copilots and restricted me from performing any Google searches. This lack of flexibility felt unrealistic, as it does not reflect the way modern developers work. Additionally, I was asked to implement a feature using Views/XML, which is considered obsolete by today's standards where Jetpack Compose is the preferred approach for modern Android development.
Furthermore, a significant portion of the interview was focused on theoretical questions about concurrency and synchronization, without paying attention to practical problem-solving or my thought process. Finally, during the last 5 minutes, I was asked to write a test, and they even scrutinized the name I chose for the test—an approach that felt overly meticulous and disconnected from actual development priorities.
Overall, the interview model felt archaic, seemingly designed for a decade-old landscape rather than the current state of Android development. The emphasis on outdated technologies and theoretical questioning, rather than practical problem-solving and creativity, makes me question whether this approach is suited to evaluating modern Android engineers.
Preguntas de entrevista [1]
Pregunta 1
Implement a feature using Views/XML.
Explain various concepts related to concurrency and synchronization.