How do I bridge the "Microsoft-Scale" knowledge gap as someone considering applying to Microsoft?

[dwalleck]

As a long time C#/.NET user, I've slowly become more and more interested in moving towards taking a crack at the Microsoft interview process and working on the actual tools and libraries that I'm passionate about. However, there a lump of fear that swells up when I think of the size, complexity, and criticality of systems like .NET, Visual Studio, VSTS, or the mammoth challenge that is Windows. I do watch the ASP .NET Community Standup and it feels like the same types of problem solving I'm used to, just in different domains. How do people get over that learning curve? Do new team members come razor sharp across the board to hit the ground running or is there more of an understanding of "you're a smart and competent guy. You'll figure out how you fit in"?

[CamSoper]

Not Scott, but I'm a little qualified to answer as I've administered a few tech interviews in my tenure at MSFT. :)

It depends on the role you're going for, but in general, the interviewers should be looking for the fundamentals and intellectual curiosity. Be honest about what you know, what you don't, and what your best guesses are. No matter how much you know coming in, starting at MSFT consists of 1-6 months of drinking from the proverbial firehose.

Reach out to me if you'd like to chat more about this. :)