Skip to main content

Continued Education

A couple of weeks I got done reading “The Hard Thing about Hard Things” by Ben Horowitz.  I received the book as a gift at Box Developer Day ( and it turned out to be one of the best management books I’ve read in a while. You should definitely spend the $15 to buy the book yourself.  One of the key things that I took away from the book is the emphasis on training:

Almost everyone who builds a technology company knows that people are the most important asset. Properly run startups place a great deal of emphasis on recruiting and the interview process in order to build their talent base. Too often the investment in people stops there.
Horowitz, Ben (2014-03-04). The Hard Thing About Hard Things

Since reading this I started implementing a training program for my engineering team at DocuSign.  We picked out Tuesday mornings at 9AM to have a one-hour class where we can share some of the things that I have learned over the years.  The first class was on the concepts of agile project management.  I took for granted that people knew the concepts and philosophy of Agile and thought that books like “Agile Software Development with Scrum” by Ken Schwaber and Mike Beedle were read by everyone.  It turned out that the majority of the team has not read them.

That was a light bulb moment for me: there are a bunch of basics that I probably think are too basic to teach, but for some people its net new information or at least a refresher.  I encouraged the team to buy and expense the books that I mentioned, and got working on the second class – the basics of the Internet.   In this class I am going to cover the basics of the internet that I feel people never fully dive deep into such as cookies, error codes, DNS, SSL handshakes, HTTP request and response structures and such.

While attending NY Tech Day and meeting with some partners in New York I had a chance to get lunch with Ben Siscovick (@bsiscovick) and he recommended a blog post from that talks about progressions of Jeff Jordan through the management ranks at eBay.  The funny thing is that naturally I am following a very similar path and now that I am managing a team of close to 20 people I am turning more into a coach than a player.  I definitely recommend reading the full post here:

The next class is on Tuesday.  I will let you know how it goes!

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 …