I had an interview with a series of 4 or 5 Technical Engineers in person, and one phone interview prior to that. I was taken up to their Northern California campus and led around to various offices for a series of interview questions. Of those, I had more interviews related to abstractly figuring out problems software product manufacturers were having, and less on actual coding expertise. The process took about 3 hours, not counting the short breaks in-between interviews. Thankfully, I was with a group of other people interviewing at the same time, so the interviews were one-on-one, but I could at least talk to them before, during, and after to decompress a little.
How would you manage to work with an API that does not have support for a critical function of the customer's product?
The following metrics were computed from 1 interview experience for the Microsoft Technical Evangelist role in San Jose, California.
Microsoft's interview process for their Technical Evangelist roles in San Jose, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Microsoft's Technical Evangelist interview process in San Jose, California.