Skip to main content

So you want to be the boss?


Nowadays a lot of people feel like they need to move up in order to claim “growth” in their professional life.  Once they master something they think that the next natural thing is having a few folks “underneath them”

I think at the core of this is a failure in American corporate culture. The fact that you are a director actually does not mean that you are smarter than all of the people who report to you.  In the position of a director you are concentrating on different things.

If you are a good engineer you should actually continue being an engineer because if you become a director you are probably not going to engineer anything.  If you are a director that still writes code you are probably missing some other important responsibilities.

What are the issues you are going to deal with as a director?
1) recruiting and talent retention
2) defending your team from external interruptions
3) being an external and internal champion for your project
4) dealing with under performers
5) stroking peoples egos
6) conflict resolution
I am not suggesting that as a director you should be completely oblivious to the details of how things are done, but most of your time is actually spent selling and using other “soft skills.”  You are selling the opportunity to candidates, selling the fruits of your team’s labor to your sales/marketing team and so on.  If you are an engineer and dealing with dense people irritates you, or you take rejection personally, or if you like getting deep into technical problems – you are probably not going to be happy being “the boss.”

How do we keep engineers happy at engineering so they don’t desire to be promoted to the maximum level of incompetency?   Simple – recognize that products are really their creation.  For example a couple of guys on my team just shipped a product.  I made sure that they were the ones who were mentioned in the internal announcement – not “the team,” not “my team,” but Dave and Mike.

-mb

PS: I picked engineers here because I am familiar with this topic, but the same thing goes for marketers, sales people, artists and all other individual superstars.

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!

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 …

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…