![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
First seven (work) days at the new job...
May. 15th, 2013 09:23 pmSo, there's good news and bad news.
The good news is that I'm working for SQL Support again. The old skill set is coming back quickly, and I feel really good.
The bad news: Microsoft is hoping to run a V- organization here. That is: they want to hire a company to provide services. Which means that I might end up being a star for a contracting firm, *not* for Microsoft, and did I mention that the contracting firm, like all contracting firms has awful benefits compared to full time employment? And I have a major concern about the medical plan, which is grandfathered in under the Affordable Care Act so it can still have annual limits on the amount they'll pay. The limits are relatively high, but I could see a medical crisis burning through it in a scary-short period of time.
Still, it's a chance to dig back into a job I loved doing and was damn good at. It's a steady paycheck, and I'll get by for now. What happens next will be whatever happens next.
The first few weeks are intended to be training. I'm re-reading a lot of old stuff and learning a bit that's new, which is always good. Then, we'll have to see what they want us to do. Typically, they start all engineers in "core" - basic installation and configuration. (You would not believe how complicated setup can be for a major product like SQL Server.) I wouldn't mind getting my feet wet again, but I hope to jump into the advanced team quickly. I'd like to be a great onsite resource for the core engineers at my location but work the advanced cases.
Life has been good in general, but I'm adjusting to new schedules and having the normal "ugh, I have to get up on time, and go to work!" adjustment period :-).
The good news is that I'm working for SQL Support again. The old skill set is coming back quickly, and I feel really good.
The bad news: Microsoft is hoping to run a V- organization here. That is: they want to hire a company to provide services. Which means that I might end up being a star for a contracting firm, *not* for Microsoft, and did I mention that the contracting firm, like all contracting firms has awful benefits compared to full time employment? And I have a major concern about the medical plan, which is grandfathered in under the Affordable Care Act so it can still have annual limits on the amount they'll pay. The limits are relatively high, but I could see a medical crisis burning through it in a scary-short period of time.
Still, it's a chance to dig back into a job I loved doing and was damn good at. It's a steady paycheck, and I'll get by for now. What happens next will be whatever happens next.
The first few weeks are intended to be training. I'm re-reading a lot of old stuff and learning a bit that's new, which is always good. Then, we'll have to see what they want us to do. Typically, they start all engineers in "core" - basic installation and configuration. (You would not believe how complicated setup can be for a major product like SQL Server.) I wouldn't mind getting my feet wet again, but I hope to jump into the advanced team quickly. I'd like to be a great onsite resource for the core engineers at my location but work the advanced cases.
Life has been good in general, but I'm adjusting to new schedules and having the normal "ugh, I have to get up on time, and go to work!" adjustment period :-).
