Slashdot Mirror


Working at Microsoft, the Inside Scoop

bariswheel writes "Responding to the public interest, a long-time Apple and UNIX user/programmer, and a JPL/Caltech veteran, writes an insightful, articulate essay on the good, the bad, and the in-between experiences of working at Microsoft; concentrating on focus, unreality, company leadership, managers, source code, benefits and compensation, free soft drinks, work/life balance, Microsoft's not evil, and influence."

8 of 437 comments (clear)

  1. embedded in this message (not surprisingly) by yagu · · Score: 5, Insightful

    Aside from the obvious puff-piece nature of this article, it's a bit of a Trojan Horse. Under the auspices of a broad view of what life at Microsoft is like, the author gets to air out the PR spin that Microsoft's Not Evil in seven contrite paragraphs (the average number of paragraphs for each segment is closer to four).

    Also, assign credibility inversely proportional to the distance from the source. This guy works there, okay so the only way to describe "work at Microsoft" is to be there, but come on, are we going to get objective information?

    For the record, I once worked at Microsoft, and agree with his observations that the people there are like people elsewhere, and they're bright, and they're hard-working, etc. But, to equate individual ethical behavior somehow with a collective corporate ethos doesn't add up, the calculus is flawed. In my opinion, Microsoft as a corporation exhibits behavior that could be considered evil, certainly some/much of its behavior has been found in a court of law to be illegal.

    As for the some of the author's observations:

    At Microsoft, I've had access to the source code for Halo 1 & 2, Internet Explorer, MDAC, MSXML, the .NET Frameworks and CLR, SQL Server, SQLXML, Virtual PC, Visual Studio, Windows, the Xbox and Xbox Live, and probably several other projects that I've forgotten about. Does it get better than this?

    Yes.

    Given that Microsoft's been convicted of monopolistic practices, it may shock you when I say that Microsoft's upper management strikes me as very ethical. They talk about ethical behavior all the time...

    Thou doth protest too much.

    On the one hand, I'm making more money now than at any other point in my life, and I have all I need so perhaps I should be satisfied and leave it at that. Overall, I think Microsoft's compensation and benefits package are still above average for the industry, and well above average for the typical American worker.

    On the other hand, I and my coworkers have watched many benefits erode or disappear during the past five years. It's public knowledge that raises and annual bonuses have diminished, option grants have been replaced with stock awards, employee stock purchase plan benefits have decreased, and cafeteria and company store prices have increased. For new employees, vacation time has been cut from three weeks to two, and new parents have to take their parental leave within 6 months instead of 12. It's not a positive trend.

    Microsoft's ill-gotten gains were long the easy way to sustain the talent pipe-line. Market forces are catching up, and Microsoft is starting to have to compete on more equal footing with other companies to get talent in the door (no more, "you're guaranteed to be a millionaire in fiver years" promises). And, it's a little annoying to hear the Microsoft have-nots whine about this -- join the rest of the world folks.

    1. Re:embedded in this message (not surprisingly) by Procyon101 · · Score: 5, Informative

      I've worked inside and outside of Microsoft as a Software Engineer in the greater Seattle area since 1996. Microsoft has always been on-par or below industry standards for compensation for the area in the Senior Level Engineer arena. Except for the crazy stock back in the 90's it hasn't been a "get rich" kind of job ever.

      However, the work environment at Microsoft is so enjoyable, that personally, I would take a slightly lower wage in order to work there.

    2. Re:embedded in this message (not surprisingly) by archen · · Score: 5, Insightful

      Microsoft's ill-gotten gains were long the easy way to sustain the talent pipe-line.

      I wonder if it really has to do with sustaining the pipeline, as much being mired in corperate BS. Why is this company that makes money hand over fist with some of the best programming talent you can find putting out products that are hardly better than the last version?

      I've given this some thought and I'm starting to think that Microsoft has spread their uber-talent too far across the board. Now before you say "what else are they supposed to do?" consider 8-10 years ago during Win95/98. The company was throwing out significant upgrades left and right with REAL improvments - about the opposite we see today. At the time however MS had a real focus on some core products that could in some respects tie together.

      Nowdays Microsft is in everything from the Xbox to who knows how many software company aquisitions and trying to tie them together in a meaningful manor. It seems like in trying to use the MS engine (OS) to drag up new producs, they bit off more than they can chew and the engine (company) is being held back. MS can't sustain itself because the one hand literally cannot see the other. The company is too big, and lacks focus.

    3. Re:embedded in this message (not surprisingly) by IamTheRealMike · · Score: 5, Insightful
      I could have also sworn that at the time IE came out, the only other browsers were horrid and stagnant.

      Let's see. Internet Explorer was introduced at a time that Netscape, for better or worse, was adding features at a relentless speed. Why do you think they threw so much money at it?

      IIRC Netscape 2 added Java, frames, plugins, several new elements and one or two other things I forget. Netscape 3 added JavaScript, a HUGE change which is basically what makes web apps possible in the first place. They also added cookies (or was that v2) and SSL at some point, which made online shopping possible. Netscape 4 added DHTML and lots more CSS support. Netscape Navigator evolved so fast that the term "internet time" was coined to describe it. Then IE came out and cut the funding for competing browsers to a big fat zero. That is when things started to stagnate.

      To claim that IE somehow re-energised the market is a gross misunderstanding ... and even if IE was better back then (and by v6 I'd say it was better) this doesn't change the fact that it wasn't built to be competitive. It was built to destroy the competition and then halt the progress of the web. That's just bad, no two ways about it.

  2. I don't believe it. by TooMuchEspressoGuy · · Score: 5, Funny
    the good, the bad, and the in-between experiences of working at Microsoft; concentrating on focus, unreality, company leadership, managers, source code, benefits and compensation, free soft drinks, work/life balance, Microsoft's not evil, and influence.

    Sheyah. They all say that until the chairs start flying.

    --
    Many Bothans died to bring you this sig.
  3. You almost had me... by mlheur · · Score: 5, Funny

    Until I read the "Microsoft's not evil" part. This must be a hoax.

  4. Brainwashing by Mayhem178 · · Score: 5, Interesting

    My friends and I knew a guy at our college (Rose-Hulman Institute of Technology) that was hired on at Microsoft. Prior to leaving, he was always very open-minded about software usage, willing to try various options, be they proprietary or open source. After a while, he came back a changed man. He simply couldn't fathom how it was that we (as students) were using anything but Microsoft products, and would argument, sometimes vehemently, that we shouldn't be using *NIX or anything of that nature. It was truly scary.

    --

    "You will pay for your lack of vision..." - Emperor Palpatine to Ray Charles

  5. His experience not the norm, in my opinion by tokengeekgrrl · · Score: 5, Interesting

    I was a contractor at Microsoft from 1995-1997, working on MSN.com when it first came out, before Internet Explorer existed. As a result, I was apart of the permatemp class action lawsuit.

    My Microsoft experience was both good and bad.

    I got to work with some really talented and highly skilled people and learned a ton. The original lead engineer on Slate.com was a great guy and mentored me on his own, even though I wasn't a "blue badge" and not entitled to such perks. He had been recruited out of college back in the late 80s so he was a millionaire. He retired a few years later after his second marriage/wedding since he had already lost his first marriage to Microsoft and didn't wish to repeat the experience. He also told me that only people hired on at or promoted to a certain level got really lucrative stock options. From what I saw, he was right.

    I shared an office at one point with an amazing programmer, super smart and super nice guy. I remember him telling me that he had to learn to not care so much about his work because the business and marketing departments always rule in the end. He had a product he had worked on that he was really proud of, the users were really happy and he was excited about working on more features. He never got to because the product was outsourced and no more versions were going to be released, it was just to be supported as is and it didn't matter if the support was mediocre, just that it was cheaper. He said he found that a hard pill to swallow because he really believed in producing great products but he learned to accept it and was "watching the clock" meaning waiting his 5 years for his stock to vest. I met several fulltimers watching the clock and they seemed to me to be the some of the most talented people there.

    I met many people who worked very hard and others who were coasting, some arrogant and rude with no social skills whatsoever and some genuine, amicable and highly skilled, both fulltimers and contractors.

    I worked with great managers and incompetent ones. One manager was so bad that when the first round of contractor layoffs happened at one point, he cut a really skilled programmer who was vital to many projects in favor of keeping around the pretty, no experience or technical ability, woman that he was boinking, much to the dismay of the rest of us who had to workaround the incompetence of both of them. He was arrogant and had a mullet, a paradox beyond comprehension.

    I did not envy the people who became fulltimers during this time. Compared to contractor pay which included overtime, their pay was cut in half and their hours stayed the same or increased. One friend had to move somewhere cheaper due to the pay cut and carried 3 pagers at all times resulting in her moving closer to work as well. Her first year of employment was what was then called the "probation year" meaning she would not receive any stock options until after that first year. She and other people who went fulltime soon realized that the stock options were not going to make them millionaires but simply restore the compensation that had been cut when they took the salaried fulltime job. I knew several talented people who left before their options vested as a result.

    Some contractors-to-fulltimers I knew did ok with stock options meaning they were able to gain an extra 200-250k and after taxes bought themselves a nice house and/or car. But no one retired early.

    I knew several fulltimers who once they hit their 5 year mark, cashed out their stock and left the Microsoft with propriertary information on which they based a new company, hoping to get bought out by Microsoft and make more money. Some were sued, some weren't sued but didn't get bought out as they hoped, some did.

    Overall, it was an interesting place to be during the time I was there. That said, I'm inclined to think that the author's experience is not the norm given the high status at which he entered the company. If he had come in as an entry level contractor or programmer, his experience would be much different.

    - tokengeekgrrl