Adyen Software Engineer candidates typically report a recruiter call, a HackerRank assessment, a technical review of their submission, and later team or leadership conversations, with concurrency and payments design recurring.
$113K
Avg. Base Comp
$131K
Avg. Total Comp
4-5 rounds
Typical Rounds
4-9 weeks
Process Length
Most Adyen Software Engineer candidates describe a recruiter conversation followed by a HackerRank assessment that is then discussed live with engineers. Several reports say the follow-up matters as much as the code: you may be asked why you chose an algorithm, how efficient it is, and what alternative data structures could improve it.
Concurrency is the most repeated technical theme. One candidate was asked to build a payment method with a rolling ten-second card-use count and then explain Java's synchronized keyword and thread-safe collections. Another reported a rate-limiting question with a concurrency focus, and a third was rejected mainly for thin concurrency and multithreading discussion in system design. Assessment content varies by report: SQL, object-oriented Java, data structures, and a longer five-question format were each described.
Payments context also appears in design rounds. Candidates mention designing a payment gateway for an e-commerce customer and a payment service provider, and one suggests learning how payment flows work first. Behavioral questions cover motivation for Adyen, ownership, stakeholder management, and conflict. Several people mention the Adyen Formula, so read it and decide which part fits you.
Reported outcomes are mixed, mostly rejections with a few offers. Reported timelines run from about a month to about two months, with gaps between stages. Feedback is often limited, so prepare to explain your decisions directly and concisely. Reports on the later stages are thinner, so treat stage order as typical rather than fixed.
Synthesized from 37 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Adyen process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Adyen
In which case would you use a bagging algorithm versus a boosting algorithm
| Question | |
|---|---|
| Swipe Payment API | |
| Text Editor With OOP | |
| Dot Product | |
| Why Do You Want to Work With Us | |
| Decreasing Tech Debt | |
| Accessible Data | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Employee Salaries | |
| Closest SAT Scores | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Subscription Overlap | |
| Payments Received | |
| Top 3 Users | |
| Total Spent on Products | |
| Merge Sorted Lists | |
| Size of Joins | |
| Last Transaction | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| String Shift | |
| Google Maps Improvement | |
| Largest Salary by Department | |
| Find the Missing Number | |
| Scrambled Tickets | |
| Comments Histogram | |
| Get Top N Frequent Words |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an introductory call covering background, why Adyen, and salary expectations. One candidate who withdrew described a half-hour version with ownership and stakeholder questions, while another felt the screen was scripted and was eliminated there. It may be evaluative, so prepare concise, direct answers.
Candidates describe assessments with SQL, a data-structures or algorithm problem, object-oriented Java, and concurrency or rate-limiting tasks. Reports range from two to five questions and from one to three hours. One described a payments-themed task. Expect the format to differ, and practice explaining every choice you make.
Candidates report that engineers walk through the submitted solution, asking about complexity, edge cases, alternative data structures, and concurrent access, including synchronized and thread-safe collections. Sessions reportedly ran about an hour or more, and some drifted into behavioral questions. Be ready to defend and improve your code live.
Some candidates report system design on payments, such as a payment gateway for e-commerce or a payment service provider. Behavioral questions around deadlines and team independence were reportedly mixed in. One rejection cited weak concurrency discussion in design, so prepare scaling and concurrency tradeoffs.
Candidates report team-lead, hiring-manager, leadership, or SVP conversations that may include a case study or in-depth project walkthrough. Topics included conflict with a manager, on-call and deployment practice, and one challenging project examined in depth. Outcomes were mixed, with both offers and rejections reported.
