Skip to main content

Why work at Microsoft

I spent a total of 5 years at Microsoft.  2 years as a contractor and 3 years as a full time Engineering Lead.  My time at Microsoft had its ups and downs but overall it was a very valuable experience.  I am tough on Microsoft, but that’s primarily because I think they can do a lot better.  I want to devote a few paragraphs to why one would actually work at Microsoft, because even with all its flaws Microsoft can contribute a lot to someone’s growth.

First thing to remember – Microsoft is a very engineering driven company.  It is the best place to learn how to be a great developer, tester or program manager.  Most of the groups at Microsoft know exactly how those roles play together and how to train and execute in those disciplines.  Microsoft has had some issues delivering breakthrough products lately, but it’s rarely an engineering issue.  Windows 7, Windows Phone 7, Xbox, Office, Windows Servers and Visual Studio are stable, extensible, responsive and are a pleasure to use.  In the interest of full disclosure I do use an iPhone and a Macbook Pro, but it’s mostly a hardware issue.

When you join Microsoft as an engineer they will train you how to write secure code, how to test it, how to grow in your role and invest in yourself.

Being at Microsoft as an engineering manager or a lead is also a great experience.  Microsoft will invest into training you how to hire and terminate, how to deal with various personalities and how to drive your team to excel.

The time I did spend at Microsoft I shipped products, did bug triage and gained intuition about how to manage a release.

There are plenty of reasons not to be at Microsoft and that’s why I left 5  years ago to join DocuSign, however that’s a whole different blog post.  I do consider my time on the Windows Team as a Masters in Software Engineering (as opposed to Masters in Computer Science).  The curriculum consists of taking classes, doing a lot of homework, working hard, coming into the lab on the weekends, and passing your finals by shipping software.
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!

SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Ego in Your Decision Making

Oxford dictionary defines Ego as: “a person's sense of self-esteem or self-importance”. It says that it is “responsible for reality testing and a sense of personal identity.” For a lot of us techies those were really important functions that probably served us very well early in our career.  We had to be assertive, we had to choose a coding style guide, pick our frameworks and “be decisive”.  However when it comes to engineering management the same things that used to help might be turning into a liability.

When my job changed from writing code to creating an environment where the best code is written - it took me a while to understand how my ego was holding me back.  I kept applying the old tricks - defining the architecture, the final design and task priority.  What ended up happening is those things led me to turn off a lot of the best and brightest people on my early teams.

I remember the feelings of being aggravated when I had to go over an explain my decisions and get buy …