(20##) 10 9 8 7 6 5 4 3 2 1 0 <
DesktopWeb FormText   womanhole coversSun, 16 May 2004 15:38:39 GMT # 

heading out to MS for an interview tomorrow. will let you know what they say about my blog :) if they make an offer and if i hire on, of course i would clean it up. the funny thing is that some people have acted impressed when i tell them i'm going to interview there in general. i dont understand this. is it company worship? have heard that they are selective ... but 50K+ is alot of people to have been selected. other rumors are they dont pay as well. maybe this has changed with the fall out of stock, not to mention they have picked up alot of big named people. need more info on the redmond area itself. the weather doesnt look great, but manageable. sort of eternal fall. a major positive is technology. some have called it a geek paradise. that depends what you are working on, and how tightly focused you are on that problem, but there is alot of cool stuff happening there. they are bringing me up for technology X. they had a couple positions in tech X that they showed me, but only 1 was compelling. although i have tech Y too, no positions in those were offered up. i'm assuming that represents the problems MS has getting across product lines? also, the people. would be extremely cool to get to meet and learn from the people there. now to the interview rumors. riddles do not help you understand how people think. all they do is make the person trying to solve the riddle feel like an idiot. you want to make the candidate look bad so that they will be humbled and want the company to hire them just to improve their riddle solving abilities. i've heard of people memorizing all the riddles that they could find on the internet to prepare ... stupid. my riddle strategy is to think way outside of the box. they are like: "how do you tell which light bulb was on?". me: "do i have super powers?". them: "no". me: "not even a genetic mutation?". the only person i've seen that needed advanced riddle solving skills was batman. he would constantly have to solve them to catch the riddler. also heard about having to whiteboard code for data structures. another skill i've never had to execute at a job. employers prefer that i actually type the code in and use the System.Collections namespace :) [until Generics] MS research is probably already working on whiteboards with intellisense. tech interviews have changed for me since starting the website. if they want to see how i think, then they can just read an article. typically document the mistakes i made and what i had to teach myself to get something to work. i really wish other people would write like this too. most articles just write the steps to get it to work, and omit what went wrong. i think the wrong paths that you took are just as important to understand so that others will not follow. it also provides a more complete understanding. else they might follow and turn what you thought was a wrong path into an alternate route. then there is code. if you want to see some, i have smack loads available for download. if those niceties are out of the way, then they can spend all the time trying to figure out if i know how to be professional :) anyways, i wont be able to tell you what actually happens, and the above are just my thoughts about the common rumors