Stages: HR → 2 Technical → System Design → 3 Team Fit rounds

Technical Rounds: The Reasonable Part

The actual technical interviews were solid and fair. System design was standard for the level. No complaints here – this is how technical interviews should be conducted.

Team Fit: Where Things Got Creative

Round 1: Team A - The Trust Issues Edition

Started normally with behavioral questions, then suddenly turned into an interrogation. The interviewer seemed convinced I was fabricating my experience and began re-asking technical questions from previous rounds ("How exactly do you guarantee exactly-once delivery?"). Apparently, working 3-5 years ago requires forensic-level memory of database status values. The passive-aggressive undertone was palpable.

Round 2: Team B - The Coordinated Rejection

Two weeks later.

Different team, same tribe, but apparently communication flows freely between teams. The interviewer opened with "So you already failed one, but apparently you know how to pass interviews" and wrapped up in 15 minutes. Efficient, I'll give them that.

Round 3: Team C - The Microservices Philosophy Exam

Another week passes.

Completely different tribe this time, yet somehow they also needed their own assessment. Because apparently surviving two team fits from different teams isn't enough data – they needed a third opinion on why I chose microservices architecture. At this point, I was genuinely curious about their decision-making process and wondering if there's a fourth tribe waiting in the wings. The interviewer had been working less than a year at the company.

The "Challenge" Question Backfire

When I asked about their biggest technical challenges last year, the answer was enlightening: "We deployed a bug to production that wasn't caught in staging." Truly groundbreaking stuff. It really makes you wonder what kind of entrepreneurial genius they're expecting to hire for a senior role.

The One-Way Street

The entire process felt like a job application to an exclusive club rather than a mutual evaluation. They expect you to be thrilled by the opportunity while showing minimal interest in what you might bring to the table. These are classic symptoms of a company that believes their paycheck grants them unlimited interview creativity.

Final Thoughts

After a month-long process, they ghost you. No feedback, no closure – just silence. Professional courtesy apparently doesn't scale with valuation.

Advice for future candidates: Prepare your "Why Revolut?" speech, brush up on microservices philosophy, and maybe practice remembering database schemas from your previous jobs. Oh, and bring extra patience – you'll need it.

Why Revolut?

What made you choose us?