Solicité el puesto a través de un captador. El proceso duró 4 semanas. Acudí a una entrevista en Microsoft (Tel Aviv)
Entrevista
- codelity questions: fix a binary search, write a simple crud app with dropwizard (2 hours)
- homework: write text classification CLI app given your input is path to scan on file system, json classification rules.
- 3 interviews one after another with 15 min break between each. 1 about the homework, 2 about stuff you did, 3 design interview.
- AA interview: talking about your entire past
Preguntas de entrevista [3]
Pregunta 1
- wanted to know why I left any company I worked for
- tell us about what *we* do in MDA (wtf??)
- tell me about a conflict in your job
- tell me of something you are proud of
- does it scare you to start in a new place?
Acudí a una entrevista en Microsoft (Vancouver, BC)
Entrevista
HR screening, one technical interview with the hiring manager then three interview loop which covered two system design and one dsa round.
System design was intensive and challenging.
It took them 5 weeks to come back with an offer. Background check was completed in a week, got joining date after 3 days.
Preguntas de entrevista [1]
Pregunta 1
Design a system for a startup company that let users post various types of content and get a unique url which can be shared with others to access the content
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.
