I applied through a recruiter. The process took 2 weeks.

It started with a reachout from the recruiter. I had a brief conversation for 15 minutes, and then we never talked throughout the process. Everything happened through automated emails and scheduling links. Most engineers I interviewed with were fairly junior and seemed unfriendly with the coding language of my choice, which was one of the most popular languages. One of the interviewers spent 10 minutes trying to understand the output from my code because it was not prettified exactly how it was expected in the question. I had to output a table, and I represented it as a map and printed the map. Spending time on prettifying the output seems like overkill when you have 45 minutes to go through a 4-part problem.

One of the engineers replied to all my discussions with a single "cool". It was impossible to interpret if I was heading in the direction that he was expecting or not. When I said, "I think I can represent this structure as a tree," he said, "cool." When I said, "I think this tree could have a reverse edge, so it's more like a graph," he said, "cool." When I said, "I could simplify this approach by using an xyz data structure," he said, "cool."

I was able to solve the problem, but I just wanted to be done with the interview. The conversation was one-way, and I had already made up my mind not to be there even if I got an offer. That's not how a collaborative discussion works. This is not a place where I would be excited to drive to every morning.

It was not LeetCode-y, but you could map it to a LeetCode question. The coding problems are all very similar to each other. Even though there's no language restriction, there's a pretty decent language bias based on the comfort level of the interviewers with the language of your choice.