Ho presentato la mia candidatura tramite un'agenzia di reclutamento personale. Ho sostenuto un colloquio presso Microsoft (Bruxelles)
Colloquio
Assez long, screening HR, premier interview HR, puis plusieurs interviews contenus avant de revenir pour deux derniers interviews pour négocier salaire et avantage. Assez long dans l'ensemble avec des périodes sans nouvelles. Les différents interviews permettent de rencontrer différentes personnes de différents départements afin de se faire une idée de la société et de sa structure.
Domande di colloquio [1]
Domanda 1
Décrire la vue et la position de Microsoft sur la marché et vis-à-vis de la concurrence, points forts et faibles des solutions, comment s'intégrer, quelle est le parcours précédent, pourquoi changer et pourquoi Microsoft, ......
Ho sostenuto un colloquio presso Microsoft (Tel Aviv)
Colloquio
The Microsoft Principal Architect interview was intense. The first round focused on LeetCode problems testing algorithms and data structures - binary trees, dynamic programming, and graph traversal challenges that assessed coding proficiency and optimization skills.
The second round simulated architecting a large-scale system. The interviewer presented a scenario requiring a globally distributed cloud application. Candidates needed to:
Design the system architecture using Azure services
Plan for high availability and disaster recovery
Implement security best practices and compliance requirements
Optimize for performance and cost
Demonstrate knowledge of microservices, containerization, and serverless
Handle database scaling and data consistency challenges
Present monitoring and observability solutions
The panel evaluated technical depth, decision-making rationale, and ability to adapt the design based on evolving requirements. Leadership and communication skills were assessed through system design discussions and stakeholder interactions.
Ho presentato la mia candidatura online. La procedura ha richiesto 2 giorni. Ho sostenuto un colloquio presso Microsoft (Ottawa, ON) nel mese di gen 2016
Colloquio
Technical depth. Had several scenarios that you had to identify how you'd solve based on customer requirements and issues. Not one size fits all but why you would select one approach over another.
