wu :: forums - Print Page


    
      
        wu :: forums
        (http://www.ocf.berkeley.edu/~wwu/cgi-bin/yabb/YaBB.cgi)
      

        riddles >> microsoft >> Microsoft
        
(Message started by: Miguel on Nov 2^nd, 2004, 7:41am)

Title: Microsoft
Post by Miguel on Nov 2^nd, 2004, 7:41am

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.
:o

Title: Re: Microsoft
Post by puzzlecracker on Nov 6^th, 2004, 9:43pm

what "cases"? what is that?

Title: Re: Microsoft
Post by John_Gaughan on Nov 8^th, 2004, 11:34am

Use cases? UML?

Title: Re: Microsoft
Post by Luis on Nov 8^th, 2004, 6:06pm

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 ... :o

Title: Re: Microsoft
Post by puzzlecracker on Nov 27^th, 2004, 9:59pm

what is the best and discriptive reference of UML -- need some tips for upcoming interview!

Title: Re: Microsoft
Post by John_Gaughan on Nov 28^th, 2004, 1:27pm

on 11/27/04 at 21:59:10, 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 (http://www.uml.org/). I do not know of any online resources because I learned it the old fashioned way, but I am sure Google could help.

Title: Re: Microsoft
Post by Ganon on Feb 11^th, 2005, 6:44pm

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..