1. Recruiter call. Asked "why Adyen" and salary expectations. They warned that there would be a Codility test, where the quality of the task is not that important. What's important is to be able to discuss the solution during the code review.

2. Codility test. 120 minutes, 3 tasks: PostgreSQL query (potentially with schema modification), arithmetic challenge (search "Codility test for nails hammer on hold" on the internet), Streams+Lombok challenge, where the description does not match the unit tests.

3. 60 minutes of panel grilling – one author and two reviewers, in other words, Gruppencodeüberprüfung. Yes, it was that harsh. One week later, after the Codility tests and late enough to forget everything, we had a chance to do a "code review". This is a very live example of a stale merge request being reviewed. First, the interviewers introduced themselves, then asked "why Adyen", and then went on to criticize. And there it turned out that I now needed to defend "why my solution is the best possible", which directly contradicts what was said in (1).

Recommendations to the candidate:

• Do your best to save the challenge texts for later. You'll need to review them before the interview. It is required that you remember the definition from the top of your head during the interview; however, you lose access to the challenge 120 minutes after starting working on it.
• Don't pretend you know more than you know. Given that there are two interviewers but only one you, chances are that at least one of them will spot your overstretch.

Why Adyen

What other advantages, aside from syntactic sugar and parallelization options, do Java Streams offer?

How would you store a password in the database?

What is OWASP?

What was your most technically challenging project?