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 Research Software Development Engineer 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. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      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 Research Software Development Engineer

      1 juin 2012
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative

      Autres retours d’entretien d’embauche pour un poste comme Research Software Development Engineer chez Microsoft

      Entretien pour Research Software Development Engineer

      5 mai 2017
      Employé (anonyme)
      Redmond, WA
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez Microsoft en juin 2008

      Entretien

      The HR asked me if I could remember all Windows APIs first. I was shocked. Why would I spend time doing that when IDE can provide everything? I don't need to develop software in Notepad. Then I was asked to describe how would I design a system for automated selling machines. I spent five minutes to express my idea. There were other questions.

      Questions d'entretien [1]

      Question 1

      How many windows APIs do you remember?
      3 réponse(s)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Microsoft (Redmond, WA)

      Entretien

      First, one of the team members called me on the phone and we had a short chat about what the role requires and my resume. Then I had a standard phone call with an HR person who set up the technical phone interview as the next step. After this step, I got invited to go onsite. After five rounds of interview we called it a day, and within a week I received an offer.

      Questions d'entretien [1]

      Question 1

      NDA
      Répondre à cette question
      5

      Entretien pour Research Software Development Engineer

      19 mars 2016
      Candidat à l'entretien anonyme
      Le Caire,
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Microsoft (Le Caire, ) en mars 2016

      Entretien

      - Technical test composed of 8 questions in 2 hours on hackerrank.com. 1 question on probability, 1 question on algorithms, 6 coding questions; mainly on arrays, linked-lists and BST as well as a math problem. - Invited for an onsite technical interview, It was at least 3 interviews. First Interview was about algorithms and how to solve a problem till you write its code. Second was a design interview, mainly about OOP. I couldn't pass the second interview, so I don't know what the third interview was supposed to be about.

      Questions d'entretien [4]

      Question 1

      1) Array of length n, its elements are x-powers of the range (1 to n+1). There is one repeated element, find it. - The interviewer helps you till you reach the final solution, but he keeps asking about time and space complexity of each move you do. He may ask you to implement system functions like pow, sqrt and so on.
      Répondre à cette question

      Question 2

      2) Can static functions work on non-static members?
      Répondre à cette question

      Question 3

      3) Design a logger class.
      Répondre à cette question

      Question 4

      4) What's n-tier applications?
      Répondre à cette question
      5

      Entretien pour Research Software Development Engineer

      24 oct. 2015
      Employé (anonyme)
      Redmond, WA
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 2 jours. J'ai passé un entretien chez Microsoft (Redmond, WA) en oct. 2015

      Entretien

      Very pleasant interview process. Since I'm about to graduate with a PhD, I interviewed with two teams: one a very research-y team, and the other a software development team. Both interviews were extremely pleasant. The interviewers were genuinely nice, and allowed me plenty of time for me to ask them questions about the team and the role I would play. In terms of actual questions, the research-y team had most of the interviewers asking me about my ideas on the research problems they were trying to solve, with only one actual "coding" interview, which dealt with the standard tree traversal questions, and the design for a battleship game, with the challenge question being about how to scale up the battleship game to a large grid. The other team had more coding style questions, but most of them were not about writing code per se, but more of designing data structures and algorithms to solve specific problems in distributed sorting, google doc style spreadsheets, etc. Lots of puzzle/brainteaser questions from this team as well. Overall, a great interview experience!

      Questions d'entretien [1]

      Question 1

      Design for a google doc style spreadsheet, with a focus on how to handle multiple concurrent edits and formulas on the spreadsheet.
      2 réponse(s)
      3