(Yes I stole this format from Jeremy J http://blogs.msdn.com/jeremyk, simply because it was a good start J)

I am a Escalation Engineer for SharePoint Portal Server and Windows SharePoint Services. I started my tenure with Microsoft in March of 2000.  As an Escalation Engineer (EE) we represent the last line of support for the most demanding of issues related to SharePoint Portal Server and Windows SharePoint Services. As an EE we are tasked with:

• Resolving the most the most technically and politically challenging customer issues
• Engaging and being a resource to the larger SharePoint PSS group.
• Researching, diagnosing, and writing code to further diagnose and resolve customer’s issues.
• Employing advanced tools and diagnostics to analyze source code.
• Making recommendations to the development team on improvements to product
• Isolating defects to the faulting line(s) of code.
• Writing tools to further analyze problem or improve the overall SharePoint experience.

All of these things within very compressed timeframes. What this really means is on a typical day the vast majority of my time is spent mentoring, debugging and researching issues I am currently involved in, and overall contributing to the success of those around me. By using knowledge of software design and programming in conjunction with general product knowledge, it allows people in our group to bridge the gap between the typical end to end support troubleshooting methodologies and the very focused, specific code level knowledge of a developer.

From a personal perspective, I have a wife and two children.  I spend most of my free time (what little there is J) with my family and composing music (check out http://www.indieopolis.net )