Software Engineer applicants have rated the interview process at Revolut with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 39% positive. To compare, the company-average is 35.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 17 days to get hired, when considering 84 user submitted interviews for this role. To compare, the hiring process at Revolut overall takes an average of 23 days.
Common stages of the interview process at Revolut as a Software Engineer according to 84 Glassdoor interviews include:
Skills test: 27%
One on one interview: 26%
Phone interview: 24%
Background check: 12%
Presentation: 4%
Drug test: 3%
Personality test: 2%
Group panel interview: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 3 weeks. I interviewed at Revolut
Interview
Interview process had 4 stages. Fist is coding question that you build upon, second is technical discussion about DBs & Concurency, third was system design and fourth round is team matching. Cleared all the rounds but somehow didn't received an offer. They just kept giving me different teams for matching.
Interview questions [1]
Question 1
Implement URI shortener, be aware of possible parallel access.
Passed first two stages - HR and Live coding. Process is smooth and clear. Hr is responsive, every stage is well structured. Feedback is given on request. Still in the process, will update once done.
Interview questions [1]
Question 1
A lot about multithreading and problems around it.
I passed the hr interview , it includes concurency, db, CQRS patterns, locking mechanisims, and some java related questions
- Introductions to Revolut, our Java teams and why we're hiring
- Some basic HR questions
- Discussion of your background and experience
- 1 or 2 technical scenario questions (usually around concurrency & isolation, sharding & indexes, or testing)
1. Selección por parte del reclutador: entrevista de selección inicial centrada en temas generales como ACID, CQRS, microservicios y conceptos básicos de la nube. La conversación fue directa, amistosa y distendida.
2. Programación en directo + Preguntas teóricas: esta entrevista combinó un ejercicio de programación en directo (implementación de una transferencia de dinero entre dos cuentas) con un debate en profundidad sobre temas de ingeniería de backend, entre los que se incluían los patrones de diseño, la indexación de bases de datos, las estrategias de implementación, las transacciones distribuidas, la observabilidad y los principios de diseño de sistemas.
Interview questions [1]
Question 1
Conceptos básicos como ACID, CQRS, fundamentos de bases de datos y escalabilidad de Kafka.