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

Lessons from my 9 Year Journey with DocuSign

After over 9 years at DocuSign I am taking on a new challenge.  It’s been phenomenal seeing the
company grow from from 25 to 2000 employees.  DocuSign has changed the way the people do business and I am proud of it.  The next chapter is going to be heading up software development at Tempo Automation - a 25 person startup that is changing the way people produce electronics.  While I am extremely excited about the future, this is a good time to reflect on my journey and share the things that contributed to the success and things that I will do differently next time around.
1: Focus on the Customer One of the key things that contributed to the success of DocuSign and my personal career is relentless focus on the customer success.  From the very beginning our CTO has taken meetings, listened and prioritized requests and feedback coming from customers.  People who could not be bothered by customer requests didn’t last long.  As a result over time our engineering team retained and reward…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

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!