I had a screening interview on campus and was asked about my coursework and why I applied for the position.
I was also asked some theory questions related to my coursework, and then about my favorite software and hardware products and how I would improve them.
I was then called back for an onsite interview in Seattle, Washington. I met with four members of the same team: an SDET, a Dev, and the PM.
The interviews were all one hour long, except for the lunch interview, which was 1.5 hours.
These interviews were challenging. Getting the right answer wasn't the primary goal, as they would provide additional constraints and I would have to come up with another answer.
You are hired to make entries into a database. Your boss edits an entry but does not save it at the moment. You edit the same entry and save it. After this, your boss goes and saves his edit, thereby overwriting your entry.
What would you change in the database to avoid such a situation?
The following metrics were computed from 56 interview experiences for the Microsoft Software Development Engineer In Test (SDET) role in Seattle, Washington.
Microsoft's interview process for their Software Development Engineer In Test (SDET) roles in Seattle, Washington is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Microsoft's Software Development Engineer In Test (SDET) interview process in Seattle, Washington.