I learned a lot from these people. From the technology perspective, the code is high quality and the architecture is clean. It's not exactly the TDD methodology, but every code has a quiet lot of automated tests. (In TDD, you first write code; then you write the feature, but we just implement the feature, and in the same PR, we write the unit/spec and/or integration/e2e tests.)
The CEO/CTO/upper management are very careful on making wise decisions and rational choices that can keep the company financially upward.
Man, a lot of work.
The interview consisted of two phases. In the first phase, I completed two coding tasks in Java. These tasks assessed my TDD skills and general programming proficiency. The second phase focused more on concurrency in Java, involving writing pseudoc
I entered the interview process with the company with clear expectations based on our initial discussions. The structure was outlined as three stages: * Coding * Theoretical * System design I was informed that successful completion of the fir
I applied through a recruiter. The process took 2 weeks. Overall, I found the interview process at Revolut to be very well organized and structured, which I really appreciated. A special thanks to the recruiter I worked with. They were friendly, sup
The interview consisted of two phases. In the first phase, I completed two coding tasks in Java. These tasks assessed my TDD skills and general programming proficiency. The second phase focused more on concurrency in Java, involving writing pseudoc
I entered the interview process with the company with clear expectations based on our initial discussions. The structure was outlined as three stages: * Coding * Theoretical * System design I was informed that successful completion of the fir
I applied through a recruiter. The process took 2 weeks. Overall, I found the interview process at Revolut to be very well organized and structured, which I really appreciated. A special thanks to the recruiter I worked with. They were friendly, sup