Real, anonymous reports from people who interviewed for Software Engineer at Adyen, newest first and distilled into what to expect across the loop.
I ended up going through a recruiter-to-offer flow for an Adyen Software Engineer I role in Bangalore. The process culminated in an offer with a first-year CTC around ₹54,00,000, including RSUs. The package was structured with fixed pay of ₹44,50,000 (base plus PF) and RSUs of ₹9,50,000 per year.
I applied for a Software Engineer (Java) role and got pulled in by a recruiter to schedule interviews. The journey I was preparing for had just two named stages: an initial HR conversation and then a leadership round.
The interview process typically includes an initial HR screening, followed by a technical assessment on HackerRank, and then interviews with team members and leadership. The structure can vary, with some candidates experiencing a more straightforward flow while others face unexpected changes or additional rounds.
Candidates report a mix of coding challenges, including algorithmic problems and system design, with expectations for high performance. The assessments often feel strict, with a strong emphasis on correctness and sometimes vague or confusing prompts.
The final stages often include leadership-focused discussions that can feel confrontational or misaligned with earlier evaluations. Candidates express uncertainty about the expectations for leadership qualities and how these are assessed.
Communication throughout the process can be inconsistent, with some candidates experiencing quick responses initially but then facing delays or lack of closure after interviews. Many report feeling ghosted or receiving generic rejection emails without constructive feedback.
Overall candidate experiences vary widely, with some describing the process as friendly and transparent, while others find it stressful and disorganized. The atmosphere during interviews can shift from collaborative to confrontational, impacting candidates' perceptions.
Many candidates express disappointment over the outcomes, often feeling that their efforts were not adequately recognized or that the evaluations were inconsistent. Reflections highlight a desire for clearer expectations and better communication throughout the process.