Working for Revolut has been great for me as an engineer and has helped me develop my skills a lot with the help of a great team. We're all focused on delivering wow and making sure our customers are happy all over the world.
The work-life balance is good; nobody asks you how much you've worked or how many breaks you took. The most important thing is to deliver on time with great quality. Estimations are not absurd.
Revolut is a place where you can grow a lot as an individual and engineer, as people are very open to sharing their knowledge.
It starts to feel more like a corporation, with processes and so on, but the documentation is kept up-to-date and in good shape, so it's easy to find everything.
None
I applied through a recruiter. The process took 2 days. It was a screening interview, questions about my background, nothing special. The only problem was that after the interview I did not have any answer from the recruiter, so I did not know what
The interview process consisted of an initial resume screening followed by a standard technical assessment. The technical portion was typical for software engineering roles, focusing mainly on core data structures and algorithmic problem-solving. I
First, an HR interview. Second, an interview with two iOS developers. They asked questions about map, heap, and stack memory. * How are maps represented in memory? * How are hash collisions handled by the system? Then, a live coding problem that r
I applied through a recruiter. The process took 2 days. It was a screening interview, questions about my background, nothing special. The only problem was that after the interview I did not have any answer from the recruiter, so I did not know what
The interview process consisted of an initial resume screening followed by a standard technical assessment. The technical portion was typical for software engineering roles, focusing mainly on core data structures and algorithmic problem-solving. I
First, an HR interview. Second, an interview with two iOS developers. They asked questions about map, heap, and stack memory. * How are maps represented in memory? * How are hash collisions handled by the system? Then, a live coding problem that r