Live data from Hacker News

Microsoft changed how it interviews software developers

businessinsider.fr

21–30 of 348 posts

Re: Microsoft changed how it interviews software developers

#21
post #20
post #3

https://blog.usejournal.com/rethinking-how-we-interview-in-m... is the original post by a PM at Microsoft. It doesn't have any useful information about a pure technical interview for software engineering. >(Note: I started at Microsoft when we were still asking questions about why manhole covers were round, how many ping pong balls would fill a 747, and how to reverse a linked list. In 20 years here, I’ve yet to have…

Manhole question is bad, because around half manholes im real world are squared. So the correct answer is that they are not in fact round and square works perfectly fine. Of course I know right answer, but it has zero to do with me being smart and a lot to do with me being in right culture and thus having heard about it before. Which is exactly what it test along with other brain teasers - have you encountered this s…

Haha. That was exactly what I was thinking! I have yet to see a round one! Lol

Re: Microsoft changed how it interviews software developers

#22
post #3

https://blog.usejournal.com/rethinking-how-we-interview-in-m... is the original post by a PM at Microsoft. It doesn't have any useful information about a pure technical interview for software engineering. >(Note: I started at Microsoft when we were still asking questions about why manhole covers were round, how many ping pong balls would fill a 747, and how to reverse a linked list. In 20 years here, I’ve yet to have…

Google stopped asking brainteaser questions like that because they found no correlation in its hiring usefulness.

I think it's true for majority of questions (apparently leetcoding is the new thing at Google and also FB). IMHO interning for a few weeks is the best for both sides - unfortunately it doesnt scale.

Re: Microsoft changed how it interviews software developers

#23
post #3

https://blog.usejournal.com/rethinking-how-we-interview-in-m... is the original post by a PM at Microsoft. It doesn't have any useful information about a pure technical interview for software engineering. >(Note: I started at Microsoft when we were still asking questions about why manhole covers were round, how many ping pong balls would fill a 747, and how to reverse a linked list. In 20 years here, I’ve yet to have…

Google stopped asking brainteaser questions like that because they found no correlation in its hiring usefulness.

I'll be the obligatory ex Googler claiming Google never did ask brainteaser questions, or at least they were long gone by 2006.

Re: Microsoft changed how it interviews software developers

#24
The original article [1] describes new process in the context of PM interviews, which are different from software developer interview, no matter how technical PM is.

The changes that I particularly like are: improvement in coordination between interviewers themselves, and stop sharing feedback between themselves until the very end. The latter really affects how next interviewers view the interviewee.

[1] https://blog.usejournal.com/rethinking-how-we-interview-in-m...

Re: Microsoft changed how it interviews software developers

#25
post #15

Earlier quoted context omitted.

According to the Wikipedia [1] Reasons for the shape might include: * A round manhole cover cannot fall through its circular opening, whereas a square manhole cover might fall in if it were inserted diagonally in the hole. The existence of a "lip" holding up the lid means that the underlying hole is smaller than the cover, so that other shapes might suffice. (A Reuleaux triangle or other curve of constant width would…

Don't forget also: round manhole covers are a Schelling point. Making a manhole cover round is one of the first intuitive shapes you'd think to make them (along with squares and rectangles); and so you'd guess, as a construction company gearing up to sell the concept of concrete manholes with removable iron-plate covers to a municipality (back in the 1800s or whenever we first got them) that what the municipality wil…

Thanks for explaining why roads are round!

Re: Microsoft changed how it interviews software developers

#26

The original article [1] describes new process in the context of PM interviews, which are different from software developer interview, no matter how technical PM is. The changes that I particularly like are: improvement in coordination between interviewers themselves, and stop sharing feedback between themselves until the very end. The latter really affects how next interviewers view the interviewee. [1] https://blog…

After reading about wisdom of the crowds, we started doing this with estimates. We always break up the project into small tasks together then seperate and estimate them individually.

We've found we're a lot more accurate because we don't influence each other, as well as don't go into autopilot on an estimate assuming someone else has it under control, or someone just deferring to the more Sr. Dev when the more Sr. Dev made a mistake.

I could see how this would also work well with interviews.

Re: Microsoft changed how it interviews software developers

#27
post #3

https://blog.usejournal.com/rethinking-how-we-interview-in-m... is the original post by a PM at Microsoft. It doesn't have any useful information about a pure technical interview for software engineering. >(Note: I started at Microsoft when we were still asking questions about why manhole covers were round, how many ping pong balls would fill a 747, and how to reverse a linked list. In 20 years here, I’ve yet to have…

There was a linked list interview question going around back then that went: In constant time, without allocating memory, given a pointer to the first element of a linked list, how can you tell if it eventually ends in a null or if it loops back on itself at any point? I actually ended up implementing the solution while tracking down a hang in a DCOM service I was working on...

Re: Microsoft changed how it interviews software developers

#28
post #3

https://blog.usejournal.com/rethinking-how-we-interview-in-m... is the original post by a PM at Microsoft. It doesn't have any useful information about a pure technical interview for software engineering. >(Note: I started at Microsoft when we were still asking questions about why manhole covers were round, how many ping pong balls would fill a 747, and how to reverse a linked list. In 20 years here, I’ve yet to have…

Isn't the round manhole covers just to make sure they can't fall in?

That’s exactly why they’ve given up the brain teaser questions - all it checks is whether somebody’s told you the answer before.

Re: Microsoft changed how it interviews software developers

#30
post #27
post #3

https://blog.usejournal.com/rethinking-how-we-interview-in-m... is the original post by a PM at Microsoft. It doesn't have any useful information about a pure technical interview for software engineering. >(Note: I started at Microsoft when we were still asking questions about why manhole covers were round, how many ping pong balls would fill a 747, and how to reverse a linked list. In 20 years here, I’ve yet to have…

There was a linked list interview question going around back then that went: In constant time, without allocating memory, given a pointer to the first element of a linked list, how can you tell if it eventually ends in a null or if it loops back on itself at any point? I actually ended up implementing the solution while tracking down a hang in a DCOM service I was working on...

In constant time? O(1)?
Post reply on HN