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!

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 …

Why you should take the software job in San Francisco (or not).

Silicon Valley is an iconic place for technology.  Many people say this is the place for the “best and the brightest.”. Apple, Google, Facebook, Salesforce, Twitter and other top companies draw a lot of talent form all over the world and the largest chunk of VC capital goes to companies in the Bay Area, so it seems like moving here is a no brainer!

The real situation is actually not that simple, I believe there are three scenarios where it makes sense, but in many cases living in the Bay yields disappointing results.  The cost of living, housing situation, homeless catastrophe make places like San Francisco a lot less appealing to a lot of people.  So in what situations does it make sense to move to SF?

Startup founder raising millions There are many places to be a startup founder, but if you are looking to raise capital the largest pool of VC money is in the Bay Area.  There is an established network, events and conferences which give founders an opportunity to pitch more people th…