At first, I thought this was some April fool's joke when I received the rejection email from Microsoft Swiftkey, not because I was expecting a positive reply, because how much my words were twisted in the last round of the interview and then were stated as a reason for rejection. The reason was that I had stated that in future I wanted to become a System/Solutions Architect , and as per Microsoft and that is something that sales people do, not Devops Engineers. Also, because "Gluing/Using existing tools together with automation, to help Developers deliver solutions faster and better, " is probably not something that Devops Engineers do. I might have got the definition wrong, have no idea what Devops Engineers do anymore I think. About the process, 6 Rounds in total. First a phone call with HR, second a telephonic interview with Hiring Manager, then 3 rounds of face to face interviews on-site on the same day. The idea that would be told to you by HR will be that they conduct 4 rounds with 4 different interviewers so that Microsoft can receive an independent, unbiased opinion from all the interviewers, you may perform well in two and not so well in two and that wouldnt impact the outcome that much considering that two interviewers are very impressed by you. HOWEVER, in reality that is far far from truth. The outcome would be only dependant upon how you perform in the last round, the one with senior management (so keep an eye on the titles), whose main intention will be to make sure that you dont "leak" into Microsoft from Swiftkey somehow. The senior management person will be interested in all your previous role, most importantly why you left em, would try to question you in various ways just to find out if you are lying or not. Besides this, the other three rounds will be purely technical white board algorithm questions, if you have interviewed for Developer roles after uni in the past you would be better off. Typical questions from books like '100 coding questions to crack and whiteboard interviews'. There will be no systems/architecture based questions, bacause they are looking for a Developer, not a Devops Engineer, its just a badly advertised/described role. I didnt know about any of this when I showed up for the interview, so I hope this helps out atleast a few folks out there