The theory behind the technical questions is not whether you can reverse a linked list, but rather:
-Do you know basic computer science concepts
-How are your problem-solving skills
-Can you move beyond "obvious, yet flawed" answers
-Do you exhibit passion (passion to get to the right answer, enjoyment of problem solving, etc)
-Can you present and justify solutions
-Integrity (If you've seen the problem before, tell the interviewer, don't 'fake solve' it!)
-Are you thorough (probing to understand problem, handling error cases, boundary cases, etc)
-Can you communicate/collaborate with the interviewer
Anyway, that's the theory. In reality, many interviewers use whiteboard questions as a crutch to an easy interview loop and don't really understand why they're asking what they're asking.
My biggest piece of advice is to remember the technical interview isn't just (or even mostly) about the technical aspect. Communicate constantly, verbalize your thoughts, ask questions, show passion. I've hired plenty of people who have done not-so-well at the technical portion, and I've given a 'no hire' to plenty who have aced the technical portion.
Same here, I've tried it twice and both times gave in about day 3. It's not that I couldn't physically stay awake, just that my resolve and willpower trended towards zero.
Belltown actually is kinda sketchy at night these days. South Lake Union has a much safer, 'yuppie' feel to it. For something a bit quieter you might consider east of the lake. There are also some nice neighborhoods (not sure of prices) closer to the university that would still be a nice short commute.
I live just south of Lake Union (2200 Westlake building). There are several condos around that have some rentals available. They'll be a much higher quality building than an apartment of similar price.
If you want more of a social thing, then an apartment may be better. There's a building that's pretty popular called Rollin Street Flats that has a good scene.
Stuff's expensive around here, especially with Amazon moving in. Unfortunately you're not going to find a great place for under $2k.
Belltown is also pretty close and has good night life. Easy bicycling distance. There's a relatively decent complex called 2900 on First that should be in your price range.
Craigslist is a good place to look if you decide to go the condo rental route.
Most of us may not agree with his philosophy, and have questions about his basic technical and leadership competencies. But right or wrong, he's being very transparent about their hiring and development philosophies.
This is a good thing. It helps his company attract the kind of person that will work well in that environment, and gives clear warning to the rest of us that this is not the place for us, and that we are better of not wasting our time seeking a career there.
This is decent basic advice for generic advice on landing a job at any number of tech companies.
His advice on how to answer questions, however, fell short. Just saying "I don't know" to questions is a sure-fire way to terminate the interview loop early. Interviewers at Microsoft aren't primarily looking for knowledge, but rather problem-solving skills and the ability to think about issues. If you don't know something, it's fine to explain that you don't know, but you had better follow up with a discussion on what you think and why you think it.
Leverage existing equity as collateral and purchase one or several investment properties (very carefully of course). There are some incredible deals to be found right now.
Replace the soft word "warez" in your description above with "stolen property" and it might help make the issue less morally ambiguous. It's theft, plain and simple.
Why would you want to work for them? If they believe this is ok, it's only a matter of time before you're screwed over too. If it is an oversight on their part, you breaching the subject is much better than them eventually realizing they have an employee who is fine with dishonest business practices.
You should be able to broach the subject in a professional way; if you're dismissed because of it you have grounds for a lawsuit.
Incidentally Microsoft (and probably other companies) has a great program called BizSpark to help startups get over initially prohibitive software costs. You might want to bring this up to the founders as a solution for them to make sure they're legal.
Anyway, that's the theory. In reality, many interviewers use whiteboard questions as a crutch to an easy interview loop and don't really understand why they're asking what they're asking.
My biggest piece of advice is to remember the technical interview isn't just (or even mostly) about the technical aspect. Communicate constantly, verbalize your thoughts, ask questions, show passion. I've hired plenty of people who have done not-so-well at the technical portion, and I've given a 'no hire' to plenty who have aced the technical portion.