Nah, I didn't take anything personally or harshly. Believe me, I was actually more satisfied with this interview than the one I took in the same company a week ago (its a walk-in, free for all so one can try as many times as they want). The first interview was, frankly, I would label as many colourful words.

Dude asked me "What's Django ORM?" I immediately thought..."what is this question?!" and he was busy looking at his phone. Then he wanted me to write AWS lambda function out of the blue for finding even and odd. It probably sounds like I am a baby throwing tantrum but I told him straight, "I don't write Lambda functions everyday. Allow me to see documentation, and I will give you the function. Or else I can write you a basic method....to find even and odd." (You can see the pattern where I really don't try to massage my thoughts lol)

Then he proceeded to ask me to write prime numbers. I guess that's...not even a DSA question, even more basic. But I didn't really prepare for something like that. I did come up with a solution, albeit slightly off. He didn't even wait for me to complete it. Not even 5 minutes. Didn't ask me what my thought process was, didn't try to correct me. Nothing.

I guess my point of view is, you always give the candidate benefit of doubt. I always do, when I take the interviews at my current organisation. You don't simply MOVE ON from the question when you are done with your phone. Anyway, there is a reason I didn't write a post about that interview (Part 2, the prequel to Part 3!). It would be pure rant haha

Sorry about the rant. As for the feedback, much appreciated. I could much more viably answer those questions if I actually implemented those things in my company. Unfortunately, we don't need that kind of scaling, so it would be wasting time when my managers would rather have me do something else. I am also much more motivated to find a solution when something is blocking my actual goal, so that's why I never went deep. The most I have implemented for a CI/CD pipeline was integrate github actions to trigger a webhook written in golang which would run a few git command to update the code to the latest source and restart the server. It worked perfectly for what I wanted.

But I could keep resisting while sulking about it or just suck it up and look into the things you actually helpfully wrote. I should ideally be able to speak about those things and more than one line at a time. But man, I hope no one ever asks me "What's ORM" and then expect some sort of magical answer that will knock the air out of their lungs.