I had a quick chat with the recruiter, where we discussed my experience.

They asked me to describe a time I made a mistake.

The second part was a 1.5-hour interview with two engineers. During this interview, they asked me to talk about a project I was working on.

I described it at a high level and also went into specifics. They also asked questions about certain areas of the system.

I believe I did okay in this part, but the feedback was that I didn't explain the low-level details well. This was a bit of a surprise, as they responded positively to my explanations.

In my opinion, it wasn't clear how deep they wanted me to go. Therefore, I would recommend continuously asking whether your explanation is low-level enough or if you should go further.

There was also a Codility test, which was simple enough: remove duplicates from a list of integers while keeping the order.

The engineers were nice and provided hints.

They asked me how I would test the code, about its time/space complexity, and for a way to make it more optimal.

I didn't perform great on this part, but that was mainly on me, as I got stuck, likely due to a lack of practice.

TCP/UDP: Differences and Use Cases

Explain the Java Garbage Collector

What is MapReduce?