So, here's the gist of an interview. I recently got scheduled to give an interview for the Senior Golang Engineer position with the primary skill to check in which is Golang. Since I have good experience in golang while developing microservices with Gokit and also with hexagonal architecture patterns. So, coming to the point interviewer first asked some questions compared to slices and arrays and later he just asked to predict the outcome. Well, I thought I would be coding and explaining all things anyway later on I tried to give half a correct and half a bit incorrect solution. The interviewer was not prepared to be honest about this I will come later. Later, he asked some map questions which I again provided correctly and only a small tweaked wrong approach. Anyways, later he asked to implement a coding solution using goroutines and channels to print even and odd numbers where I coded it well, was only just stuck with a signalling issue. I was asking him well what should I do here he had no idea and coming to that I was not able to run my code on my own because their platform didn't allow me to do the same. I ignored that phase and was again on again optimising the solution again. Later, on he asked some general questions related to databases, git, acid transactions, cap theorem, etc. Where I gave the answers to what I knew. I knew I was going to get rejected. On 6th Dec, I received a rejection email. Later, I just started to check to prepare myself for this type of trick question and later I found that the same question he asked from ChatGPT well he didn't put any effort into preparing. Just reverse the roles, I am pretty sure he won't be able to get one answer correctly in that same scenario. Lessons learned from this type of interview -> I am glad that I got rejected well I learnt these kinds of questions an interviewer can ask without preparation or anything.