Autodesk Devops Engineer interview questions

I was approached by the HR team regarding a DevOps Engineer opportunity. Since I was actively exploring new opportunities, I agreed to proceed with the interview process. The interview was scheduled within a few days. The technical discussion was straightforward and covered my current responsibilities, Kubernetes, CI/CD pipelines, and related DevOps concepts. The conversation went well, and the interviewer appeared satisfied with my responses. I was also given positive feedback during the discussion, which led me to expect at least a formal update regarding the outcome. Unfortunately, after the interview, all communication completely stopped. There was no follow-up call, email, rejection, feedback, or status update from the recruitment team. Multiple attempts to understand the status of my application went unanswered. What I found most disappointing was not the rejection itself, but the complete lack of professional courtesy. Candidates invest significant time preparing for interviews, adjusting schedules, and participating in discussions. The least an organization can do is communicate the outcome, regardless of whether the decision is positive or negative. A recruitment process reflects an organization’s professionalism, culture, and respect for candidates. In this case, the absence of any communication after a seemingly positive interview created a very poor impression. Ghosting candidates after interviews demonstrates a lack of respect for their time and effort. Based on my experience, the technical interviewer was professional and knowledgeable, but the recruitment process was poorly managed. The lack of transparency, accountability, and basic communication significantly undermined the overall candidate experience.