RepostedAdyen logo

Adyen · Phone screen

In process

Adyen Kotlin Backend Engineer Live Coding: 1 Experience

Software engineer · Full-timeMaster's degreeReported Nov 18, 2026
Shared byjanebeingjane

A 2026 Adyen backend Kotlin interview: a recruiter call, then live coding that parses contacts from JSON, searches and prints them, with unit tests.

At a glance

  • Process: a recruiter call → a video live-coding round in Kotlin with two interviewers (report 01)
  • Asked recently: parse a JSON list of contacts, search by name prefix, print in a set format, write JUnit tests (report 01)
  • Difficulty: the candidate rated it average and found no algorithm puzzles
  • Practise first: Search and Format Contacts

Coverage: One experienced engineer with a Master's degree, changing jobs, who applied online for a backend Kotlin role in Chicago after mostly Android work. The report covers a recruiter call and one live-coding round. It gives October to December 2026 as the interview period and went up on November 18, 2026.

What came up

The coding round was practical rather than algorithmic: model the data, parse it safely, search it and test it. The candidate's impression was that the company doesn't seem to ask LeetCode-style algorithm questions.

Topic Reports Last seen
Live coding in Kotlin: parse, search and print contacts 1 of 1 Nov 2026 (report date)
Unit tests for the solution 1 of 1 Nov 2026 (report date)

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Parse contacts from JSON into objects, search by name, print each match in a fixed format, and test it (practice) 1 Nov 2026 (report date)

1 detailed candidate timeline, loops, and screens

01: Experienced backend Kotlin engineer, live coding

Interview period: 2026 Q4 · Report date: November 18, 2026 · Role: Backend engineer (Kotlin) · Degree listed: Master's · Channel: Applied online · Candidate's rating: Neutral experience, average difficulty · Result: Waitlisted

  1. Recruiter call. A short walk through the candidate's work experience.
  2. Live coding. A video round with two interviewers: the lead in Amsterdam and a shadow interviewer in Chicago. The task was a contacts list given as JSON. Parse it into a list of objects, search by name, print the results in a given format, and write JUnit tests. No Android UI was needed; printing to the console was enough.
  3. Modeling the data. Some contacts have no email, so the candidate made email (and the last name) nullable with a default. The JSON parser was set to ignore unknown keys. The candidate notes that this only skips extra fields: it doesn't help with malformed JSON or missing required fields, so they wrapped parsing in a result type and handled the failure explicitly.
  4. Searching. The candidate matched names by prefix with startsWith. FastPrep's practice version is Search and Format Contacts.

Result

The candidate was waitlisted when they posted.

Keep practicing

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.