Summary
I experienced a challenging first-round interview with Hexaware marked by the interviewer's arrogance and unhelpful demeanor. The discussion primarily revolved around Azure service deployment, middlewares, and API security, concluding abruptly after a specific question about app.Map.
Full Experience
I recently had my first-round interview with Hexaware, and it turned out to be quite a peculiar experience. The interviewer approached the session with a noticeable arrogance, implying that his knowledge was the ultimate truth. We started by discussing my approach to moving or deploying a service to Azure, then delved into topics like middlewares and API security.
Throughout our conversation, despite my attempts to provide detailed answers, he frequently interrupted, stating, 'Don't say generic answers.' This made the interaction quite frustrating as I was unsure what kind of specific response he was looking for. Towards the end, he abruptly asked, 'Did I ever use app.Map?' I honestly responded that I wasn't sure and hadn't really paid attention to it. At that point, he simply declared, 'That’s it,' and concluded the interview without further discussion.
Interview Questions (2)
The interviewer asked me about my approach and considerations when moving or deploying a service to Azure. He seemed to be looking for non-generic answers regarding best practices, potential challenges, and architectural decisions in an Azure environment.
The interviewer directly asked if I had ever used app.Map, likely referring to a specific function or concept within a web framework (e.g., ASP.NET Core).