Adyen Early Career Java Tooling Engineer interview questions
based on 1 rating - Updated Oct 9, 2022
Difficultinterview difficulty
Very negativeinterview experience
How others got an interview
100%
Applied online
Applied online
Interview search
1 interviews
Adyen interviews FAQs
Candidates applying for Early Career Java Tooling Engineer roles take an average of 21 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Adyen overall takes an average of 27 days.
Common stages of the interview process at Adyen as a Early Career Java Tooling Engineer according to 1 Glassdoor interviews include:
Phone interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 3 weeks. I interviewed at Adyen in Sep 2022
Interview
Applied with referral, had a 30minute chat with 2 engineers to discuss motivations, received an online assessment (HackerRank) which had 1 java and 1 mysql question, then had a 1hr technical interview with 2 engineers to discuss my solution. The technical interview engineers were very unprofessional. After struggling to answer a question, they'd say things like, "I didn't think you would know this, thanks for confirming my suspicions." I think they must have had a bad day and needed to dunk on a student to make them feel better about themselves. They asked random questions and barely discussed my HackerRank solution at all. The job description did not mention databases at all, so I was very surprised to see a MySQL question on the HackerRank. Most job descriptions have some form of DB listed just to be safe. Not including SQL anywhere but asking it on the HackerRank and then focusing on database knowledge in the technical interview caught me off guard.
Interview questions [1]
Question 1
Which 3 parts of the Adyen formula are your favourite? Why do you want to join Adyen? How would you modify your solution to be multithreaded? Which Java data structures are thread-safe? How would you test your query for performance? How does PostgreSQL run a query at the low level?