We've helped several engineers get the job at Microsoft
Interview Cake is a systematic approach to solving any programming interview question. We've helped engineers get jobs at all the best tech companies, especially including Microsoft. We want to help you with even the toughest software engineer interview at Microsoft.
Microsoft has been one of the tech industry's giants for decades, and it shows in their coding interview. They expect a high degree of acumen and precision, so much so that it sets them apart from the vast majority of other companies that compete with Microsoft for talent. Microsoft interviews are tough, but they are solvable. Microsoft extends thousands of job offers a year, and you could be one of the engineers receiving one of those offers.
Get ready for Microsoft with the free 7-day crash course!
In this free email course, you'll learn the right way of thinking for breaking down the tricky algorithmic coding interview questions Microsoft loves to ask.
No CS degree necessary.
You're in!
Practice Questions for the Microsoft Interview
Microsoft's coding interviews are hard, but not impossible. Like anything else, it just takes practice. We'll walk you through it, step by step.
What people are saying about Microsoft's interview
Here are some positive snippets from interview reviews from Glassdoor:
"I got referred to a specific team at Microsoft as New Grad hiring was halted for 2016. Talked to a manager on the phone for an hour, and was asked about my resume and did a interview question. Was flown to Seattle 2 weeks later and had an onsite interview with the team at Redmond. It consisted of 5 interviews with coding and culture-fit questions. I was at the Microsoft Campus from 9AM to 4:30PM. The process was nice, and the interviews were more conversational than say Google onsite interviews. I got a call 2 days later with an offer to join the team."
"Everyone was super friendly and super excited about future of Microsoft under new CEO leadership."
"Took part in an interview event which lasted about half of the day. Four rounds of approximately one hour interviews with short breaks in between. The questions were based on algorithms and Big-O notation for run-time and space complexity. Questions were either straight from or similar to questions in Cracking the Coding Interview. Make sure you understand the complexity of the code you are writing or at least be able to walk through the calculation of it. Practice solving problems from Cracking the Coding Interview and you should do fine."
And here are some negative snippets from interview reviews from Glassdoor:
"I had the initial phone screen and got rejected 3 weeks later. They asked me a series of behavioral questions, and one logic puzzle (fruits and baskets with wrong labels). I am surprised and disappointed in the rejection because I feel that I'm a strong candidate (had final round interviews with very competitive companies). I solved the brain teaser and felt I did a decent job on the behavioral aspect. However, my interviewer was NOT a technical person, so she couldn't answer any of the more technical oriented questions I asked at the end. I remember my interview only lasted about 20 minutes. She ended my interview before I could think of more questions to ask. I am very confident that if I had a technical person interview me, they'd have a way better understanding of my skill set. Needless to say I won't be applying to Microsoft again."
"I attended the MS 30 min on-campus interview last week. I prepared a lot of behavior questions before but it turned out that the interviewer didn't ask any behavior questions. The coding problem he asked me was to find the next larger element in a BST. He didn't even defined the BST and the function declarations for me, so I had to define it by myself."
Actually, we don't support password-based login. Never have. Just the OAuth methods above. Why?
It's easy and quick. No "reset password" flow. No password to forget.
It lets us avoid storing passwords that hackers could access and use to try to log into our users' email or bank accounts.
It makes it harder for one person to share a paid Interview Cake account with multiple people.
“Interview Cake made all the difference for me. The questions are unmatched in caliber, and the web interface simulates real coding interviews. It's very challenging and therefore totally worth it.
—
Mikhail