It was good but unfortunately didn't pass, everything was professional on their side, treated me very nice, made me a tour around the office and facility. The interview itself was a bit on the difficult side
Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en Microsoft en ene 2020
Entrevista
Recruiter Connect: It is highly recommended to maintain a good Linkedin profile to get noticed by Microsoft recruiters. It is also advised to connect with existing Microsoft employees to get referrals for job positions. The candidate can also try applying on the job portal.
Interview Rounds: The interview rounds start with an initial screening interview which is DS/Algo based. The later rounds are more technical and focus on DS/Algo skills along with system design knowledge.
After Interviews: Performance of the candidate is judged based on the past interviews and the verdict is decided. All of the interviewers hold a meeting to discuss and debate the ratings of candidates with the hiring manager.
Hired: Once the team and you both are comfortable and ready to start, the offer letter is prepared and shared with you by the recruiters and you are HIRED!
Preguntas de entrevista [1]
Pregunta 1
What is your favourite language and why?
How do you keep yourself updated about the new trends in the industry?
What’s the most recent thing that you have learned?
What is Pair-Programming? Have you ever done
One coding assessment and final round with three coding questions (leetcode easy-medium). A few behavioral questions and resume related questions were also asked during the final round. The assessment was a bit difficult and I didn’t pass all of the questions
The interview process for the Software Engineer (IC2 – Full Stack) role at Microsoft typically involves multiple stages designed to evaluate technical skills, problem-solving ability, and collaboration mindset.
Process Length: 2–3 weeks from initial screen to offer
Interview Format: Virtual (via Microsoft Teams)
Preguntas de entrevista [1]
Pregunta 1
One of the questions I got was a coding problem that tested both algorithmic thinking and code quality.
