I've been a contractor at Microsoft numerous times, including now. There are many, many agencies that place contractors to work for or at Microsoft. Non-compete agreements abound, and Microsoft has its own policies to make sure the contracting game is played straight and contractors don't take the place of (permanent) FTE employees. Well, those policies are catching up to me all at once.
A couple months ago I took on a short writing assignment for Microsoft, through Volt Technical Servies. Since this assignment is short and I'm working directly for a Microsoft manager, not doing work remotely, this is an a-dash position. Oh, let me back up:
There are (basically) two types of contractors: a-dash and v-dash. The names refer to the letter before your e-mail alias at Microsoft when you're a contractor. In the past I've been mostly v-ditrag (I know, great alias), and now I'm a-ditrag@ms.com. The difference between the two is that a-dash contractors work on site, are managed by a Microsoft manager, and have to take a 100-day break after working for one year. Yup, one hundred full days. V-dashes are "vendors" and (usually) work off-site, being managed by the Vendor company managers, and don't (usually) interface with Microsoft directly. (Though they can.) Vendors don't have a limit to their assignment, and can stay on indefinitely. I was a vendor for almost three years a couple years back.
So now I'm an a-dash again. If I want to take on another contract after this is up, and it's another a-dash, but through another agency, I have to take 30 days off first. That's Volt's non-compete. If I find another contract and it's a v-dash, I have to take that 100-day break. That's Microsoft policy. Hmf!
So pretty much my only option/hope is to find another a-dash contract with Volt. Of course I have other leads and possibilities; Volt is not the only fish in the pond. A former manager wants to bring me on through another company as a vendor -- nope. I'll be available for that August 10.
But even if I find another Volt assignment, sooner or later I'll come up on that 100-day break thing. 100 days. That's a nice long vacation if I manage to save up money for it. Of course there's no guarantee if the position I left would still be there -- Microsoft would probably fill it with someone else. Or hire a v-dash.
Well, that's the bind I'm in. My assignment is winding down, and I'm looking for work again, and I'm hoping something *other* besides Microsoft pops up. There's gotta be other employers in town...!
Hey, thanks for tweeting a link to your blog. I didn't realize that you had a blog.
ReplyDeleteThanks for the a- and v- explanation. I see those in e-mail addresses and never figured it out (except v- for vendor guessing).
I've heard about the 100 days off for a-dash positions.... does this mean you can't work ANYWHERE for 100 days or just at another Microsoft position or a tech-related position?
ReplyDeleteI wish I would have read your post before I accepted my new a- assignment that is projected to last 3 months. I have done v- work for MSFT but never a- work. Living in the Redmond area and almost all my experience being at Microsoft it is about the only opportunities I have in town. I will be screwed if I have to take a 100 days off in 3 months.
ReplyDeleteBelated replies:
ReplyDeleteshimmy: You can work anywhere else you like during your 100-day break -- you just can't do another contract at Microsoft during that time.
Trev: I hear ya. Your best bet is to look for more a- positions until the year is up. Or find work at another company.
I was a v- at Expedia for a year until recently, and now they've switched me to an a-. (Expedia used to be part of Microsoft, so they must have inherited some policies.) I'm not sure why the switch, except now there's a clock ticking over my head -- curious to see what happens when the second year is up!