Java Software Developer Interview Experience - Amsterdam, Netherlands
Process
I received an offer to be interviewed last year. The first stage was an online test. It consisted of different tasks:
- SQL task
- Java streams
- Algorithmic task
- A task to find mistakes in a block of code and fix them.
This took about 3 hours. I didn’t finish all tasks. I received an email with feedback; the SQL task was done perfectly, but the others were not. So, I didn’t go further.
Questions
SQL task - something about writing a query with a subselect, HAVING, and GROUPING.
Algorithmic task - some logic problem about hammering nails.
Was this helpful?
Interview Statistics
The following metrics were computed from 3 interview experiences for the Adyen Java Software Developer role in Amsterdam, Netherlands.
Success Rate
Adyen's interview process for their Java Software Developer roles in Amsterdam, Netherlands is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Adyen's Java Software Developer interview process in Amsterdam, Netherlands.
Adyen Work Experiences
- 4.0Nice company to work with!Java Software Developer • Current EmployeeAmsterdam, North Holland, NetherlandsSeptember 29, 2023Pros: Nice compensation. Exchange opportunities to other offices in the world to create an impact.Cons: Compulsory office attendance for 3 days. Some toxic teams (I'm lucky that I'm not a part of those teams).
- 5.0Great Pay, Great BalanceJava Software Developer • Current EmployeeAmsterdam, NetherlandsJanuary 12, 2023Pros: God pay, good life-to-work balance.Cons: Not that much, really, to add.
- 5.0Great social companyJava Software Developer • Current EmployeeAmsterdam, NetherlandsJanuary 8, 2023Pros: Many people here are social and friendly; you will see many people having coffees with others in the coffee place. Great work-life balance; there will be very few people left in the office at 5. Great documentation on most things (non-technical stuff too).Cons: - There are some technical "legacy project issues": - Massive monorepo, meaning the IDE sometimes has a hard time keeping up. - Not an issue for me, but not many (if at all) popular frameworks/tools are used. If you want to increase your marketability, you might find this as a con.
