A recruiter contacted me through LinkedIn about some opening positions at Revolut, and we scheduled a call with someone from HR for an initial conversation about the company and me.

My mistake was not checking Glassdoor before the interview. Now I completely understand some of the comments about this step. The conversation was not focused on me and my skills; it primarily consisted of typical questions you can find with a quick Google search.

The feeling I had was that they expected me to answer these questions perfectly, even if I hadn't worked in that specific area. As someone else mentioned, it's better if you are a "living Wikipedia."

I asked the recruiter if she could give me an overview of how many incidents per week/month the company has, because I felt she was placing a lot of importance on how to solve concurrent problems, but she did not provide an answer.

After two days, I received feedback that I was "not what they are looking for." It would be nice to know what that means.

What is CQRS and ACID?

Are you okay with working without a framework?

Have you encountered concurrency problems before? How do you solve a deadlock?

What are the best and average times to access a HashMap? What is the internal implementation of a HashMap?

How many years have you worked in Java?

Brief introductions were exchanged from both my side and the recruiter's side. Suddenly, the recruiter switched to technical questions, such as: What are DDD, CQRS, ACID, SOLID, concurrency, and locking?

He also asked about my experiences and how I ensure code testability.