Relatively good salary, good technology, and during the last couple of years, an almost positive atmosphere.
I say almost because I have heard that there were some problems in the past. I have heard bad things have happened in the past.
But it seems nowadays nobody dares to behave improperly towards employees, at least not publicly. It seems that the management has made some changes to itself and other levels a couple of years ago to evolve Revolut into a positive atmosphere. I would say it has kinda worked, and I hope it gets better.
So, in the end, Revolut was a better place than what I had imagined, but still, it needs to improve.
All I say is based on my personal and my team's experience. There are many teams in Revolut; I'm in a proper team. There may be some teams that are not very good (I'm sure a couple exist). In the end, it depends on your luck.
High work pressure; initial onboarding is hard.
You have to try very hard at the onboarding stage to gain company-based knowledge. It gets easier after a couple of months, although nowadays there are much more and better documentations than when I joined.
Keep improving.
Also improve internal domain-based company knowledge trainings.
One task for writing an API for money transfer. Future candidates: Please keep away from such companies that first give you take-home assignments. Rarely will you make it. Simple reason: You never know what kind of code reviewer will be reviewing y
The process took a month and consisted of three steps: * Take-home assignment * A couple of technical interviews This was one of the better interview experiences I have had. Before every stage of the process, clear expectations were set, and co
I applied through another source. The process took 4 weeks. The process has been along these lines, with a recruiter always available to guide me in all the steps: * LinkedIn Reachout * Screening Call * Live Coding Interview * System Design Intervie
One task for writing an API for money transfer. Future candidates: Please keep away from such companies that first give you take-home assignments. Rarely will you make it. Simple reason: You never know what kind of code reviewer will be reviewing y
The process took a month and consisted of three steps: * Take-home assignment * A couple of technical interviews This was one of the better interview experiences I have had. Before every stage of the process, clear expectations were set, and co
I applied through another source. The process took 4 weeks. The process has been along these lines, with a recruiter always available to guide me in all the steps: * LinkedIn Reachout * Screening Call * Live Coding Interview * System Design Intervie