Pretty much what others have said here.

1. Chat with recruiter.
2. Coding assessment: This was fairly easy and involved calling an API, processing some data, and calling another API.
3. System Design (1): Great interviewer; they put me at ease and asked leading questions. This gave me confidence in what I was talking about (and even told me I would do well in later rounds).
4. Hiring manager: You get a few behavioral questions and also a chance to ask them (so be prepared with questions).
5. Coding: It was an easy question. I managed to do it quickly, and the interviewer asked lots of follow-ups just to pass the time. I guess the interviewer had less experience and probably thought they needed to fill the one hour scheduled. Nothing is wrong with stopping earlier if you're happy. Anyway, the interviewer was very nice, so I had no problem.
6. System Design (2): The interviewer was different from the one originally mentioned. They also had a difficult time understanding me, and I had to repeat a lot of things. But the real problems were with how they conducted the interview itself. There were no probing questions or discussion. They had a solution in mind that was different from mine. I had to ask a few times if they were happy with the choices/assumptions and got no response other than "let's move on." There were clear problems with this interviewer.

And then, to make it worse, the recruiter ghosted me. I reached out after 10 days, and they said they were dealing with some personal emergency (fair enough) and that they would not be moving forward. They told me a call would be set up when they were back to give me feedback, but they ghosted me again. I'm too embarrassed to ask again; I guess they are not ashamed of not giving any feedback when the candidate has spent 7+ hours just interviewing.

System design interviews:

• Netflix system design (view, search, and keep track of where users left off)
• Weather module that gets weather data from a server every hour

Coding:

• Merge two sorted lists