In Microsoft, there are a number of standard job titles.  The most important one is SDE – Software Development Engineer.  The rest can be considered the supporting cast (one requirement of being an SDE is to be so supremely confident that such a statement as the previous one can be made without actually laughing out loud while doing so).  The life of an SDE at Microsoft is as close to heaven as a computer geek can get.  Chocolate donuts for breakfast, a quick bite in the cafeteria for lunch, any fast food at all for dinner, and before, in between and after is glorious coding.  Of course, other things intervene occasionally – like annoying testers who keep insisting the code actually works, or program managers who insist the code actually be useful to someone (honestly, I don’t know where they find these people), or bosses who insist on “talking”, sometimes even in the form of meetings.  These are unfortunately necessary evils and an SDE will tolerate them and, on occasion, even indulge them from time to time.

There is a cloud on the horizon in many SDE’s careers however, and it’s called management.  At Microsoft, there aren’t a whole lot of real managers, they are mostly technical people who at one time or another did real work and then – probably due to chemical imbalances in the brain brought on by a diet of donuts, cafeteria and fast food – suddenly “stepped up” to the management plate.  It’s pretty insidious.  One day you’re a happy go lucky developer enjoying work to its legal limit and with masses of extremely marketable skills, and then your boss suggests that maybe you should take on a report or two.  Just junior people, you understand, to see how you like it.  Zap.  Six months later you have a team of 15 and you can’t write a line of code to save your life anymore (but you can create a mean Powerpoint presentation).

Microsoft does have an alternative career path for SDE’s (and the other, lesser, disciplines) which enables an IC (individual contributor) to remain an IC but continue to progress in that role.  While the ultimate destination of a manager is a VP, the equivalent IC role for an SDE is a DE (Distinguished Engineer).  DE is quite a bit harder to attain then VP, actually.  An intermediate IC role is usually some kind of architect.  

I know some people who have followed this path successfully, but it is a bit of a harder road to hoe.  In my case, I’ve taken the Bilbo Baggins approach (“There and Back Again”).  Prior to 1998, I had spent 13 years as an IC (not all at Microsoft, although I wish I had joined the company in ’85).  I then took on two reports.  Then six.  Then, after Exchange 2000 shipped, I took on a team of fifteen.  Then suddenly I had seventy developers working for me.  I even attained the exalted level of PUM (Product Unit Manager).  Those were the dark times.  I forgot how to code.  I forgot how to debug.  I pretty much forgot how to think.

I finally snapped out of it and ever since I’ve been striving once more for IC status.  I currently am down to a team of five, but I’m not likely to get much lower than that any time soon.  No matter.  I’m coding again and once more feel like a contributing member of the team rather than a roadblock on the way to success.  And those chocolate donuts are yummy.

- Jon Avner

Not applicable
Thank you Jon, you made Valorie laugh with that one (and me too of course :)).
Not applicable
That was a really enlightening read ... thanks!
Not applicable
An amusing (I hope its tongue in cheek) post about management roles at Microsoft on one of the Exchange blogs. Sadly I can see how much of it is true (from real life experience!)...
Not applicable
Great, interesting read. Thanks.