Taro Logo

Mid-Senior Software Engineer Interview Experience

August 31, 2026
Neutral ExperienceNo Offer

Process

I applied through an employee referral. The process took 3 weeks.

After application I received an email with information about my recruiter, a calendar to choose a meeting date and time, and a message that if I have any questions to just feel free to ask. I wrote an email to him about some general things. He didn't answer for a week. I wrote a second email - still no reply.

The meeting day had come. On the screen call it was obvious that he didn't look at my CV at all and even didn't know anything about me, as he was asking elementary questions. Then he went into technical questions when he was asking a lot about databases, concurrency, and locking. Questions were relevant and given answers were accepted without the need to go deeper. About the email thing he said that "it was in spam" - yeah, of course an email from namesurname@gmail.com replying to namesurname@revolut.com with no URLs etc. in the body was classified as spam. And even if it was there - as someone in touch with people, so great that you wouldn't even once a week look there.

The next step was the "Build It" live coding. It was just some practical live coding session with a simple interface to implement, however, you have to be really precise in terms of requirements and what EXACTLY is crucial for these given requirements to be satisfied.

  • Don't fall into a trap of going with a known production standard solution as this one may be so much different, while looking really similar.
  • Think about access queries and their relevance.
  • Don't overengineer.
  • Don't create a future-proof solution.
  • Just make this one small scope of implementation do its work the right way.

I actually fell into that trap so I failed this step. After finishing this task there are also questions still about Databases, Concurrency, and Locking, this time in a more practical sense and with production-grade tradeoffs. The person that was interviewing me was helpful, nice, and with a great attitude. 5/5.

I received information about rejection, but without any details nor feedback. I sent an email asking just for some basic feedback - no response. Ghosted.

Questions

What are Database Isolation Levels?

Describe what is Concurrency and what problems can it cause.

Describe what is Race Condition and how to prevent it.

Complexity for typical operations on Data Structures.

Explain every letter in ACID.

What are DB indexes and their tradeoffs.

Locking or Concurrency classes in Java.

Implement given interface fulfilling functional requirements using the right data structures for given API queries.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Revolut Mid-Senior Software Engineer role.

Success Rate

0%
Pass Rate

Revolut's interview process for their Mid-Senior Software Engineer roles is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral100%
Negative0%

Candidates reported having mixed feelings for Revolut's Mid-Senior Software Engineer interview process.

Revolut Work Experiences