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

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!

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …