As a Final year CS student, I'm not looking forward to these sort of interviews!
At Microsoft - Page 3
Blogs > Triscuit |
Jono7272
United Kingdom6330 Posts
As a Final year CS student, I'm not looking forward to these sort of interviews! | ||
LightTemplar
Ireland481 Posts
| ||
theBizness
United States696 Posts
| ||
mizU
United States12125 Posts
| ||
WIllBIll
590 Posts
| ||
NeThZOR
South Africa7387 Posts
| ||
Mavkar
Germany592 Posts
Best of luck to you and don't be evil. | ||
Ciryandor
United States3735 Posts
| ||
ionize
Ireland399 Posts
| ||
Pipeline
Sweden1673 Posts
| ||
Cambium
United States16368 Posts
For me, four out of the five technical questions (my final one wasn't super technical, it was more of a complicated brain teaser) involved linked lists. And I really dreaded linked lists at the end of my interviews. And yea, you aren't supposed to share this information lol... I'd take it off otherwise they might rescind your offer. | ||
pwncakery
Canada131 Posts
For the nlogn I'm pretty sure we just went over one of those for a simulations class...map the tree onto an array (heap) then sort from there? The code escapes me too offhand lol. Must be hard to do under pressure like that. Congrats on the offer! | ||
FakeDouble
Australia676 Posts
| ||
Cambium
United States16368 Posts
On November 10 2011 20:25 ionize wrote: Interesting read, but I got one question: Why do they have so many interviews at Microsoft? Because you can't tell if a candidate is good with one or two interviews. Most respectable software firms (actually, any firm in general) will require numerous interview cycles, it may be even more if the candidate is a lateral hire (versus new grad). Some firms are very strict in that if one interviewer says "no", then you are done. Most firms are more reasonable. The reason for a tight interview procedure is because getting rid of someone is extremely costly. | ||
CatNzHat
United States1599 Posts
Gratz on the success as well, any chance you can tell us what their offer is? @D4Lorg, Yep, basically just map it out to a linear heap and then sort from there. For bonus points write it in assembly! | ||
CutieBK
Sweden227 Posts
I've always wondered what the process of getting hired by one of those mega-companies was like Edit: And congratulations! Well done! | ||
dontgonearthecastle
Poland21 Posts
| ||
Osmoses
Sweden5302 Posts
| ||
thedz
United States217 Posts
On November 10 2011 20:40 Cambium wrote: Because you can't tell if a candidate is good with one or two interviews. Most respectable software firms (actually, any firm in general) will require numerous interview cycles, it may be even more if the candidate is a lateral hire (versus new grad). Some firms are very strict in that if one interviewer says "no", then you are done. Most firms are more reasonable. The reason for a tight interview procedure is because getting rid of someone is extremely costly. It's not just at Microsoft. When I interviewed at Apple (though I didn't end up taking their offer), it was a full day of interviews similar to the set described in the OP. The "big three" (Apple, Google, Microsoft) and also Facebook all do multiple interviews over the course of a day. And it's not just the cost of firing a new hire. A bad hire will also negatively influence the team, bringing the entire project down in quality. Most individual interviewer during the day will usually also try to see if there's a cultural fit as well. | ||
Roggay
Switzerland6320 Posts
| ||
| ||