Slashdot Mirror


Internal Microsoft Email about Life at Google

An anonymous reader wrote in to give us "An interesting perspective on Google, from an internal email sent around Microsoft. Basically an interview that provides analysis about how Google compares to Microsoft from an employee perspective. Included are suggestions for what Microsoft might copy in order to stay competitive in the job market and criticisms of Google's "college kid" atmosphere."

11 of 410 comments (clear)

  1. From the perspective of someone on the outside... by TheRaven64 · · Score: 5, Interesting

    The biggest difference between Google and Microsoft is that Google turns research ideas into products. Microsoft spends something like five billion dollars on research a year, and pretty much any conference has a few interesting papers by Microsoft Research, but five years later you still won't see any products based on them. Google have a good track record of turning employees '20% time' into products. I think the difference here is that Microsoft have a research arm, and a products arm, and are not good at passing ideas between the two, while Google have people doing product work 80% of the time and research 20% of the time, so there is no disconnect.

    --
    I am TheRaven on Soylent News
  2. Why negative responses? by transmetal · · Score: 3, Interesting
    Can someone explain to this naive college student why that post is getting responses like

    Dude you shouldn't have published this, why do you even work for microsoft. you should quit right away.
    and

    I cannot believe you posted this. What is wrong with you? Makes me shudder to think what else your pathetic and bereft character would allow yourself to post. No house is perfect, we're all a little dysfunctional. Assuming you have a significant other or children, how would you feel if one of them decided to post something that highlighted your imperfections..? Wait, they wouldn't have to, your lack of integrity has been sufficiently demonstrated here.
    The entire post sounded reasonable, and was an interesting peek into the sort of corporate environments I may / may not be hired into in the next few years.
  3. Re:isn't this normal? by Aladrin · · Score: 5, Interesting

    With the exception of the 'almost always work at home' (doesn't happen a lot) and the hours (they vary according to individual's preference), sounds like here, too.

    I have no problem with keeping an eye on email every time I walk by my computer, and responding or fixing a problem or 2 here and there. It keeps Everyone (including my co-workers) happy, and generally doesn't cost me much. There's only been a few times when I had to put something fairly important (to me) away, and almost never that I had to stop something -very- important. (Usually someone else will step in and do it, instead.)

    One of my co-workers DOES spend a ton of time at home working, and I kick myself for lack of work ethic whenever I realize he's spent time working at home. I then realize that I already over-work anyhow, so no biggie.

    I think a lot of the people that complain about these working conditions have never actually experienced them. I've been in the cube farm of a major OEM and a major telecommunications company, and I've done retails in different stores, and I -far- prefer to work a little harder here and know the people around me are doing the same, for the good of ourselves and the company. It's a completely different feeling and I don't ever think, 'Man, if I have to deal with that lazy bugger again today...' Every other job I've had, I've had to do someone else's work because they were too lazy. I'm not saying that'll never happen here, but it hasn't so far (near 2 years now).

    My point: Don't judge a book by its cover. Just because 1 aspect of the job seems to suck doesn't mean there aren't 2 others that make up for it.

    --
    "If you make people think they're thinking, they'll love you; But if you really make them think, they'll hate you." - DM
  4. Re:From the perspective of someone on the outside. by Anonymous Coward · · Score: 3, Interesting

    five years later you still won't see any products based on them. You will see patents making sure no-one else can implement products based on similar ideas and perhaps threaten microsoft's monopoly - the WHOLE POINT of microsoft "research" is to deny market entry to anyone else.
    Now, you say "oh, but patents 'only' last 20 years". Well, I've got news for you: US diplomats have been pushing for 40 year patent terms abroad (asia, mainly). Once a country goes for that, then the USA will have a policy-laundered excuse to "harmonize" up to 40 years. Lather, rinse, repeat.

    The entire patent system should be abolished - if you want to reward "innovators" over and above the free market, find a way that doesn't deal a death of a thousand cuts to the freedom of hundreds of millions.

  5. Re:Fun with FUD by NickFortune · · Score: 3, Interesting

    hmmm... a while back there was speculation that Microsoft had despaired of ever having its press releases taken seriously, and instead had started to release company PR disguised as "leaks" about which it would then pretend to get vary annoyed.

    By doing so, instead of everyone going "ho-hum - more PR from Redmond" they'd take the leaked document very seriously. Then someone would pipe up with, "you know, if you think about it, Microsoft really don't sound too that bad in this", and everyone would take that seriously too. Because, you know, if it wasn't true, why would they be so angry?

    So I suppose it's possible that Microsoft employees aren't the intended audience here...

    --
    Don't let THEM immanentize the Eschaton!
  6. Tech stops by Spy+der+Mann · · Score: 5, Interesting
    This idea is just too awesome to leave it gathering dust in TFA.

    Google has the concept of "Tech Stops." Each floor of each building has one. They handle all of the IT stuff for employees in the building including troubleshooting networks, machines, etc. If you're having a problem you just walk into a Tech Stop and someone will fix it. They also have a variety of keyboards, mice, cables, etc. They're the ones who order equipment, etc. In many ways the Tech Stop does some of what our admins do. If your laptop breaks you bring it to a Tech Stop and they fix it or give you another one (they move your data for you). If one of your test machines is old and crusty you bring it to the Tech Stop and they give you a new one. They track everything by swiping your ID when you "check out" an item. If you need more equipment than your job description allows, your manager just needs to approve the action.

    The Tech Stop idea is genius because:

    1. You establish a relationship with your IT guy so technical problems stop being a big deal - you don't waste a couple of hours trying to fix something before calling IT to find out it wasn't your fault. You just drop in and say, "My network is down."

    2. Most IT problems are trivial when you're in a room together ("oh that Ethernet cable is in the wrong port")

    3. The model of repair or replace within an hour is incredible for productivity.

    4. It encourages a more flexible model for employees to define their OWN equipment needs. E.g. a "Developer" gets a workstation, a second workstation or a laptop, and a test machine. You're free to visit the Tech Stop to swap any of the machines for any of the others in those categories. For example, I could stop by and swap my second workstation for a laptop because I'm working remotely a lot more now. In the Tech Stop system, this takes 5 minutes to walk down and tell the Tech Stop guy. If a machine is available, I get it right away. Otherwise they order it and drop it off when it arrives. In our current set up, I have to go convince my manager that I need a laptop, he needs to budget for it because it's an additional machine, an admin has to order it, and in the end developers always end up with a growing collection of mostly useless "old" machines instead of a steady state of about 3 mostly up-to-date machines.
  7. The softies are hatin on this guy by grouchyman · · Score: 4, Interesting
    The comments on that blog are quite funny actually:

    What is wrong with you? Why would you publish this? This is internal only. Thanks for ruining it for the rest of us.

    this is horrible, man you ARE the reason microsoft is suffering!

    WHen I refreshed this page, it shows your e-mail and all. You better be careful too
    And the best one:

    Idiot, idiot, you should quit. You should be ashamed. Hopefully HR will figure out who the hell you are and can your ***.
    I wouldn't want to work at a company if these were my coworkers.
  8. Valley culture by Animats · · Score: 3, Interesting

    What makes the open plan office thing tolerable at Google is a very large number of modest-sized, well-equipped conference rooms.

    Google does go overboard on on-site services designed to keep people at work. I'm surprised they didn't go all the way and build dorms. Some large Japanese companies do that. But the real feel of Google is "overfunded dot-com". Yes, they're profitable. But the profitable part, search, was built some time ago. Most of the technical people in Mountain View are working on Google's money-losing sidelines, like desktop apps. Those are the labor-intensive parts of the business.

    Remember that Google is really an ad agency. That's how the money is made. Much of their newer hiring is sales reps for ads. The days when the ad sales just ran on autopilot are over; now Google has to push their ad products. In time, the ad agency people may take over. That will be an interesting culture change.

    Google's campus used to be SGI's campus. Most Google buildings are former SGI buildings. So if you've been in the Valley for a while, there's always that reminder that a company can go from #1 to zero in just a few years.

    Compare Intel in Santa Clara. Intel looks like Dilbertland. Intel is where cubicle culture began. Intel has built buildings from the ground up with single rooms covering about two acres, full of tiny cubicles. The cubicles are so small that only one chair will physically fit in them; they look like library study carrels. These aren't for call center employees; these are the people who design Intel CPUs.

  9. Re:I heard... Over at Google by Serapth · · Score: 4, Interesting

    You know, I have never once considered working at google. The free gourmet lunch thing... yeah, thats great. All of the perks and status attached, thats great too. Yet, at the end of the day, im really more interested in family time then I am work time. I work to live, not the other way around.

    That said, give me a Natalie Portman clone and im in! Who needs family time when you have Natalie Portman?!?!

  10. Re:isn't this normal? by j-pimp · · Score: 3, Interesting

    If workers are "interchangeable parts," as the article seems to suggest, then from the company's point of view, it's best if your work IS your life. So what if you burn out early, there's a class-load of graduates every year, plus stragglers or over-achievers at mid-year.

    In other words, you have to set your limits, because many employers will be happy to take all they can get from you, without thought to the future.

    Unfortunately, in an employment situation like we have now in the US, there is little-to-no disincentive for employers to put workers on the burnout track, as a matter of course.

    There seem to be plenty of places to go after google, or any other "burnout track" job. Although you are kinda like an abused foster kid at that point. It takes you a while to learn to behave in "normal" manner, at least that was my experience. Granted I didn't work at MS or Google, but a place that qualified as "not normal" in many regards. I think in the long run it was a beneficial experience, as it has made me better at what I do. I'll never be a manager, but I am happier that way.

    --
    --- Justin Dearing http://www.justaprogrammer.net/ We're just programmers.
  11. I agree, but there's still a downside by PCM2 · · Score: 3, Interesting

    I agree with what you're saying for the most part, but I, too, have worked in both types of environments. You've captured the downsides of the start-up type company pretty accurately. The downside of the other type of environment is a tendency toward under-achieving.

    You see it more in larger companies, and especially as companies get closer and closer to government ... i.e. big HMOs, university staffs ... any job where it's really difficult to get fired or laid off once you're in. These jobs attract people who have families, outside lives, want the healthcare and the work/life balance, precisely because they offer so much security.

    The problem is, once you have a preponderance of people with that mindset on staff, it becomes difficult to act like the smaller company. When your whole staff is seeking security in their employment, it makes sense that the organization naturally becomes more and more risk-averse. You stop taking chances. There's nobody to rock the boat.

    When that really starts to suck is when upper management starts looking at the numbers and they say, "Hey, it's a different market, your department isn't pulling its weight anymore. We need change." In a company full of ambitious over-achievers who have learned to be just a little bit afraid for their jobs, this situation is an opportunity. It's time for new ideas to surface, for the underdog to make his bid for success. New projects get launched. People move offices, start reporting to different bosses. You try stuff.

    In a staid, safe, secure work environment, however, this is how it happens: Upper management says "we need change," and the head of your department says, "Yes sir, will do, sir" ... and the buck stops there. Your manager diddles the numbers a bit. Everybody's told they need to "work a little harder." And that's it.

    And maybe you were at the same meeting that the head of your department was, and maybe you heard that upper management guy saying "we need change," and now you're just sitting there. Twiddling your thumbs. Waiting for the axe to fall. And you go to your boss and you say, "Shouldn't we really be doing this or that?" But he's thinking about his kid's braces and his car payment and his wife's last biopsy, and he doesn't want to rock the boat. So he sends you back to your desk. To wait.

    Bitter much? Nah, not me.

    --
    Breakfast served all day!