First, I had an HR screening, followed by a hiring manager screening. Both were 30-minute interviews scheduled across two different weeks.
After that, I went through two technical interviews with staff software engineers.
The first technical interview was based on a simple real-world use case from the company. What I found surprising is that I had explicitly been advised to prepare data structures and algorithms, including more advanced topics. As a result, I spent a significant amount of time reviewing concepts such as TreeMap, LinkedHashMap, ordering guarantees, and other non-trivial data structure implementations.
In reality, the exercise consisted of using a simple HashMap, completing a straightforward method, and identifying a bug related to ordering. There was a clear mismatch between the preparation guidance and the actual interview content.
The second technical interview was even more disappointing. I was specifically told to prepare for topics such as large-scale ETL processes, high-throughput data systems, Kafka, distributed systems, scalability, and architecture challenges typically expected at a senior or staff engineering level.
Instead, the entire interview consisted of designing a simple data model for a peer-to-peer payments use case. There were no discussions around distributed systems, event-driven architectures, throughput, fault tolerance, consistency, scalability, data pipelines, or any of the topics I had been instructed to prepare for.
What I find most frustrating is not the difficulty of the interview itself, but the complete disconnect between the preparation guidance and the actual evaluation. I invested a considerable amount of time preparing for complex distributed systems topics because that is what I was explicitly told would be assessed. If the interview is ultimately focused on basic domain modeling, then candidates should be informed accordingly.
It is difficult to understand the rationale behind asking candidates to spend hours preparing for ETL systems, Kafka, distributed architectures, and large-scale system design when none of those subjects are evaluated during the interview process.
Writing Code Interview — 60 minutesThe exercise consisted of completing a specific method in an existing program. Some helper methods were already implemented, and the task was to use them to evaluate a set of business rules related to loans and disputes. The domain involved dispute events with different statuses, such as Open, Closed, and Fraud. Based on the list of dispute events associated with a loan, the method had to determine the final loan status. For example:
Fraud, the loan should be considered fraudulent;ArrayList of dispute events, applying the business rules, and returning the final loan status. After that, some tests were failing due to a bug in one of the already implemented helper methods. The issue was that the disputes were being sorted by ID instead of by dateCreated, which affected the final result. Identifying that ordering bug was the second part of the exercise. That was the full scope of the coding interview.System Design Interview — 60 minutesThe system design interview focused on designing a data model for a peer-to-peer payment system, similar to Venmo. The use case was the following: User A wants to pay User B. Both users have an internal debit/account balance within the platform, and both may also have external bank accounts connected to their profiles. Payments involving banks had an expected delay of around two days. The main task was to design the data model needed to support this flow, including the relevant tables and attributes. The discussion then explored how the model would change depending on different payment scenarios, for example:The following metrics were computed from 3 interview experiences for the Affirm Staff Software Engineer role in Spain.
Affirm's interview process for their Staff Software Engineer roles in Spain is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Affirm's Staff Software Engineer interview process in Spain.