Advanced

Microsoft Contractors Face New Work Limits

Posted by Collin_O on · 8 comments
eweek; By Pedro Hernandez
Mail this story
Print this story

The pitfalls of working on closed source projects for contract developers...

Days after Microsoft announced that it was kicking off a massive round of layoffs, the company has issued new policies pertaining to contract workers.

The changes will limit the time "external staff" in the United States can access Microsoft buildings and internal networks to 18 months before a mandatory six-month break kicks in. In short, contract workers must take a half-year break for each year and a half spent at Microsoft. The action is being taken to protect "Microsoft IP and confidential information," according to the company.

Microsoft describes external staff as "individuals performing services for Microsoft on a non-permanent basis. Examples include consultants, temporary contract workers, vendor workers, freelancers, independent professionals and contractors, staff augmentation and business guests." The company does not publish data on the number of contractors that it uses.

In a July 18 memo to outside staffing firms from the Redmond, Wash.-based software giant's Global Procurement Group, the company revealed how the new policies can be a boon for some contract workers and a loss for others.

The Seattle Times reported that "v-dash" workers, those contracted through vendors, "will now have to take a six-month break if their work requires access to Microsoft buildings or its corporate network." Previously, v-dash workers were permitted to work indefinitely and could assume "another v-dash position immediately after their last project ends."

A-dash workers, on the other hand, can eke out a few extra months under the new rules, but will have to wait longer to pick up contract work from Microsoft. While their stints can now stretch to 18 months from the previous one-year limit, the new six-month break period is nearly double the 100-day restriction that was previously enforced.

Although the new policy only applies to the United States, it may have implications for some contract workers abroad. In an accompanying FAQ, Microsoft explained that "if the resources sit outside of the U.S., but is assigned to a U.S. company code, the policy will apply."

The fate of some external contractors, those who can perform their jobs without setting foot at the company's facilities or logging onto its network, will remain unchanged. "External staff without access to Microsoft corporate network or buildings are not subject to the new policy," said the memo.

The move comes just days after the software and cloud services provider announced that it was eliminating 18,000 positions within the company, roughly 14 percent of its 127,000 employees. The Nokia hardware division, which Microsoft acquired for $7 billion, was particularly hard hit with the loss of 12,500 employees.

In an effort to restore efficiency at the 39-year-old tech titan, the layoffs also spell the end of the Lumia X line of Android smartphones. Instead, CEO Satya Nadella said in a statement that "select Nokia X product designs [will] become Lumia products running Windows." The company's other hardware units, namely Surface, Xbox and Perceptive Pixel, will be subject to "limited change," assured former Nokia CEO Stephen Elop, who now serves as executive vice president of Microsoft's Devices Group.

Full Story

  Nav
» Read more about: Groups: Developer, Intellectual Property, Microsoft

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

  Related stories
» More like this

Comments (8)

Quoting: contract workers must take a half-year break for each year and a half spent at Microsoft. The action is being taken to protect "Microsoft IP and confidential information," according to the company.


Liar pants on fire-- it's the same old perma-temp dodge, so they don't have to hire them.
Well, at least the new CEO has his priorities in place,... $$$,... and LEAN to boot... It looks like ol' MS is gearing up for the long fight (to stay alive). Good for them. They'll need all the strategies they can come up with.
"To boot".... followed by "to crash."

Does Apple mistreat contract workers like this? How about Oracle? Cisco? Google? Yahoo?

Redmond is already hashed into rubbish. Time to take M$ to the tip.
> Liar pants on fire-- it's the same old perma-temp dodge, so they don't have to hire them.

I expect most of these contract workers are going to be on H-1B visas, and will simply go back home.
> Does Apple mistreat contract workers like this? How about Oracle? Cisco? Google? Yahoo?

Of course they do! If they can. It's precisely the reason why contract workers exist. It's a method to control fluctuating labor requirements all companies face. It's jes that contract workers --"temps"-- are typically somewhat educated and skilled, as opposed to illegal labor, which is merely grunt labor.

I was more often than not, a temp in the 25 yrs I worked in hi-tech and in Silicon Valley (SV). The abuses were many. The stories I could tell. OTOH, temps typically make more $$$$ while receiving almost zero bennies. Some workers actually prefer being employed as temps. But, the company usually has little to say. It's state and federal laws which determines how temps are treated, not the individual companies. So, how Gobble vs how Crapple treats a temp is a non-issue. They all draft from the same pool and are all governed by the same laws. If anyone is going to screw over a temp, it's usually the the temp company doing the reaming.

Bottom line, they cost the corporations less than perm hires and any changes in the temp laws must come from the govt. OTOH, that doesn't mean the companies, usually as a whole, can't influence the pols that make the laws. I've experienced that song and dance, too.
When they tell you to go away after 18 months and take a six-month break, you're not a temp. You're someone who should be on payroll, and they're just playing games. The tech industry has all but gutted state labor laws in Oregon and Washington, and done away with overtime pay, and weakened temp worker classifications into uselessness. Most temp workers are not H-1B workers-- they're locals.
OK, I'm rather ignorant on this topic -- but is it possible that this will actually turn out to be counter-productive?

Doesn't this make these jobs less attractive to prospective contract employees, and reduce their motivation to work hard and "keep their noses clean"/"keep their heads down" during their employment, as they'll definitely, absolutely be out of a job regardless, when the current contract expires... etc?
> When they tell you to go away after 18 months and take a six-month break, you're not a temp. You're someone who should be on payroll,

Jes "18 mos"!? I've been a temp for 2 yrs for a private corp and 3 yrs for a govt lab. CA finally sed 12 mos max, but if the corp doesn't tell you and you don't know..... Even after the change of state law, many temps were employed longer than 12 mos simply because the worker was not savvy.

Ignorance of the law is the corp's and the temp agency's friend. I once discovered I was being screwed outta $0.37 per/hr. Six hundred dollars had accrued before I learned the facts. The govt lab hiring dept sed, "not our problem". The Federal Labor Relations Board sed, "It's jes an administrative infraction". IOW, zero law allowing me to recoup the missing $$. I tried to tell other temps. "I don't want to know" was the universal response.

I don't know how bad it's become in WA and OR, but I can imagine, What you describe is not only SOP, but not even remotely surprising. ;)

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post