I had three telephonic interviews: two algorithm and one design. Somehow, my telephonic coding didn't go as well as I'd hoped (even though I felt it went pretty well), so they asked me to give another design round before the actual virtual onsite.

For the onsite, I had one presentation round, one coding round, two system design rounds, and one experience round.

Pros:

1. The recruiter was able to schedule interviews promptly, and in most cases, they were very quick to respond.
2. They called me and provided feedback even when I was not selected. Very few companies do that, and I really appreciate it. This helps candidates improve for future interviews.

Cons:

1. If you are not from a Java background, they force you to take at least one telephonic interview in Java. They had some bad experiences with a candidate who, after being hired, didn't like Java. Hence, they put this condition in place for the telephonic round. I felt this is a really silly condition, as any good engineer can easily pick up a new language. Anyway, I had to brush up on my Java knowledge before the interview.
2. They did not keep me updated about the telephonic rounds and asked for my availability. I thought this was for the virtual onsite, but when I received the calendar invite, I realized they had scheduled another design round. I had to clarify with them before confirming the interview. I felt they could have done a better job of giving me a heads-up.
3. In the presentation round, all the interviewers were present, which I didn't expect. They didn't even introduce themselves and jumped straight into the interview. A better standard for interviews should be set. Also, some of the interviewers were late.
4. The recruiter didn't provide enough heads-up about the interviews and what to expect. When I explicitly asked, they only provided the type of interview and its schedule. Generally, recruiters call and provide very detailed information about what to expect from each interview.
5. Regarding telephonic interviews, I had solved all the problems and didn't think they would give me negative feedback, requiring another round before the virtual onsite. The second interviewer was not listening to me all the time. He was away from his laptop (I figured this out based on his lack of response to my questions and the voice quality, which indicated he wasn't near his laptop). If you're not listening to the candidate all the time, how can you judge properly? This was a really bad user experience.
6. One of the system design interviews focused heavily on database internals. I haven't worked on database internals extensively, so this expectation is also poor. Ideally, they should have identified early on that my profile wasn't a complete match and perhaps I was a better fit for another team or role. Also, the recruiter didn't provide any heads-up about this design interview.

Advice to the management and recruiting team:

1. Your telephonic rounds are quite long (two rounds). People are investing their time and energy, so please show some respect and provide them with a heads-up about each step. Don't sneak in interviews without giving prior notice, as this causes unnecessary confusion and a bad experience.
2. Train your interviewers. Ask them to remain near their laptops when conducting interviews. If they need to attend to something urgent, they can provide a heads-up to the candidate.
3. Design the interviews to test the actual abilities of the candidate and avoid situations/questions that are irrelevant to their work experience.
4. Any good engineer can quickly learn a new language. In a telephonic (algorithm) interview, you won't be able to judge Java skills effectively due to the limited time; your focus should be on the algorithm, not language expertise. If you truly want to assess their Java skills, have a specific interview for that (this is an old-fashioned approach, and engineers would likely dislike it).

I had three coding interviews. They were mainly related to array operations, DFS, and dictionary operations. I noticed that these questions were very much aligned with Facebook coding interviews.

Design questions focused heavily on the internals of database systems and how to design efficient distributed systems.