Interview Process: • First Technical Round: Conducted by a two-member panel, this session focused on core Java, Spring Boot, and microservices, along with a coding exercise. I successfully cleared this round. • Second Technical Round: This round primarily covered microservice architecture patterns, event-driven design, and cloud security. I cleared this as well. • Managerial Round: This was the most disappointing part of the process. Unlike standard interviews, there was no self-introduction—the discussion jumped straight into my company details, project duration, and job transitions. When I was asked why I wanted to switch jobs, I explained that my spouse and I were planning to relocate to Trivandrum or Kochi for personal and professional reasons, and I was also looking to gain experience in a new domain. However, my response was met with skepticism, as if my motives were being questioned rather than understood. The manager also dismissed the insurance domain as “not challenging” and asked why I would want to transition into it. In my experience, every domain presents its own unique challenges—it all depends on how one approaches and solves problems. Making assumptions about a domain’s complexity without deeper insight felt unprofessional. When discussing long-term career plans, I clearly stated that in the next five years, I see myself moving into an Application Architect role. However, my answer did not seem to align with his expectations. He implied that within five years, a lead should be aiming for a CEO-level position—which, in reality, is neither a common nor a practical trajectory. Growth should be about expertise and leadership, not just a race toward executive titles. Other parts of the discussion included: • Verifying my educational background and scrutinizing my college details. • Asking about the features I had proposed in my company and whether they were implemented. • Requesting me to explain a UML diagram verbally, without allowing me to draw it, making it unnecessarily complex. Toward the end, he stated that only candidates with 15+ years in a single company are considered as “long-term committed,” implying that my career transitions made me a “job switcher.” If this was a firm requirement, why not communicate it before conducting multiple rounds? This lack of transparency wasted time for both sides. Feedback: While the technical rounds were well-structured, the managerial discussion was disappointing. If tenure expectations are rigid and domain shifts are discouraged, these should be clearly stated upfront to ensure alignment early on. An interview should evaluate skills, knowledge, and career growth potential rather than simply focusing on the number of years spent at a company. Advice to Management: • Set clear expectations about tenure, commitment, and career growth before conducting multiple interview rounds. • Recognize that career paths vary, and not every lead is aiming to become a CEO—some focus on technical leadership instead. • Avoid dismissing an entire domain as “not challenging” without understanding its depth. • Foster constructive discussions rather than making candidates feel as though they are being interrogated.