The interview process consisted of:

• A recruiter screen
• One coding screen (DS/algorithms style)
• One system design screen
• A panel interview

There would have been one more interview with the hiring manager, but I only reached the panel interview stage.

This was one of the least well-organized recruiting processes I've experienced with a large tech company. The interviews were rescheduled several times. I was asked to interview after 5 PM to speak with a team in China, despite this being a US job. The interviewers had only been at the company for a few months (around three). During the panel interview, they didn't seem prepared with questions or a defined process. After one of the technical rounds, the recruiter called me to ask about the questions I'd been asked, almost as if she was trying to prep a different candidate.

After my final interview, I didn't hear back from the recruiter. I emailed to follow up a week later and was rejected.

Overall, the technical interviews were "painfully easy," akin to LeetCode Easy or below. I finished one of them 30 minutes early, and the interviewer had no follow-up questions. This was not the final interview; it was one I definitely passed.

The panel interview was strange. The interviewers didn't seem very prepared, and most of the questions were machine learning trivia – things that could be easily Googled and memorized, which, in my opinion, doesn't demonstrate a strong understanding of DS/ML. It was also challenging due to time zone differences and a language barrier.

There were many red flags due to the chaotic interview process, to be honest. It might be that they are hiring rapidly and their recruiters are overwhelmed, but either way, it left a bad taste in my mouth.

Design a spam detection system.