Overall, this was a confusing and disappointing interview experience. It was my first time interviewing with Microsoft, and unfortunately it didn't meet the expectations I had for the candidate experience.
I applied for an administrative role supporting the CVP of Global Channel Sales. After applying, I received an email from a contract recruiter who introduced me to the lead admin for the organization, mentioning that they believed I would be a strong fit. The lead admin and I scheduled an introductory conversation.
The initial conversation with the lead admin went well. At the end of our discussion, I asked whether he or the recruiter would be the best person to answer questions about compensation, the role's location, and whether relocation assistance was available. He advised me to speak with the recruiter.
A few days later, I received three interview invitations without anyone first checking my availability. Before committing to several interviews, I wanted to confirm that Microsoft and I were generally aligned on compensation expectations, where the role would be based, and whether relocation assistance would be provided. I also wanted to know who I would be meeting with and the focus of each interview so I could prepare appropriately. I reached out to the recruiter for clarification before accepting the interviews.
After not hearing back over the weekend, the recruiter finally responded shortly before my first interview. She told me we could discuss my questions after the interview process. That surprised me, as every other large technology company—and even startups—that I've interviewed with has covered compensation expectations, role location, and relocation during the initial recruiter conversation to ensure mutual alignment before investing everyone's time. She did provide the interviewers' names and focus areas, but the information came so late that it wasn't particularly helpful for preparation.
Despite the lack of basic information, I decided to move forward because Microsoft has long been one of my top companies, and I viewed the interviews as an opportunity to learn more about the organization, the types of questions asked and build relationships.
My first interview was with the CVP. She was personable, and it was clear she is stretched thin and manages an extremely demanding workload. When she asked why I was interested in the role, I answered honestly that it was difficult to evaluate my interest because I still didn't know key details such as where the position was located or what the team specifically supported. It also seemed that she wasn't entirely certain where the role would ultimately be based.
My second interview was with the same lead admin I had already spoken with during the introductory call, which was unexpected. Rather than conducting another formal interview, he used the time as a follow-up conversation to discuss my meeting with the CVP and answer questions. During our discussion, it became apparent that his description of the role differed from what the CVP had shared, leaving me with conflicting information about the position's scope and priorities.
Ultimately, he asked whether I wanted to continue in the interview process. I explained that I didn't feel comfortable moving forward without understanding whether we were aligned on compensation expectations, where the role would be located, and whether relocation assistance would be available. He suggested I should be "more flexible" while interviewing with companies and explained that Microsoft typically doesn't discuss compensation specifics until an offer is extended.
I appreciated his feedback, but clarified that I wasn't trying to negotiate salary or discuss a final offer package. I simply wanted to confirm that my compensation expectations were within the role's range, understand where the position would be based, and know whether relocation would be supported. Those are standard conversations I've had early in the process with every major tech company (FAANG) and smaller companies I've interviewed with, and they help ensure both the candidate and employer are investing time wisely.
I'm not sure whether this experience reflects Microsoft's standard recruiting process or if it was unique to this particular situation. Either way, it was disappointing, as I had been looking forward to interviewing with Microsoft for the first time. Better communication, clearer expectations, and earlier conversations around foundational logistics would have created a much stronger candidate experience.