The interview process was very lengthy and involved six interviews with different members of the team, but I came away with very little understanding of what the day-to-day responsibilities of the role actually were. I met with the Hiring Manager, who commented that my background and skill set were impressive. I also interviewed with another Senior IT Engineer, where we discussed topics such as preventing PII from being shared in Slack, MDM migration strategies, evaluating tools during a proof of concept (POC), project coordination, and prioritizing competing initiatives. The discussion was highly technical, and the interviewer mentioned that he was surprised by the depth of my hands-on experience as we explored each topic in detail. The final stage was an executive interview with the VP of Engineering, and unfortunately it was a disappointing experience. At the start of the interview, she stated that she had not read my resume and did not even have it open. The interview was recorded using Ashby's note-taking tool, but it felt as though there was very little effort to learn about my background. She did not address me by my name during the conversation, appeared disengaged, and gave the impression that she wanted to conclude the interview as quickly as possible. It did not feel like a meaningful evaluation of my qualifications. After completing all six interviews, I was informed by the recruiter that they had selected another candidate because they were looking for someone with more in-depth messaging. Given the level of technical discussion throughout the process and the positive feedback I received from earlier interviewers, this explanation was surprising. Based on my experience, the interview process was significantly longer than necessary and lacked consistency across interviewers. While every candidate's experience may differ, I would encourage prospective applicants to carefully consider whether this interview process and culture align with what they are looking for.