Microsoft Interview Experience 🔥Software Engineer | Web Developer

so uh so i was interviewed with microsoft like around a couple of months back for the bangalore location and the role was uh the role which i was being hired for was a software engineer front-end too and the team was microsoft teams so microsoft teams is a product by microsoft which is just like slack and it has a lot of more integrations with other products of microsoft and it is popularly used in enterprises for chats and sharing files and a lot of other stuff so it's great so now about how i got to their interview so i was approached by a recruiter on linkedin so somehow the recruiter got my profile and they called me up and uh asked me that whether i am looking for and whether i would like to try with microsoft for a fronted role so i said yes and then i was being called directly for the interview at the bangalore office so that was it and yeah so generally microsoft before calling the people to on-site they generally take a telephonic round before but i don't know in my case they just directly called me to the site itself and then i was directly being interviewed face to face i faced four rounds of interview which were done over a period of two days like uh first day i had two rounds and then i think the interviewers were not were a little busy or something then then i was called again for the second day where i had two more rounds with the senior manager so those were the four rounds of interviews which i have faced and and the interview process like in a week i went two days and the interview was completed within a week however they offered me quite quite after some time so you have you should be patient if you are interviewing that is what my experience was so i was offered like around three weeks after the interviews were done so so let me move on to the rounds what i faced and what was the more main focus area in each of these specific rounds and the questions which were being asked so first of all i would like to tell you that uh while i was interviewing for microsoft in each of the rounds i was asked to write the code on the whiteboard or i was just using the whiteboard to explain everything unlike uber like in uber generally we give the candidate the preference to use their laptop and can code along with us and that's how we do it but you can again feel free to use whiteboards or something but here on microsoft generally i was solving the problem and telling my approach on the whiteboards yes i was being asked to write the code for a specific problem in the first round so let me start with the first round first so in the first round i was being interviewed for general ui concepts that is what the only round was mainly focusing on ui i guess otherwise all the other rounds were quite generic and in this first round i was asked to uh code it on i was asked to develop a small web application using vanilla javascript so the web application was something like to develop a small uh a small email client which will have certain folders like inbox and items and something and then you have some of the emails tagged to those folders and if you click on those emails then you can open an email separately so it was something like that you can come up with your own design and can uh do the things so and you can also assume these emails to be in a json whatever you want to the main focus area what the interviewer was trying to assess was the use of vanilla javascript and how well i can manage things how good i am writing code am i being modular or not and all these other stuff so few features which which were asked to develop were mainly focused on persisting the state of the application making a dynamic behavior suppose if i if a new mail comes in and if a new mail is added to the json then how your ui should render and how dynamically everything should modularize and and also uh suppose the mail could be read or unread so you have to tag each mail with a red or a red flag and then according to that you need to persist their state if you have clicked on the mail and you have that mail unread then you need to purchase that state even if i refresh the browser and these was the kind of functionalities which were asked to be developed and so it was basically the use of uh they were trying to check whether i can uh properly use a local storage and what should i use like and what i am using to uh maintain the state and how i am writing the code so that was it so i felt that as very easy like it was not that tough and like i was given one one hour of time for solving this i did it in around 50 minutes or something and then i was just brushing up with these css and other things and i completed it in one hour and then i submitted it uh i uh i submitted the code to the interviewer so that was about the first round i and the interviewer was quite nice like he explained me the problem quite well and there was no i didn't ask for any help or i didn't need any help in the process so but the interviewer was quite friendly and helpful so this was all about the first round now the second round uh was after an hour gap between the first interview and i went for lunch after that and then i came back and then i had the second round the second round of interview was majorly focusing on data structures i think they were not going deep into the data structures but they were generally trying to see whether i am good at handling nested objects and all those stuff so one pro problem which i remember was asked was something like suppose you have a menu of a e-commerce site which can be nested at any level so suppose if you have electronics the electronics can have suppose a brand samsung and that brand can have cameras mobiles and other stuff then in cameras you can have different type of companies can and other companies and then in the canon we have one more uh level of hierarchy where we are listing down all the cameras so suppose if you have a json something similar to that and the interviewer was asking me to uh asking me to search the products and then how you are how we will be nesting it how will be how you will be routing through those products and so all the other stuff so they were just trying to check whether how comfortable i am in handling these nested objects and how well do i use data structures how will i map all those and how will i sort them and like similar stuff so it was more of like uh the general thing uh i didn't feel it much stuff because just because these are the kind of problems which we handle in our code daily and we use objects and all a lot and then we try to manipulate it so that was it nothing complex was asked like any trees or graph questions so it was basic nested objects so i wrote some recursive solutions to traverse that thing and then search and sort accordingly so that was it it was uh it was good then that was uh these were the two rounds which happened in the first day and then i was called for the second day again for two more rounds on the second day i had my third round in the morning those rounds were again not focusing on the front end but they were purely focusing on design and how to approach the problem statement and it was quite of more generic and i think and the interviewers were quite quite senior and they had experience of around 10-15 years and they were i think leads or managers i'm not sure about that but but they were good so in the third round i was asked to design a load balancer like the interviewer started with asking me the problems what i face uh while my day-to-day work and what kind of projects i am working on right now and all those i told and then afterwards i don't know how the conversion led to load balancers and then he asked me to write a solution to communicate between the nodes and the load balancers how we can manage different nodes and how the load balancer how the load balancer just transfers the load to all these nodes and i was asked to write a specific type of algorithm where we can efficiently use all the nodes and those type of stuff so the conversion went more deep into how we can scale this and what type of data structures will be used and how i am managing if the node goes down and all those things related to load balancer and how our projects will be kept deployed and all those things so that was the main thing uh which was being talked about apart from that the interviewer was asking me questions from the projects which i did only and uh he was basically drilling down into the core concepts and thing which i have already worked upon and which i can use to solve problems uh and come up with some solution and good approach so that is what the interviewer was trying to look upon so the interviewer was quite helpful and uh i was going in some wrong direction and then he identified that oh if you use this uh set of approach then you will face such problems and then he was trying to help me with some hints so that i can uh rectify those problems and he was quite helpful and the interviewer was more of two-way like we were both communicating a lot and it was a mix and match and i felt really good like uh it was not tough but yeah tricky i would say so uh that that was the second third round uh on second day and then afterwards i had the fourth round uh it was like back to back i had the third round and then within 15 minutes the fourth round was scheduled so the fourth round was again taken by a senior person of microsoft so in that round it was mainly focused on design so i was asked the question to design a online multiplayer chess so the problem was huge and huge in different dimensions so i need to come up with some high level diagram of how i'll manage the whole application what all things i will use what all things you i will use how will set up the environment and uh it was basically focusing on the scaling of the web app and then what things you will have in back end what things you will have in front front end what data will you keep in memory what data will you keep in database and how you will design the ui how it should look like what data structures will you use to keep the chessboard and the chess players and a lot of things like if it is an online multiplayer chess then definitely it would be a problem for scaling as well how will you scale your web app how can multiple players join a game and then what is a game actually how will you define your classes how will you modularize it so that was a huge multi-dimensional problem i would say and it was fun to solve it like i was i was getting uh stressed by it but still it was very fun to solve the interviewer helped me at certain points and then he was identifying some problems which i had in my designs and then he was trying to help me by telling me identifying the problems and then he was asking me for possible solutions and that is what he was focusing on mainly and we spent like around more than an hour in fact i guess one hour and 20 minutes uh just about solving all these uh problems in different dimensions so again i started with a very high level diagram of how i will try to keep my data and how i will try to manage different users and and then i was slowly focusing on separate components smaller components and then devising algorithm so some at some point of time the interviewer was asking me to write code for uh code for specific set of problems like uh how will you validate a move for a queen or how will you validate a move for a bishop so that's what the interviewer was asking me in between and sometimes like suppose how will you manage the manage such load and traffic on your website and how will you make it fast and how can a user start a game how can uh how can uh so whether you will keep the logic for validating a move in front end or a back end and then we had a great discussion in that question like whether we should keep a algorithm of checking the moves in front end or on back end it should be client-side or server-side how fast we can make it and then and then that is what uh basically the interviewers trying to guess so after the interview even i didn't know that whether i did good or bad but yeah it was a completely good experience i would say yeah so that was all the four rounds i had so if i talk about the overall experience it was very awesome like each and every interviewer was very helpful very polite and was helping me and was trying to listen and understand what how i am trying to approach the problems and they were giving me hints and then they were identifying the problems and my solution and were making me think actually uh and uh getting to the solution so that was all i liked and it was worth the experience like you should definitely experience that uh once in a while so it was one of my best interview experience i would say and so that was all about the microsoft interview experience what i had and so yeah that's it for this video and if you got to learn something from this video then do give it a thumbs up and i would also be coming up with uh more interview experiences in this series of videos so stay subscribed to this channel and press the bell icon for all the notifications about all the interview experiences and check out the other videos where i have listed down main interview problems and i am solving them right in front of you in the video so that you get a better idea of how to approach those problems in interviews when asked and and i have also recently started a facebook group where you can join and connect with other fellow web developers where we have this community where we share our doubts and help each other we help with referrals references recommendations and that's how we grow right so stay connected that's all for now and thanks for watching

Channel: Akshay Saini

Views: 78,323

Rating: 4.8969593 out of 5

Keywords: akshaysaini.in, akshay saini javascript, akshay saini web engineer, akshay saini uber, javascript interview questions, frontend interview questions, javascript fundamentals, akshay saini js, microsoft Interview experience, microsoft Interview Questions, microsoft interview tips, microsoft interview, Microsoft Interview rounds, microsoft software engineer interview, microsoft interview frontend, how to get a job at microsoft, akshay saini microsoft, microsoft offer letter

Id: pjs1ZLjZhzk

Length: 16min 47sec (1007 seconds)

Published: Fri Mar 08 2019