I went through a recruiter and then did a 1 hr tech interview. One of the recruiters arrived early just as I did, so I tried to engage in a small talk conversation. I got a one worded response so I decided to awkwardly stare at my screen while I waited for the second reviewer. The second reviewer asked about my experience. A couple of the questions he asked twice, because he thought I didn't answer the question while I am pretty confident I did. This communication problem extended to the technical problems. I decided to do the tech problems in a programming language I am more familiar with. I should have just chosen Java, since they were LeetCode easy problems mostly and I think not doing it in Java caused difficulties for the interviewers. All of my solutions time complexity of O(n). I did expect one question to be iterated on so, I made it a bit more complicated than needed so I wouldn't have to refractor my code for later, but he switched to a completely different Leetcode problem (which was my mistake to prematurely optimize). The last problem I ran out of time, but was slowly getting to the right solution. My advice for the company is 1. Only interview people that you intend to hire. Even before joining starting on the technical problems, I felt like I wasn't going to get the job or move on. It felt like the interviewers were going through the motions since the beginning. 2. I sort of felt like choosing a different language than Java hurt my chances (assuming I had some. This caused more problems than I expected it would). Maybe that is fair considering the position was a Java position, but the interview was labeled language agnostic. 3. I think a more generalized interview process would be a better way to attract talent. As an outsider it is hard to determine what team to apply to, and while at the end of the interview I didn't want to work with the team that interviewed me, I was completely open to checking another team out.