New Job – Back at Microsoft

I’ve had a fair number of jobs in my career, shit pumper, consultant, engineer, writer, manager, lead, and then some. I’ve had jobs that were ok, jobs that sucked, jobs I loved, and some that were just jobs. I had a few jobs where the only thing that kept me going was an income counter at the bottom of my screen telling me how much money I made every second. My current job I rate up there as pretty much awesomest job ever for me. In all of my past jobs the things I have loved the most have been, fixing things (troubleshooting) and Exchange (Email). My current gig is filling with pretty much nothing but trouble shooting Exchange in a big room with lots of other Engineers


I am back working at Microsoft again, supporting Microsoft’s Hosted Exchange, and Corporate email ( Millions and Millions of Mailboxes scattered in datacenters all over the world). I work in a room filled with Exchange and BES engineers who work on the most complex Exchange cases. My job title is tech lead. What the title means is, I am responsible for making sure cases are addressed correctly from a technical point of view, training and making the guys on my shift smarter, working the most complicated / politically charged cases in the room to accelerate resolution, I act as an escalation point for all cases in the room, and as the gateway to escalate out of the room and to the product group as needed. Wait, it gets better, below are a few things that make this job even belter–

  • No one in my room is allowed to talk to an end user, or the customer’s admins. If we have to do that we engage another team. – That includes me.
  • I don’t really have to work issues personally. When things are broken I work through someone else’s hands. I have them do the work while I sit and watch and think about what to do next. I can jump in work on servers if I NEED too – but most of the time I am working through someone else’s hands.
  • If I don’t want to care about it, I don’t have to care at all about root cause. We have another team for that, and my mandate is to restore service as quickly as possible.
  • When I don’t know the issue I have options to escalate directly to the engineers who write the code for the product.
  • No utilization numbers to care about at all. I don’t have to close x cases a day, be on the phone X hours a day, answers X emails – you get the idea. No numbers to pay attention to at all.

It’s good to be back at Microsoft in a dedicated trouble shooting job. For now I am happy with this job.

Related Posts with Thumbnails

About Kevinm