Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Revolut

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Revolut | Offerte di lavoro di Revolut | Stipendi di Revolut | Benefit di Revolut
      Colloqui di RevolutColloqui per Java Backend Engineer presso RevolutColloquio di Revolut


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Java Backend Engineer

      28 apr 2021
      Candidato anonimo a colloquio
      Porto, Oporto
      Nessuna offerta
      Esperienza neutra
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Revolut (Porto, Oporto) nel mese di apr 2021

      Colloquio

      The interview process was composed of three interviews: The first one was with a tech recruiter, who asked questions regarding my past experiences and also some technical questions, like algorithms used by database indexes, big O related questions, ACID properties, etc. The second interview was with a software engineer, it was a live coding interview. He arrived 10 min late, blaming his calendar. The coding exercise was a simple problem: design and implement a really simple Load balancer. In that task he was evaluating my coding skills related to writing clean code, following solid principles, and mainly if the code was well covered with unit tests. No fancy or hard algorithm had to be implemented. First he presented me with a problem, then he asked me to extend the solution add some more features to it. The third interview was with two senior engineers, but only one was asking questions. They called it a "Technical Conversation Interview".. Not really... The interview was divided in two parts, a coding part and a Q&A part. In the coding part he gave me a task to develop a method to handle money transfer from one account to another. He basically wanted me to use locks on both account objects. I kind of struggled to understand what he was looking for as an answer: double synchronized blocks (who would implement this in a production code?) The second part was mainly database related questions, query optimization, indexes, concurrency control (optimistic, pessimistic), isolation levels, partitions.. He asked vague questions and expected really in depth answers. There were so many database questions that it seems like those guys really have problems with database in their system.. Also asked me questions about how to scale databases, then moved the subject to streams, event sourcing, CQRS, how to scale, fault tolerance, and other related questions. As result got rejected with the feedback that my answers were too vague, not in depth knowledge, even though he seemed satisfied with my answers during the interview. Also said that I struggled to solve the double coding exercise, probably the double object lock locked me as well.. Be aware of the following: - The interviewers were not even a bit friendly, lacking some basic social skills, not even trying to make me comfortable during the interviews, maybe this is a cultural difference, eastern Europe, so be aware of that. - The interviewer gave me tips in a few moments, and this seemed to have affected my evaluation as well - They ask vague question, but required in depth responses

      Domande di colloquio [1]

      Domanda 1

      How can you identify issues in a database query? How to interpret the query execution plan, how can you tell that it is using indexes or not? What algorithms do database indexes use? In addition to b-tree, what other algorithm is used by db indexes? What is the difference between hash based indexes and b-tree? When to use them? Trade-offs? If even after solving the issues with indexes, how can you improve the performance of the database? How would you solve concurrency issues with database transactions? How to use pessimistic lock? What are the isolation levels? What would be the best isolation level to solve the issue with money transfer coding exercise? What is exactly the isolation level repeatable read, serializable, read committed, and other questions related to the same topic...... How would you create partitions in a database (which approach would you use)? What are the tradeoffs of db partitions (sharding)? If even after sharding, you still have problems with performance, what would you do? Some questions about event sourcing, that I don't recall anymore.. What is CQRS, how to implement it? There were also some questions about availability like, if a write database is down, what would be the impacts if it is down for a long period of time? (Guess what the answer was? Because of locks in their upstream systems….) So, seems like they prefer pessimistic concurrency control and synchronized blocks.
      Rispondi alla domanda
      10

      Altre recensioni di colloqui per Java Backend Engineer presso Revolut

      Colloquio per Java Backend Engineer

      10 feb 2021
      Candidato anonimo a colloquio
      Kraków
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un'altra fonte. Ho sostenuto un colloquio presso Revolut (Kraków) nel mese di feb 2021

      Colloquio

      First I had an intro with an HR person (it was rescheduled as the interviewer didn't join it for the first time) - we spoke about the role and then I was asked a few basic technical questions. The next step was a live coding interview. The interviewer told me that there will be "a few" tasks, but did not specify the amount. He kept rushing me and whenever I paused for a moment to think, he'd hand out the solution. Later on I received feedback saying that I should focus on speed (which in my opinion is not the greatest quality to access in regards of programming). After that I was supposed to have another round, the hr interviewer asked me to book the time in my calendar, but then didn't reach out to cancel and a few days later I got the feedback.

      Domande di colloquio [3]

      Domanda 1

      Complexity of lookup in a hash map
      Rispondi alla domanda

      Domanda 2

      What does ACID stand for?
      Rispondi alla domanda

      Domanda 3

      Write an URL shortener app + tests
      Rispondi alla domanda

      Colloquio per Java Backend Engineer

      21 dic 2020
      Candidato anonimo a colloquio
      Kraków
      Nessuna offerta
      Esperienza positiva
      Colloquio facile

      Candidatura

      Ho sostenuto un colloquio presso Revolut (Kraków) nel mese di dic 2020

      Colloquio

      The interviewer was very nice, but he didn't clarify what exactly was evaluating, so I started codifying fast in order to complete the 3 tasks on time, but the most important for him was to make use of TDD. If I had known that, I had changed my approach.

      Domande di colloquio [1]

      Domanda 1

      Create a short URI taking four random alphanumeric characters.
      Rispondi alla domanda