Software Development Engineer Interview Experience - Redmond, Washington
Process
The process was long and tiring. First, there was the screening at my university. This included a few logic questions (geometry, etc.) with a Microsoft engineer.
Then, a few weeks later, came the onsite interview, which consisted of one-on-one interviews with approximately six engineers, going from 8 a.m. to after 5 p.m. Questions there ranged from the purely syntactical (recursively reverse a singly linked list) to more design-oriented (designing a radar system to keep track of bowies and their distances from an island, etc.).
Questions
Recursively reverse a singly linked list.
Was this helpful?
Interview Statistics
The following metrics were computed from 214 interview experiences for the Microsoft Software Development Engineer role in Redmond, Washington.
Success Rate
Microsoft's interview process for their Software Development Engineer roles in Redmond, Washington is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Microsoft's Software Development Engineer interview process in Redmond, Washington.
Microsoft Work Experiences
- 3.0Boring, safe, and predictable, like a family sedanSoftware Development Engineer • Current EmployeeRedmond, Washington, United StatesJune 23, 2008Pros: The benefits are top-notch. The pay is solid, if not spectacular, but decent given the stability and low risk. In teams I've been on, work-life balance is excellent. Oh, and occasionally we get to write software.Cons: It's hard to get anything interesting done at a company this size. More energy goes into covering your butt and navigating the tangled web of interdependencies than into innovation.
- 5.0Great Company, High RentSoftware Development Engineer • Current EmployeeRedmond, Washington, United StatesMay 7, 2008Pros: Great company to work for.Cons: Cost of housing in Seattle area
- 2.0Politics, slow-moving, crappySoftware Development Engineer • Former EmployeeRedmond, Washington, United StatesFebruary 12, 2015Pros: Large scale, smart people. There is a word minimum, so many more words. Why is there a minimum? Words, words, words, words! La la la...Cons: There was lots of in-fighting. I worked on boring projects, with lots of planning compared to the amount of code I got to write. There were also lots of meetings. One of my projects was scrapped because they had to re-assign my testers to another project, even though I had completed the coding work.
Microsoft Interview Questions
