My process began with a recruiter screen, then I had a call with the hiring manager. After that, I went into a case study interview with two people from the Implementation team. The case study took an hour split between a presentation and a Q&A, and it felt relentlessly technical the whole way through.
I presented an end-to-end web drop-in integration plan, and the questions landed on nearly every slide. They challenged my answers and pushed into very specific details that felt like you’d only know them if you’d memorized Adyen documentation. At times I thought I’d given a complete response, but the interviewer kept pressing, which made me wonder if it was meant to simulate a tough client or just test how I reacted under resistance. One interviewer stayed mostly engaged, while the other barely participated.
> 1 year
Difficult Positive United States
I went through a notably structured set of rounds—five in total—starting with a 30-minute HR screening call about my background and “why Adyen.” Then I had a team lead round that was short but direct, where I was asked about a time I worked with APIs and we clarified details about my project. After that, the most crucial step was a technical case-study demo.
The case study involved demonstrating a “web drop in” component while two implementation engineers asked questions throughout the demo. The questions were clearly tied to what I showed them, and I could feel the interview turning subjective depending on how well I communicated the reasoning behind my choices. After the round, I got feedback that I went too technical and lost them mid-way; the gist was that my demo needed to stay at a higher-level overview while keeping deeper technical details ready in case they pushed further.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
