Candidatei-me por meio de uma faculdade ou universidade. O processo levou 3 semanas. Fui entrevistado pela Microsoft em dez. de 2017
Entrevista
Applied through university for a role in Mountain View, CA and received an invite to do an on-campus interview with a rep. Interviewer was fairly chill but also pretty dgaf (he's been doing it all day and I was the 2nd to last interview so he's probably tired)
Afterwards, got invited to an on-campus interview in SEATTLE (ok so I applied for a role in Mountain View and was getting flown out to Seattle. I thought this was a bit strange but not out of the question since their HQ is in WA).
Got on-site and had 5 total interviews (1 was behavioral). Right before my 3rd interview started, I got an email from my recruiter telling me that the role I was applying for in Mountain View was accidentally marked as available and was actually not hiring. Thus, my recruiter told me that if I wanted to, I could just leave and go home. I decided to just finish the remaining interviews anyways for practice but this was overall a giant waste of time. Got flown out to Seattle for two days for nothing.
Candidatei-me online. Fiz uma entrevista na empresa Microsoft (Melbourne).
Entrevista
After submitting an online application, I received a HackerRank assessment after passing the resume screening stage, then I was rejected after completing the assessment and did not proceed to further interview rounds.
Perguntas de entrevista [1]
Pergunta 1
The assessment consisted of two LeetCode-medium-level coding questions to be completed within 75 minutes.
Fiz uma entrevista na empresa Microsoft (San Francisco, CA).
Entrevista
45 mins technical interview with a member of their San fran team. Very relaxed and informal but questions were focused and lots of follow ups. Easy to schedule as was over video conferencing platform
Fiz uma entrevista na empresa Microsoft (Seattle, WA).
Entrevista
Straightforward technical loop overall, with strong interviewers at every stage. I genuinely enjoyed the in-depth conversations around technical challenges and algorithmic problem-solving — the entire process felt well-structured and genuinely engaging.