Had an initial screening call with HR. It was very professional and relaxed. We went through my CV and relevant experience for the role.

Next, I completed an online coding exercise with one of the engineers. My initial impression was very positive, but...

When going through the problem description, I had difficulties understanding both the problem and the engineer. He was speaking quite fast and did not focus on formulating the problem clearly. I asked for clarification on my understanding of the problem and the requirements. I even tried to rephrase it to ensure comprehension, but the answer was often more like, "Yeah, what? Just start coding." This was quite the opposite of what one should actually do.

The problem was about designing a data structure for storing incoming signals and querying them. Actually, I had been working on a quite similar problem recently at my current job, so I felt refreshed on data structures and the topic.

It turned out there was no meaningful discussion on the problem. I just needed to code the solution (and "fast," as the interviewer emphasized), and although I managed to (almost) code the solution, "ta-da," good-bye. The global approach, code organization, and clean code did not matter.

Dear Googlers, if you really do not want to interview candidates or potential teammates, and do not care, please arrange your tasks and duties and do not waste either your or the interviewees' time. I do not mind if you are brilliant engineering snowflakes, but please let's just respect each other's time.

Designing a data structure (DS) for storing incoming signals and querying them.