Skip to main content

Leaving Microsoft

Some of you might know this, some might not so here is the major announcement: I am leaving Microsoft.

First of all I want to tell you what I am going to be doing next. I am going to be an Engagement Manager working for DocuSign, Inc. You can check out more about the company on this website: www.docusign.com

What exactly will my job entail?
I will be managing projects which interface with DocuSign partners. It's going to be part professional services that DocuSign can bill for and part technical evangelism for other companies to use DocuSign technology.

I will also be travelling mostly to New York, San Francisco, Texas and North Carolina.

Why is this a step up for me when compared to my Microsoft gig?
First because it's a position where I can utilize my customer facing skills as well as my technology skills. Secondly because I will be working with Tom Gonser an entrepreneur and a person I respect for being able to put together businesses. Thirdly it's because both the base pay and the potential for me to make millions are greatly increased at DocuSign.

Microsoft is a great company for someone who wants to drill in deep into technology and it's also a very stable company where the benefits are great. I don't have a family and I rarely get really sick so I am effectively subsidizing benefits and "work/life" balance of 40 year old Microsofties. This is the time for me to get out, take risks and try to make a name for myself.

I do love the team I was working on at Microsoft. Windows Media Center is a great product and we all made it even better! Now it's time for me to kick butt and create something at DocuSign. The impact is going to be less global, but I am confident that with the team we have at one point in time it will be a global impact company. Online legally binding signatures are the WAY TO GO.
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!