Overall interview complexity: easy.

Karat screening:

• Small coding problem (not DSA).
• Series of questions about DevOps and system design.

There were two rounds. The second round focused on system design, which I handled well. However, during the first round, I felt like I was participating in a contest where participants were assessed on traits unrelated to coding or communication skills. I was interviewed by a Splunk Principal Engineer.

The company is currently in the process of acquisition by Cisco, which might explain the interviewer's unusual behavior and nervous demeanor.

Why do I say this? During the interview, she stated that she was "shaking because of me" and felt "so disrespected" that I was asking her questions about the coding problem I was working on. This is peculiar because, after the interview, I received feedback stating that I "began working on the given problem without asking any clarifying questions."

I had the impression she wanted me to solve the problem in a very specific way. Initially, she claimed the "code cannot compile." I accepted this without pointing out that Python is an interpreted language. Subsequently, she became fixated on the specific libraries and methods I used for handling HTTP requests, despite the fact that at the application layer, the method of solving the problem makes no difference.

I felt something was wrong. I initially thought this was a behavioral question designed to test my stress levels. I am annoyed that during the failed portion, I asked the interviewer whether I should proceed to the next scheduled interview, given how poorly I had performed according to her. She did not instruct me or HR to cancel it, so I ended up spending another five hours of my life on the unnecessary second part, unaware that it was already over after such negative feedback. She was a terrible person, and I am glad I will not be working with her.

Write a script to check the availability of 100 services.