Author |
Topic: Microsoft (Read 4965 times) |
|
Miguel
Newbie
Posts: 1
|
Actually riddles are a very small part of Microsoft interviews ... right now they are more focussing on cases. So you do think as a consultant in order to face them.
|
|
IP Logged |
|
|
|
puzzlecracker
Senior Riddler
Men have become the tools of their tools
Gender:
Posts: 319
|
|
Re: Microsoft
« Reply #1 on: Nov 6th, 2004, 9:43pm » |
Quote Modify
|
what "cases"? what is that?
|
|
IP Logged |
While we are postponing, life speeds by
|
|
|
John_Gaughan
Uberpuzzler
Behold, the power of cheese!
Gender:
Posts: 767
|
|
Re: Microsoft
« Reply #2 on: Nov 8th, 2004, 11:34am » |
Quote Modify
|
Use cases? UML?
|
|
IP Logged |
x = (0x2B | ~0x2B) x == the_question
|
|
|
Luis
Guest
|
Cases that depend on your background. As an example if you background is more focus on financial issues an usual case is define a pricing strategy for a business development software ...
|
|
IP Logged |
|
|
|
puzzlecracker
Senior Riddler
Men have become the tools of their tools
Gender:
Posts: 319
|
|
Re: Microsoft
« Reply #4 on: Nov 27th, 2004, 9:59pm » |
Quote Modify
|
what is the best and discriptive reference of UML -- need some tips for upcoming interview!
|
|
IP Logged |
While we are postponing, life speeds by
|
|
|
John_Gaughan
Uberpuzzler
Behold, the power of cheese!
Gender:
Posts: 767
|
|
Re: Microsoft
« Reply #5 on: Nov 28th, 2004, 1:27pm » |
Quote Modify
|
on Nov 27th, 2004, 9:59pm, puzzlecracker wrote:what is the best and discriptive reference of UML -- need some tips for upcoming interview! |
| You can download the standard at the UML Home Page. I do not know of any online resources because I learned it the old fashioned way, but I am sure Google could help.
|
|
IP Logged |
x = (0x2B | ~0x2B) x == the_question
|
|
|
Ganon
Guest
|
What type of position are you applying for? That's going to affect your questions dramatically. I just came back from an SDE internship interview and there were no riddles. About 30-50% of the time was spent talking about my background and what I'd done, the rest was solving coding problems. The focus of the coding problems was efficiency, the most important aspect obviously being the algorithm and data structures you choose (space and time efficiency, explain your choices and their consequences), but also the little details like excess calculations, pointer dereferences and branches. They were also very thorough about the correctness of code, ie. check all corner cases, make sure you address (or at least ask if you can make assumptions that make coding it easier and/or less cumbersome) and report all possible error conditions, malformed data, etc. Make sure you know your basics! If you have trouble writing a simple stack, you're in trouble..
|
|
IP Logged |
|
|
|
|