1. Interview with a recruiter: She asked a few easy, but somewhat ridiculous questions. It was one of those situations where a recruiter reads questions from a "Developer Interview Questions" list and can't truly evaluate your answers.

2. Home task: This task could be quite involved if you aim for perfection. However, the result of this phase doesn't truly matter as long as your solution is acceptable.

3. Phone tech interview: The interviewer primarily asked technical questions not directly related to the role. I later found similar questions simply by Googling ("Developer Interview Questions"). He had these questions written on paper and did not ask about my past experience or the technologies I've used.

4. Phone system design interview: At the beginning, the interviewer stated he had questions for me and then presented a system design task. It felt less like a discussion or collaborative system building and more like he was trying to fit my responses to his predetermined questions. The first problem: the task was fairly simple, but the questions were irrelevant. The second problem: the entire task was not relevant to the position I was applying for. What is the point of asking questions that are not relevant to the actual work?

The whole process seemed overly standardized and not truly relevant to the position applied for. During every phase (recruiter, online interview), people were asking questions from a paper, literally reading from it and waiting for an answer that exactly matched theirs. I felt they weren't genuinely interested in past experience or skills, as long as you could answer all the questions from "Developer Interview Questions".

Before a tech phone interview, you don't have a chance to learn about the project, system, or your potential responsibilities, yet you are asked to invest time in a home task.

NDA