Clever interview questions

The time constraint on the Hackerrank screen is just not realistic and doesn't reflect what developers even do with real work. I don't understand why companies choose to screen like this. Each question has a 5-22 minute timeout and it is barely enough time to read the prompt and understand it. You have to type every character for your solution, since no copy/paste is allowed. They are not hard problems, but you are expected to come up with them cold, debug them extremely fast with hidden test cases, and not use Google or any other resources. I don't know a single dev who codes like this in the real world. Just another company that relies on a blunt tool to filter.

I had great respect for Clever (and had always heard great things) so I was very excited to land an initial interview. However, the process quickly turned sloppy. my initial call was rescheduled 3 times due to "internal conflicts" and when I finally did speak with someone it wasn't even the talent lead for the role I applied for. To be fair, the person I spoke with was very kind. I was told by them that I answered the questions very well and they would pass along their notes to the team. I then received an email from someone I had never communicated with BUT the email was signed from a different member of the talent team. It was clearly a pre-written email as it said that "they enjoyed meeting me".....however, I had never spoken with the person who sent the email. For as great as a reputation that Clever has, this process was somewhat humiliating, frustrating, and amateur.