There was an initial two-question coding screen with LeetCode easy/medium style problems. Then, a phone interview featured a LeetCode medium-level problem. The onsite was a bit different. There were four 45-minute interviews. One of them was a verbatim LeetCode hard problem. The other three were much more system design-focused. For all of them, it was more of a conversation with the interviewer than a "get the correct answer" situation. On the LeetCode hard problem, I definitely did not come up with a complete solution.

The system design questions took one of two forms:

1. The interviewer presented a system diagram and explained there was an issue with it. I then had to explain how I would modify the system to fix the problem. The problem was initially vague, and I had to ask the interviewer for details to pinpoint performance issues.
2. The interviewer tasked me with designing a system. They provided a rough problem, and I had to gather requirements and design a solution. The solution was largely at the "boxes and arrows" level, but for a few key methods, they asked more specific data structure questions and occasionally asked me to write actual code.

After the onsite interviews, it took about a week to hear I made it through the hiring committee, and another week and a half to get an actual offer.

I don't want to go into details because of my NDA, but at least three of the questions (two in the code screen, one on-site) were verbatim LeetCode problems.