Why Working at Microsoft is Better than Google

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
A blogger has written an interesting entry about people that choose to work for Microsoft over Google. He has some solid observations on Google as a startup vs a mature company. The grammar is a bit poor but doesn’t make the blog unreadable.

The technology press makes it seem like people are ditching Google for hot startups like FriendFeed and Facebook. However the truth is has a [sic] more nuances than that. Now that Google is just another big software company, lots of people are comparing it to other big software companies like Microsoft and finding it lacking.
 
i'd prefer google over microsoft anyday. dude probably works for microsucks ;) :D
 
iv got a friend at work who turned down a job at google to come to work at MS (iv only been there a few months now), another who left intel and a few who have left and come back to MS. they all say ms is the better place to work.
so far i love this job more then any other i could imagine (besides pro basketball) and im just a lab rat.
but i can see that MS does over work people, my entire team works 50-70 hours a week and we have a fairly high burn out rate, but wow is it great to get to know these people.
 
I worked for microsoft also, in a lowly division I wont mention but god it was great they treat people really well over there granted I can only compare them nintendo maybe not a fair comparison but MS was great.
 
As an intern at Microsoft Research right now, I'm happy to report that it's a great place to work.
 

:rolleyes:^3

Writers weren't the best... Grammar was just terrible.

Makes good points- main thing that struck me was the whole thing: Google still acts like a startup.
I've seen firsthand, many times with many different businesses/organizations... Established companies that still run as a startup crash and burn down the road. Those that adapt and change maintain a high success rate.
I'd say either Google needs to do some adapting and changing, or they'll go the way of AltaVista.
 
I have a number of friends who work (and have worked) at Google and at MS. Depending on whom I ask, I get very both very positive and very negative opinions of the workplace environment.
 
I wouldn't mind working for either Microsoft or Google. :cool:

I was going to say the same thing :) Mainly because I've worked for big companies/corporations before and the bigger and better the company, the better they treated me. I'm not even saying anything about customer service or products here, I'm just talking about actually being employed by the company (Decent pay, benefits, having health insurance, hours).. But that's just in my own case, of course.
 
I was going to say the same thing :) Mainly because I've worked for big companies/corporations before and the bigger and better the company, the better they treated me. I'm not even saying anything about customer service or products here, I'm just talking about actually being employed by the company (Decent pay, benefits, having health insurance, hours).. But that's just in my own case, of course.

Oddly enough- that's what I've found too. Bigger the company- less you have a say in things of course- buy they pay better, better benefits, treat employees like people... etc.
 
I also worked for MS at one time (also in a lowly division i wont mention) pay was great, they treated people great, benefits were awesome
 
Obasanjo's summary only tells one side of the story. MSFT has a lot of problems of their own, and some of them are the same as the problems that the GOOG blogger has identified. MSFT culture is flawed, and isn't easy to change either, for example, even on a team level. The

The Google interviews might not be flawed, but they're very different than how other tech companies interview. Indeed, Google only cares about analytical skills and hard core problem solving. That the interviews feel like an Informatics Olympiad (or an ACM programming contest gauntlet) is right on; Google cares little for any practical experience, and doesn't do anything for personality match or team fit.

I think this process is a little crazy. It makes it pretty evident that Google is really a research company and a think tank, instead of a company that wants to provide products to customers. If what Google does becomes a great product, it seems that's a lucky side effect rather than any kind of goal. That enforces the rift these posters identified between the infastructure and the presentation. Those things should work together in concert, based on the requirements of the end users. Since there's no particular end users, the infrastructure ends up driving the presentation. It's hard to make that work, obviously.

On the other hand, if that's GOOG's intentional goal--to run a research house--then I think the interviews are actually a good idea to be structured the way they are. I don't think that people coming out of school realize that's what they're getting into, though.

Getting resource allocation is a huge problem at MSFT, too. It's painfully bad, in fact. And Microsoft has plenty of problems with career growth. When I left, I was at the point where I needed a divisional vice president's approval if I was to get a promotion. This is pretty insane: what does the VP know about me, and my work, specifically? He is busy (and should be very busy!) working on the overall direction for the 1000-person group he's running. The joke in the hallways was that it's easier to get a promotion by quitting and getting re-hired at a higher level than it was to get a promotion by actually earning it.

The engineering process at MSFT is too thick. From what I read, I feel the process is too thin at GOOG. MSFT is giant, and that "too thick" can vary significantly between groups, and I'm sure that's somewhat true at GOOG; particularly when comparing the groups that are geographically removed. Thing is, there's a place that's just right as far as process goes and it's remarkable that this sweet spot eludes two of the most successful software companies in today's world.

In the end, I think that far more people have left MSFT for GOOG than the other way 'round.
 
I always forget that I can't edit posts in this section, for whatever crazy reason that is. I meant to add that the choice is also up to the employee. Different people have different work styles, and prefer different things in their career paths. It's up to them to find what they need and make it work. It looks like some guys in this thread (and perhaps the blog posters, too) want to use those incompatibilities as a disgrace towards the company involved. Fact is, some people excel in some environments and some don't.
 
I've been a drone in the collective for um. A very long time. Being plugging into the unimatrix this long does things to your sense of time.

Anyway, it's a good place to work. MSFT has it's share of silliness and politics. It ain't all puppies and unicorns. But we know how to ship code. QA has a real voice in the product cycle and is seriously funded. That is not the norm for the industry.

The GOOG folks I talk with sound like they exist in some sort of alternate reality. They'll need to grow up to keep growing.
 
Today I plan to turn down a job at Microsoft. It's a contract position that pays less and is further away from home than another offer I got from the State of Washington. Also the Microsoft job is more on the support side, and the State job is more with engineering, something I've wanted to get into. I'd also say the State job is a more senior level position.

The benefits at MS would be better if I get hired as FTE eventually, but there's no guarantee that would happen, and State benefits aren't bad. Also, MS has a requirement for contractors that after you've been working for year, you have to take 100 days off unpaid. What the heck is that? Who can just take 100 days off? I have a house and a wife and a kid.

I'd also like to say that I do value how smart the people at Microsoft are. I really would like to work with such brilliance. However, I simply couldn't handle the commute nor the less $$$. I was actually a bit pissed that they wouldn't offer me more money. I had two other offers at substantially higher pay rates, and they would not offer more for this position. Oh well, their loss, not mine.
 
Is this article a joke?

Honestly, I almost feel like I'm reading a satire, here.

If this article is legit, than all this shows me is that Microsoft employees (and anti-Google folks) can't spell, can't form sentences, and constantly contradict themselves.

It's like a bunch of young teenagers are writing why they think their parents suck, but they don't have the writing skills to get their point across. Not to mention the oodles of spelling errors, grammatical errors, and all the slang such as "sux." Why would I ever want to accept advice from these people?

Here are a few gems taken from the article... please read them and actually analyze what they are saying. I'm not going to take the time to explain all the flaws below, but I hope you can see them yourself.

So why did I leave?

There are many things about Google that are not great, and merit improvement. There are plenty of silly politics, underperformance, inefficiencies and ineffectiveness, and things that are plain stupid. I will not write about these things here because they are immaterial. I did not leave because of them. No company has achieved the status of the perfect workplace, and no one ever will.

I left because Microsoft turned out to be the right place for me.

He lists things that are "not great" and then says he will not write about them, and then goes on to say it's irrelevant anyway because Microsoft is just a better fit for him. How insightful!


Google software business is divided between producing the "eye candy" - web properties that are designed to amuse and attract people - and the infrastructure required to support them. Some of the web properties are useful (some extremely useful - search), but most of them primarily help people waste time online (blogger, youtube, orkut, etc)

Here we have a blog explaining to me that blogs are a waste of time.

On the other hand, in my year at Google, I could not figure out what was it they were doing. The better manager that I had collected feedback from my peers and gave it to me. There was no other (observable by me) impact on Google. The worse manager that I had did not do even that, so for me as a manager he was a complete no-op. I asked quite a few other engineers from senior to senior staff levels that had spent far more time at Google than I, and they didn't know either. I am not making this up!

Perhaps the managers were doing things that were none of your business?

If I need to compare Microsoft and Google, I should tell it in short: Google sux!

Right...

Google interview were not professional. It was like Olympiad in Informatics. Google asked me only about algorithms and data structures, nothing about software technologies and software engineering. It was obvious that they do not care that I had 12 years software engineering experience. They just ignored this. The only think Google wants to know about their candidates are their algorithms and analytical thinking skills. Nothing about technology, nothing about engineering.

Sounds like someone is bitter about an interviewer wanting certain requirements to be met with higher importance over others.

Microsoft have really good interview process. People working in Microsoft are relly very smart and skillful. Their process is far ahead of Google. Their quality of development is far ahead of Google. Their management is ahead of Google and their recruitment is ahead of Google.

Wait, so Google employees aren't "relly very smart and skillful" like Microsofts?!


This is far as I'm going to go, because I don't have time to read the rest of the article right now, nevermind picking it apart.

All I can say is: lol
 
why do people continue to fall into the work 50-70 hours a week trap for a company you dont own.
I did that once and swore id never do it again.
 
Until you work for MS, and get caught in a mass lay off that includes your manager who had to let you know that you were getting laid off and that he was getting laid off too. December 22nd, Merry MF Xmas and too all a good night.
 
The benefits at MS would be better if I get hired as FTE eventually, but there's no guarantee that would happen, and State benefits aren't bad. Also, MS has a requirement for contractors that after you've been working for year, you have to take 100 days off unpaid. What the heck is that? Who can just take 100 days off? I have a house and a wife and a kid.
Contractors can: they leave Microsoft for 100 days. Perhaps you're assuming that they must stop working for 100 days altogether. This was caused by the class action lawsuit that the contractors and vendors filed against the company.

Are you contracting solo, or are you with a company?
 
I like being a contractor here at MS. the people are great, the pay is awesome and during the 100 day break ill get like $500 a week on UNEMPLOYMENT. after that i can come back and make my 60k/year or go find a differant/better job, although i cant think of what can be better then to get to test out new OS's on hardware that isnt out to the public yet.
BUT yes the hours are really long and it gets rough after a while
 
Back
Top