Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Microsoft

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Microsoft | Offres d’emploi chez Microsoft | Salaires chez Microsoft | Avantages sociaux chez Microsoft
      Entretiens chez MicrosoftEntretiens d’embauche pour Cloud Solution Architect - Azure Infrastructure chez MicrosoftEntretien chez Microsoft


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Indeed, Inc. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Indeed, Inc.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Cloud Solution Architect - Azure Infrastructure

      14 déc. 2018
      Candidat à l'entretien anonyme
      Bakersfield, CA
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Microsoft (Bakersfield, CA) en nov. 2018

      Entretien

      Contacted by a recruiter through LinkedIn about an Irvine CA position. Answered and was asked to fill out a questionnaire. Interviewed by recruiter and told him that CA was not my first choice so the Recruiter added an Austin TX position to my "Action Center" profile. Was contacted and went through a second interview for technical, I was truthful and stated I was an AWS architect with some small experience and comparative knowledge on Azure. Interview was from a guy whose AWS questions I explained throughly and to his satisfaction, at least that was how the interview seemed to track. He explained that the position would be a cattle call to a city where 3 teams would spend about 2 hours with me and other candidates. I should be prepared to propose a solution if I were called for that 3rd interview. Never heard back from them after this until 2 weeks later when someone at Microsoft added a Chicago posting to to my "Action Center" area. The next week I was informed that I had not been selected for the Austin position via a form letter and the position was removed from my "Action Center" board. I then received an inquiry from another MS recruiter, this time a woman. She wanted to know if I was interested in the Irvine position, again. i was patient, answered her back and received another questionnaire, a little more detailed than the first one. The questions are not bad, and were good practice so I answered in greater detail . I explained where I had been in the process and share that I might not be someone she should consider. We scheduled a meeting via email. When we had the email, I carefully explained what had happened and after looking at her MS recruiting system, she informed me with apologies that there had been some confusion and that if I didn't hear from her in a week then contact her and she would get back to me. It's been over a week and I'm not going to contact her of the original recruiter. Obviously MS has some issues when recruiting for positions. These firms are 3rd party contractors hired by MS to hire for them. More than a little unorganized and although I was happy to be considered, I was a little disappointed in the communication, if not the lack of results.

      Questions d'entretien [1]

      Question 1

      Reasons/Motivation to make a career move. Why Microsoft? Key technology area: Cloud (Infra/AppDev/DevOps)? Describe your role: (more PreSales or Sol Architect) If PreSales – how many sales people or clients do you have? If Solution Architect – describe your cloud work or cloud specialization: Infrastructure or AppDev or DevOps? Which cloud platforms are you most proficient on (AWS, Azure, GCP etc)? Do you have cloud solution application certifications? Which ones? Explain your cloud migrations: Lift and Shift, Refactoring, Replatforming? Do you script out infrastructure for migrations to the cloud? If so, what scripting language/tool do you use i.e.: PowerShell? INRASTRUCTURE: Talk to me about core IaaS work you have done in the cloud: (virtual machines, load balancing, storage, Active Directory, automation, disaster recovery) APPDEV: What is the last application you wrote for the cloud? Cloud Native? or App rearchitecting? APPDEV: What is your language of choice in coding apps for the cloud? (.Net, Java, C#, C++, Python etc) APPDEV: What did your application address in your client’s business? (finance, reporting, IoT of products, billing, payment processing, chatbot, etc) APPDEV: If you have never used an API, how quickly can you come up to speed to work with it? DEVOPS: What technologies have you used for DevOps? (Chef, Puppet, VSTS, Docker, Kubernetes, any container technologies/orchestration) Without describing the technology used, what was the largest client cloud project you worked on and what was the business driver for the project? Tell me about any experience you have had when you lead the discussion on moving to the cloud. Who was your audience when you presented the how, what, when, and why the move to the cloud. (LOB, IT, C-Suite) Are your clients internal, or facing externally to clients?What have been the biggest roadblocks or challenges you have faced when suggesting a move to the cloud? How did you influence the decision for that move? What was your role in that presentation to influence business decisions? What industries do you have experience in?
      Répondre à cette question
      3

      Autres retours d’entretien d’embauche pour un poste comme Cloud Solution Architect - Azure Infrastructure chez Microsoft

      Entretien pour Cloud Solution Architect - Azure Infrastructure

      24 nov. 2022
      Employé (anonyme)
      Londres, Angleterre
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 5 mois. J'ai passé un entretien chez Microsoft (Londres, Angleterre)

      Entretien

      I applied on the Microsoft careers page. I had a call with the recruiter, it was a very quick call. Just to let me know that they liked my CV, wanted to introduce himself and have a quick chat with me. Then basically just told me that he'll set up a meeting for a technical interview. A few weeks later I had 30-minute interview with a senior member on the team. The interviewer was very friendly and made me feel at ease. The questions were fairly simple in my opinion, having 9 years of experience total and 2.5 years with Azure. The interviewer didn't give off much at the end of the interview but wished me good luck in the rest of the process. I checked in with my recruiter a couple times over the next couple of weeks for a status update. I was then invited to do a hiring day which consisted of three 45 minute interviews back to back . The first interview I did was a more advanced technical interview. We went quite a bit deeper on subjects within Azure. I made a point to stick to the STAR answering method. When I didn't know a question, I didn't babble on lying about it. I apologised and said I didn't know the answer to the question, but detailed resources that I would use to start troubleshooting and figuring it out. Whenever I had any related experiences I brought those up, detailed the situation, what I needed to do, how I went about doing it and the result. The second interview was a project presentation. I had to give a sales/business style presentation on a project I'd recently done. How I decided to design the architecture solution and presented a visio file. I discussed the costs and how we settled on those, how it would be supported and other design reasons. Note that this was aimed for a non-technical type interview. They wanted to understand my business presentation skills for all levels of attendees. After the project presentation was finished I was asked a few more questions to demonstrate scenarios I'd had with customers. Giving examples of negotiations, discovery, agreeing on points which needed to be fixed, how we'd get there, set expectations etc. All the usual stuff you'd expect. Then I had a manager interview to finish where I was asked more about my previous experiences, my motivations, mindset, aspirations. I spoke about my values, how they aligned with Microsoft values, how I get my enjoyment from my work, examples of how I've helped build team morale and motivations within work, improvements I've made etc. After this hiring day, it took about 3-4 weeks for the positive feedback from my recruiter. Negotiations and offer then happened over the following two weeks.

      Questions d'entretien [1]

      Question 1

      Describe to me, what is DevOps? Tell me how private DNS resolution works from on-prem and Azure. How would you design a resilient application solution. Tell me the difference between availability sets and availability zones. How can you decrease latency with an application design and infrastructure.
      Répondre à cette question