I posted earlier about interviewing with Microsoft Consulting Services; I didn’t follow up with the results of the interview because, well…let’s just say things didn’t work out, which is ok because from what I hear MCS is very demanding when it comes to employee’s schedule’s…so no worries (not that I would mind that, but they travel a lot). That being said, I was informed earlier today that I will start the interview process with another MS group, Product Support Services (PSS); if you’ve ever had to call Microsoft for a support issue (everything from “can’t connect to the internet” type issues all the way up to “my server has smoke coming out of it” issues…they handle it all), and more specifically Developer Support (so that would be PSS/DS for anyone craving to crowd their head with more acronyms), and even more specifically, the COM/COM+ group within DS. This group handles everything related to COM/COM+/DCOM/OLE/DTC/Web Services…the also own the EnterpriseServices namespace in .Net, so pretty much everything related to distributed application services except for remoting…they have their own group.
These guys stay pretty busy debugging customer’s code, analyzing crash dumps, and working with the product groups to fix bugs as they relate to the above mentioned MS technologies. Anyone even somewhat familiar with Windows knows that COM/OLE are pretty much the underpinning mechanisms that make it “just work” (well most of the time, otherwise this group wouldn’t have a gig to show up for every day). Thankfully a good friend of mine who was in the same group as I was during my first tour at MS is in now in this group, and will probably be the one interviewing me (it’s a small group), so I already have a leg up on the competition.
I am not a COM expert; I haven’t worked directly with COM since my early days as a developer, so of course the first thing I did was order Don Box’s “Essential COM” book. I do consider myself a pretty robust debugger, but just to make sure I also ordered MSPress’s “Debugging Applications for Microsoft .NET and Microsoft Windows” which I’ve skimmed before, but didn’t really delve into much. I highly recommend it though
So, back into the fire I go…man, I must be a glutton for punishment. Quite simply put, this could be a pretty amazing opportunity, and I’m sure I’d learn a ton of new stuff. That’s what it’s all about right? I’m stoked!!!
Sidenote: MS PSS is one of the greatest gigs I’ve ever had, even though the position I held previously wasn’t really that glamorous. The individual “clusters” (as they are called internally) work pretty closely with the actual product groups out in Redmond to get bugs fixed/features implemented/etc as they work pretty closely with MS customer’s (90% of them are corporate as you might imagine)…and in DS some of the support engineers are former MS product developers themselves. PSS is big…I think at last count there were close to 2,000 individuals in PSS, though PSS/DS is smaller than than PSS/platforms (think Windows, Exchange, and pretty much every server except for BizTalk/SQL Server) and PSS/apps (Office, etc) combined. DS is also much more laid back than platforms as usually the issues aren’t production critical…aside from the occasional SQL Server down issue. Platforms gets to deal with all the “My domain is offline” and “I have 20,000 emails in my Exchange queue that aren’t being delivered” stuff.
Apps gets to deal with mostly end user issues, typical idiot stuff. DS gets to deal with people like us (hey, we’re a pretty laid back bunch right?), developers trying to do their jobs and we run into a snag somewhere and need to call in for reinforcements…the cool stuff. Another interesting thing about PSS is that while Plat/Apps may have more employees than DS, there are actually many more clusters within DS, several dozen, and each group owns a specific subset of MS developer technologies and are highly highly trained on that area. For example, SQL Server actually has 3 PSS clusters; one for installation/production issues/etc, one for the TSQL language itself (and anything performance related to queries, DTS, etc), and one group just for replication/linked servers/etc. Interestingly enough, the SQL group doesn’t own DTC; the group I’m interviewing with does…which actually makes sense. Of course, each language has it’s own group and is further subdivided based on namespaces (for .Net languages), or in the case of C++, what you’re actually doing with it (MFC/ATL/COM (of course)/…basically what libraries you’re working with…the most hardcore group in PSS/DS is the base services group…they own the core Windows’ kernel dll’s, and most of the folks in that group were former developers on the Windows team so they know the kernel pretty well to say the least…they probably dream in binary).
It’s actually pretty effecient…the teams are small, and since everyone is so highly trained in their area, interoperations between the clusters is seamless. Most issues require more than one cluster to get it resolved, and it’s all done behind the scenes. Ok, I’ve rambled enough…updates as they come in. Cheers.



No comments yet