Taro Logo

Senior Backend Developer Interview Experience

January 1, 2019
Negative ExperienceNo Offer

Process

I applied through a recruiter. The process took about 10 days.

After a short conversation with the recruiter, she offered me an offline coding task.

The task was to implement a backend REST service with very vague requirements and no use cases. I was given the freedom to implement it using my own vision. The recruiter acted as a proxy between me and those who were checking the assignment.

Since there were no exact requirements, I interpreted them on my own. I created a project on GitHub and documented all assumptions in the supporting document. In my opinion, the code was written in a decent style (I had a fellow developer review it before sending it to Revolut), using SOLID principles, design patterns, and having nearly 90% unit test coverage.

The task was rejected with a short explanation: "No concurrency handled, and we decided not to proceed with this candidate." There was no requirement for concurrency, nor is it an expected business case in my opinion. However, since this was a one-sided communication, I had no chance to respond and explain my design decisions.

Questions

The recruiter asked about motivation only.

No technical interview was conducted, as I was rejected after the coding task.

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Revolut Senior Backend Developer role.

Success Rate

0%
Pass Rate

Revolut's interview process for their Senior Backend Developer roles is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral25%
Negative75%

Candidates reported having very negative feelings for Revolut's Senior Backend Developer interview process.

Revolut Work Experiences