Here's a breakdown of the interview process:

• Email application: Scheduled a phone interview.
• Phone interview: Questions covered relocation, "more about yourself," and the next procedural steps.
• Technical questions: Two coding questions requiring online submission. The platform allowed immediate checking of code functionality via compilers.
• Technical interview (phone and coding): Conducted via phone call, involving both discussion and coding.

Although the interview wasn't particularly difficult, I found it hard to grasp the interviewer's exact meaning. I would provide an answer, and he would repeatedly ask the same question. It felt as though he had a specific answer in mind and was unwilling to consider any others. I attempted to ask him to rephrase the question to better understand what he was looking for, but he simply repeated it. After struggling with the question for some time, he eventually provided the answer himself. I couldn't understand why that was the only acceptable response, why other answers weren't considered, or why he was so fixated on that single question without moving on. It was an unpleasant experience interacting with someone who seemed only interested in hearing a predetermined response. While other interviewers might operate similarly, this was by far the most confusing and frustrating interview I have encountered.

How do you test your (or general) programs?