Adyen·Software Engineer·Onsite - System Design / Architecture
May 2026
System design round at Adyen for a software engineer role, two big back-to-back design problems with a lot of depth expected on both. The bar felt high and the questions were very production-focused, not the usual whiteboard-y stuff.
- Design a production-ready thread-safe LRU caching service, covering API design, concurrency control, eviction correctness, TTL and size limits, metrics, and observability.
- How would you scale that LRU cache across multiple instances, handling hot keys, replication and failover, backpressure, and data consistency?
- Design a compute-heavy API for finding transfer combinations that needs to handle request spikes, covering stateless vs stateful worker design, per-request memory management, caching and precomputation, request deduplication, rate limiting, timeouts, and idempotency.
- Walk through your capacity estimates and testing plan for the transfer combinations API under spike traffic.
“Started with the basics of a doubly linked list plus hashmap, but they pushed hard on concurrency almost immediately.” The rest of the author's notes on Software Engineer interview at Adyen, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post