Questions entretien Software Development Engineer In Test (SDET) chez Microsoft | Glassdoor.ca

Questions entretien Software Development Engineer In Test (SDET) chez Microsoft

Entretiens chez Microsoft

516 Avis sur les entretiens

Expérience

Expérience
65%
27%
8%

Obtenir un entretien

Obtenir un entretien
52%
22%
12%
9
2
2
1

Difficulté

3,3
Moyenne

Difficulté

Difficile
Moyenne
Facile

 

Entretien de Software Development Engineer In Test (SDET)

Candidat à l'entretien anonyme - Bellevue, WA (États-Unis)
Aucune offre d'embauche
Expérience neutre
Difficulté moyenne

Candidature

Le processus a pris +2 semaines. J'ai passé un entretien à Microsoft (Bellevue, WA (États-Unis)) en mai 2012.

Entretien

receive a call from the manager, no response

Questions d'entretien d'embauche

Autres avis d'entretien pour Microsoft

  1.  

    Entretien de Software Development Engineer In Test (SDET)

    Employé anonyme - Redmond, WA (États-Unis)
    Offre d'embauche acceptée
    Expérience neutre
    Entretien dificile

    Candidature

    J'ai postulé via une recommandation d'un employé. Le processus a pris 2 jours. J'ai passé un entretien à Microsoft (Redmond, WA (États-Unis)) en juin 2010.

    Entretien

    I was referred to MS for a position on a team that was hiring. What happens when you interview there is that you interview with one team, 1:1 interviews all day back to back, with a lunch time interview, and if you are doing well you will meet a VP or other manager at the end of your interview day. Microsoft likes to give you alternatives for what team you want to work for, so you will probably meet a second manager, possibly the day after, to give you an alternative for what team to join. For the lunch interview, we went to Chili's and didn't talk tech. All other interviews were technical in nature, having you solve programming questions on a whiteboard, such as implementing atoi() etc

    Questions d'entretien d'embauche

    • Implement a function that turns a string into a number with sign.   2 Réponses
    • Implement a queue using only the stack data structure   1 réponse

    Négociation

    I pushed back on the salary and got a bump of about 2K after I received the offer.


  2.  

    Entretien de Software Development Engineer In Test (SDET)

    Candidat à l'entretien anonyme - Redmond, WA (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Entretien dificile

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris 2 jours. J'ai passé un entretien à Microsoft (Redmond, WA (États-Unis)) en novembre 2011.

    Entretien

    It was difficult with a lot of problem solving and SQL related questions.

    Questions d'entretien d'embauche

  3. Utile (1)  

    Entretien de Software Development Engineer In Test (SDET)

    Employé anonyme - Seattle, WA (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris 3 semaines. J'ai passé un entretien à Microsoft (Seattle, WA (États-Unis)) en avril 2012.

    Entretien

    All started with handing out my resume at my university's carrier fair. MSFT's (Microsoft) rep was an SU Alumni and I had a recommendation which I guess helps a lot initially. We spoke about my projects, my interests, and how I like spending time, etc etc...
    I was shortlisted and an on-campus 1:1 interview was scheduled. This was a 30 to 45 minutes interview. Everyone were asked a programming question and a testing question. Both were pretty simple, coding question was to count the occurrences of every character in a given string. And the Testing question that I vaguely remember was to write test cases for a function that takes a string as input and does something. I was also asked to describe any scalability issue that I had faced in my previous projects.

    Then I was called for a final round of interviews to Seattle for an SDET position. On the day of the interview recruiter said I will be interviewing with Windows team. Thats a huge team and I could be interviewed by any team within it. But this already sounded exciting to me!

    1st interview was with a team lead from Kernel Team. He said he wanted to start my day with less rigorous coding question and asked me to write a function to return the nth Fibonacci number in the series, given integer n. I discussed my design choices before start the code, then wrote a first function where I used arrays, which was inefficient for a large input and then I discussed use of a liked list instead of arrays which wasn't any better with its memory foot print, then it flashed to me that I dont have to store the whole series and I just have to return what ever is required... He also asked for a recursive solution and asked to compare both solutions. Testing question was more of a learning for next rounds than the answers i gave. But learning is important.

    2nd round was with another team lead from Hyper-V team. Coding question was to rotate an image by 90 deg. Image is represented by a 2D int array. After bit of crumbling, I came to a solution. I was asked to device strategy to my own code. Again it was half learning from the interviewer and applying what I had learnt from earlier interviewer.

    3rd one was a lunch interview, so no coding question but lot of testing questions. Also he was expecting me to ask back as many questions.

    4th and final was with a manager. He asked a simple puzzle, a coding question to reverse a linked list using recursive technique. He also asked me about how other interviews went. Did a lot of talking here, not technical all the time, but about the day to day work at MSFT, about the team and what they are working on, etc.

    After couple hours, I heard from the recruiter that I did get through!

    Questions d'entretien d'embauche

    • how can a particular application be tested apart from testing its functionality   4 Réponses

    Négociation

    I could negotiate the team that I wanted to work in. I was satisfied with the salary offer, so I did not even try negotiating. I was not able to negotiate the role.


  4.  

    Entretien de Software Development Engineer In Test (SDET)

    Employé anonyme - Redmond, WA (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris +2 mois. J'ai passé un entretien à Microsoft (Redmond, WA (États-Unis)) en mars 2012.

    Entretien

    Mine is an Internship. Submit resume during campus career sessions. Got on campus interview (1st round, 1:1) 2 weeks later. Received result 2-3 weeks later and booked a date for on site interview after 2 weeks. Took almost 2 month before go to the final round. Got every notification of the process usually when forgot about it, but usually required to reply within one or two days.

    On site consists of 4-5 rounds 1:1 interviews with senior engineers/leaders/managers, including one lunch interview (coding maybe required before or after taking the food, so better have somthing "light" :]) Interviewers were nice, chat with them about your ideas and concerns will help you get as much support to finish the questions as possible. Ask questions to show your type of interests, this will help them decide which product team you are fit in. Prepare to brain storm when answering testing questions, better let them stop you than stop generating ideas yourself.

    You may get a decision shortly after the final round of interview and the offer ducument may be ready in days.

    Prepare to code on paper, review basic data structures and algorithms before go onsite. Sleep well before the interview, that's immportant.

    Generally, the work place is good, not much difference from Universities. Different office/building styles depending on the year of the building. Perfect transit system across the company. People get used to talk and walk in the rain. Many people from places other than Redmond initially. Not much time to look round during the onsite days.

    Questions d'entretien d'embauche

    • compare the value of two meaningful strings;   1 réponse
    • insertion operation on binary trees with some restrictions.   1 réponse
    • how to test a certain electric device.   1 réponse
    • convert strings into int types;   3 Réponses
    • searching for patterns in strings; how to destroy your functions with different testing cases;   2 Réponses

  5. Utile (1)  

    Entretien de Software Development Engineer In Test (SDET)

    Candidat à l'entretien anonyme - Redmond, WA (États-Unis)
    Aucune offre d'embauche
    Expérience neutre
    Difficulté moyenne

    Candidature

    J'ai postulé via un recruteur. Le processus a pris une semaine. J'ai passé un entretien à Microsoft (Redmond, WA (États-Unis)) en mars 2012.

    Entretien

    Basic HR questions like "Why are you interested in working for Microsoft?" and "What do you currently do in your job now?". Then 3 basic CS questions like "What is polymorphism?" and then a testing question. Got hung up on the testing question but gave an answer. Didn't get a second interview probably because I don't do any testing in my current position. GL to others, hope this helps

    Questions d'entretien d'embauche


  6.  

    Entretien de Software Development Engineer In Test (SDET)

    Candidat à l'entretien anonyme - Seattle, WA (États-Unis)
    Aucune offre d'embauche
    Expérience neutre
    Difficulté moyenne

    Candidature

    Le processus a pris 1 jour. J'ai passé un entretien à Microsoft (Seattle, WA (États-Unis)) en octobre 2011.

    Entretien

    Each interview followed a similar pattern: discuss your work, tell me about [software engineering topic] and your experience with it, now let’s do a coding problem. Sometimes I did a problem quickly and they made the problem more complicated, or gave me a completely separate one. I was not asked riddle-type questions. I was not asked dumb, typical HR-type questions (“What’s your biggest weakness?”).

    Between every interview they will talk to each other and they will send e-mails to the other people in the interview loop. Yes, they’re talking about you behind your back. And yes, they will tailor future questions to cover areas missed by previous interviewers, or to follow up on a weakness. Also, not every interviewer is on the team you’re interviewing for. I liked this because it gave me an opportunity to learn more about other groups.

    In the first interview, the coding problem was to generate a well-known data set. I first considered how to generate the nth iteration of the dataset, but she quickly steered me to solving iterations 1-n (which is much easier). I went over the algorithm in my head and out loud, before writing any code. Then I wrote the simplest, naive code that I could think of. I immediately saw some inefficiencies and worked to address them. She prodded me slightly to the answer she was looking for (I would have gotten there).

    Questions d'entretien d'embauche

    • In the first interview, the coding problem was to generate a well-known data set. I first considered how to generate the nth iteration of the dataset, but she quickly steered me to solving iterations 1-n (which is much easier).   Répondre à cette question

  7.  

    Entretien de Software Development Engineer In Test (SDET)

    Employé anonyme - Bellevue, WA (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Difficulté moyenne

    Candidature

    Le processus a pris 3 semaines. J'ai passé un entretien à Microsoft (Bellevue, WA (États-Unis)) en décembre 2011.

    Entretien

    The interviews consisted for 2 phone screens and an onsite interview. First phone-screen was with the manager of the group and focused on my experiences and some technical questions, e.g. "How would you approach testing an elevator?", "Hint: first list types of testplans you will need to write, and only then specific tests". Second phone screen was with one of the senior team members, was similar with the first one but more relaxed. After completing the phone cycle I got an email from the recruiter with invitation to come in for an in-person interview.

    My interview from what I head was not typical, since it started at 9AM and lasted up until 5. I met 6 interviewers. Several Senior Test leads, Development leads, developers and testers. Most interviews had "HR component" or general questions about testing and coding, with question such as:
    if you have a conflict with your subordinate how would you resolve it?
    if your product has 6 features, but your team has time to test only 5 - how would you chose which one to exclude?

    Core coding questions were fairly expected, and easy. The language of choice did not matter, as long as you can write psuedocode.

    Questions d'entretien d'embauche

    • Check if tic-tac-toe has a winner   5 Réponses
    • Delete n-th element from linked list. Note, you don't have a pointer to the Head of the list.   2 Réponses

    Négociation

    If the company really wants you they are prepared to offer more then initial offer.

  8.  

    Entretien de Software Development Engineer In Test (SDET)

    Candidat à l'entretien anonyme - Redmond, WA (États-Unis)
    Aucune offre d'embauche
    Expérience positive
    Entretien dificile

    Candidature

    Le processus a pris 2 jours. J'ai passé un entretien à Microsoft (Redmond, WA (États-Unis)) en décembre 2010.

    Entretien

    A recruiter came to my college campus and conducted an on campus interview. This interview was fairly simple, he asked me to talk about a project I had done and then asked me to write a method in java that determines whether a given string is a palindrome. Then a few weeks later they flew me out to Redmond, where I ended up doing 4 interviews. Three of them were fairly simple and one was pretty difficult because it involved writing a program on a whiteboard that involved multithreading. Overall, if you are prepared and confident, you'll do fine.

    Questions d'entretien d'embauche

    • Write a program in java that determines whether a string is a palindrome.   2 Réponses
    • Write a method (in a language that you are comfortable with) that determines whether one given string is a substring of another given string.   1 réponse
    • Given an array of integers in random order from 1 to 100, but one number was missing, name 3 ways you can find out which number was missing.   1 réponse
    • Write a program that acts as an application scheduler that runs executables at given times.   1 réponse

  9.  

    Entretien de Software Development Engineer In Test (SDET)

    Employé anonyme - Redmond, WA (États-Unis)
    Offre d'embauche acceptée
    Expérience positive
    Entretien dificile

    Candidature

    Le processus a pris +2 mois. J'ai passé un entretien à Microsoft (Redmond, WA (États-Unis)) en janvier 2012.

    Entretien

    I had an on-campus interview at my University, where the interviewer focused on design issues and basic algorithmic questions. I can remember couple of questions - how to determine if two circles intersect and how should a server behave if it has to crash (maybe gracefully) and come back up.
    On-site interview was scheduled after a month's wait, and I had to schedule it for the next month since they had no slots. December-Jan is the holiday season, I guess! On-site interview was 5 rounds. First two involved coding and then coming up with as many test cases as I could for that code, to achieve maximum coverage. 3rd was the lunch interview with test lead and very casual - mostly just chatting about the interviewer's experience with Microsoft so far, and many questions on my projects and internship.
    Fourth one with a test lead was tougher - totally testing oriented where I had to fix a piece of code he wrote on the board, and then many test cases for that piece of code. Also a very interesting question on how to test a map where he gave me an upside down map and we had a discussion on whether it was valid (it was an Australian classroom map, and valid.)
    Fifth interviewer was the test manager, and we had a great time classifying test cases for testing the find function on notepad. At the end he told me I had the job - I had requested an expedited answer since I had another offer pending.

    Questions d'entretien d'embauche

    Négociation

    I did not negotiate. This was my dream job and the offer is extremely competitive for a new grad.


Ne manquez aucun emploi que aimez
Ajoutez un CV pour postuler facilement à des offres depuis n'importe où. C'est simple à configurer.