Passed the online assessment which consisted of two easy or possibly medium level LeetCode questions.
Coordinated setting up an interview through various recruiter contractors who refused to speak with me about the role. Got sent reems of prep material that was either impossible to do (know details about the role, and the people interviewing me), or was review stuff that wasn't matched up with what I asked (e.g. design Netflix/YouTube, design an Elevator System). Much of the information I got ahead of time conflicted with each other.
I spent 5 hours (including breaks) on interviews. I thought I did reasonably well, but apparently not good enough to move on. I thoughtI had a good rapore with everyone. In the end, the interview coordinator told me I didn't do well enough, but invited me to apply again in the future. When I ask when I can apply again, and for details on what I did well / what I didn't do well, I get ghosted.
I've interviewed at dozens of places, and this was by far the worst set of recruiters I've ever worked with. They should be ashamed.
Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en Microsoft
Acudí a una entrevista en Microsoft (San Jose, CA)
Entrevista
Started with a recruiter phone call and a 30 minute phone call with the hiring manager to negotiate a remote role since the job was based in Seattle and the manager agreed. Following up with five rounds of virtual on site. Four of them are coding/design. One of them is behavioral mostly leetcode medium level questions which I finished and I was able to do all the follow up and answer the design and time complexity questions correctly after the interview got ghosted for a whole month and got an automatic rejection email.
Preguntas de entrevista [1]
Pregunta 1
Leet code medium level questions. DFS, BFS, sliding windows and greedy algorithm. Follow up, asking some design questions and the time complexity of the code.
Phone interview with hiring manager for 45 minutes primarily a tech interview. Focused on questions directly related to tech stack. Come prepared knowing design questions and how those conversations go.