News

Microsoft Mum on Rumored Layoffs

Bloggers and analysts on Monday poured cold water on rumors that Microsoft plans to lay off a substantial number of its employees. The rumors, which surfaced in late December, suggested that the company might shave off as much as 17 percent of its 95,000-plus workforce.

Two blogs that started the rumors -- Fudzilla and Mini-Microsoft -- have both backed off from their first reports, which suggested that up to 15,000 Microsoft employees could be cut.

The widespread speculation about workforce cuts at Microsoft may have been fueled, in part, by a remark CEO Steve Ballmer made at a Microsoft shareholder meeting in November. Ballmer told shareholders that Microsoft will look to reduce costs in 2009 by "utilizing its resources more and reducing the head count…."

Ballmer is scheduled to address the International Consumer Electronics Show 2009 in Las Vegas as the keynote speaker on January 7.

To date, none of the sources speculating about the personnel reductions have been identified, and Microsoft has issued no formal statement. A CNBC story quoted an unnamed "Microsoft source" confirming that the company is considering employee cutbacks. However, that source described the rumors of broad reductions as "grossly exaggerated."

Still, economic challenges in the new year can be expected for many companies, even for Microsoft.

"The current economy is certainly cutting into the IT sector. However, we see an across-the-board cut by Microsoft as very unlikely," said Matt Rosoff, lead analyst for Directions on Microsoft in a telephone interview. "That said, the possibility of some sort of reorganization with some business units being reassigned, or eliminated, is likely given the economic challenges and Microsoft's business structure."

Some reports have speculated that contract workers would be the most vulnerable to job cuts. The Seattle Times reported last week that contracts with some outsource firms have been "abruptly cut short."

Rosoff confirmed that speculation, saying that Directions on Microsoft had "anecdotally heard" that many third-party contractors have had contracts "diminished in size."

"Microsoft has done very well with more than $60 billion in revenues this past year," Rosoff said. "It is not the kind of company that is going to make across-the-board cuts."

Microsoft has grown from approximately 17,000 workers in 1995 to more than 95,000 in 2008, according to company employment statistics. Microsoft hired more than 1,000 employees in October and then slipped to only 380 new hires in November, according to the Seattle Tech Report's Microsoft blog. Employment numbers for December are scheduled to be released this week.

Microsoft is scheduled to announce its second-quarter earnings on January 22.

About the Author

Herb Torrens is an award-winning freelance writer based in Southern California. He managed the MCSP program for a leading computer telephony integrator for more than five years and has worked with numerous solution providers including HP/Compaq, Nortel, and Microsoft in all forms of media.

comments powered by Disqus

Featured

  • VS Code 1.125 Adds Copilot Spend Meter After Billing Shock

    VS Code 1.125 adds in-editor visibility into additional Copilot budget usage as GitHub's AI-credit billing model continues to draw developer scrutiny.

  • TypeScript 7.0 RC Moves Microsoft's Go Rewrite Into the Mainline Compiler

    Microsoft's Go-based TypeScript rewrite has reached Release Candidate status, moving from a separate native-preview package into the regular TypeScript npm package while leaving some ecosystem-facing API work for TypeScript 7.1 or later.

  • Microsoft Highlights Visual Studio Live! Event Lineup and Longtime Developer Community Role

    A Microsoft MVP Blog post on Visual Studio Live!'s longevity arrives as the 2026 conference series continues with upcoming stops at Microsoft HQ, San Diego and Orlando.

  • Using Local AI to Cut Copilot Usage-Based Billing Shock

    After being gobsmacked by the new billing plan using almost all my monthly credits in one or two days, I tried pushing some Copilot-style coding work onto local models in VS Code. What I found was less "free AI" and more "pick your pain": cloud charges on one side, heavy local resource use and long waits on the other.

Subscribe on YouTube