The first stage was a phone screen with one of their engineers. The problem wasn't really a LeetCode-type problem and was more about getting working code. After I passed that, I made it to the onsite stage.

The onsite consisted of a behavioral interview, a system design interview, and two coding interviews. The two coding interviews were again not really LeetCode-type problems, and they required you to bring your own laptop to do the work. They wouldn't let you bring your work laptop, so I had to bring my personal laptop. Unfortunately, I didn't practice coding on it beforehand, so I was not used to various shortcuts, which slowed me down.

The first coding problem, to create a hashmap, wasn't too difficult. However, the one to fix a bug in an open-source library was a bit trickier. I assumed I could just scan through the code to find the failing line, then fix it. But due to the code style being so different from what I was used to, it was quite hard to follow what was happening. In hindsight, I would have started by putting print lines to try and understand the code first before trying to identify the code changes to make.

Create a hashmap data structure that takes a timestamp as a parameter, allowing you to have versioned key-values.

Design a system for storing many payment transactions.

Implement a bug fix for the Jackson Java library, given a unit test that demonstrates the failing change.