Are two heads better than one?

Are two heads better than one?

Architect level engineers are hard to find. These are the engineers that stand above the rest and are go to person for the others.? If your project is going to succeed you need one of these on your team.

So having two would double the efficiency of your engineering team right?

Sadly not always as I discovered.? This was something that led me to be even more strict about the interviewing and hiring process. More of that in a future post.

We need to hire strong engineers

As a newly appointed engineering leader for a relatively small start up I reached out to some software architects I had worked with in the past encouraging them to come join me.? These engineers are like unicorns.? Even after 40 years in the business I can easily count all the ones I know on two hands.

Pleased with myself about getting the first onboard and settling in, I set about selling the other on a position.?

Both were engineers I had worked with in the past at multiple different companies. I knew they had very different approaches to building software. What I didn’t expect was the extent of the? fireworks that ensued everytime they were in the same room together.

Ahead of time I had concerns that the two characters would gel well. Instincts I should have listened to. During the interview process I asked my first hire to reject if there was any concern on their part about the chemistry between the two of them.? Personally I reached out to the candidate to check too.

This was a small company and we needed to move fast.? Two strong engineers I knew personally. Two separate projects. What could go wrong?

Oil and water

It was a disaster. The two of them could not be in the same room together. Their very different styles and approaches just didn’t gel. They would actually call me to ask if the other was in the office that day.? If so, the other would work at home.

This nightmare management situation was entirely of my own doing. Undoing it was going to be challenging. Small start ups don’t have a lot of room to move people around if they can’t work together. We all row in the same direction or sink.?

Lessons learned

Lessons learned for me on hiring and following instincts. This led to an even more strict interview process where everyone had to be a yes, with no concerns, doubts.

If there are concerns it’s a no, if there are any doubts it’s a no.

A small team just cannot afford a bad hire.

This is also true for larger organizations. These companies include a culture fit as part of the process. Large companies can have a little more flexibility to move people around of course. A bad fit still makes a huge dent in engineering efficiency not to mention management time.

We don’t do anyone any favors bringing them into a role where they can’t be successful.

Alaks Sevugan

Experienced Technical Product Manager/TPM (Ex-Meta, Ex-Microsoft, Ex-AWS)

1 年

Yes, hiring not only for the technical skills but also for the leadership, collaboration, drive for results is important. Sometimes even a single strong minded architect who will threaten to leave if things don’t go their way is not very helpful in a collaborative environment.

回复

要查看或添加评论,请登录

Clive Beavis的更多文章

  • Sprint to Survive

    Sprint to Survive

    These product iterations were built on 3-? inch floppy disks and shipped to sales and customers on a weekly basis. 35…

  • Word Blind

    Word Blind

    The line of impatient customers was growing behind him. This was his fourth attempt to get the 4 letters of “cash” in…

    5 条评论
  • What does done mean?

    What does done mean?

    Software development is non-deterministic. Predicting time lines is difficult, even impossible.

  • Time is Money

    Time is Money

    Someone commented on my last post that much of what I said about measuring the efficiency of engineers was applicable…

    2 条评论
  • Concrete measure for eng efficiency

    Concrete measure for eng efficiency

    My last post “Clive’s Law” was a way to think about developer efficiency for a whole organization. As I mentioned in…

    1 条评论
  • Clive's Law - E = 1/D**2

    Clive's Law - E = 1/D**2

    Engineering efficiency = 1 / (distance between engineers)**2 Keep this simple equation in mind when looking to make…

    8 条评论
  • Priorities - Don’t get me started on P0

    Priorities - Don’t get me started on P0

    The planning progression Once upon a time there were 3 priorities, high, medium and low. These were not considered…

    4 条评论
  • One week sprints or four?

    One week sprints or four?

    And where do 2 week sprints factor? Tldr; As with much of software engineering there is no one size fits all solution…

  • What KPIs should I use to measure my engineers

    What KPIs should I use to measure my engineers

    A number of people DM’ed up with me after my initial post which was great. I appreciate the feedback and will adjust my…

    5 条评论
  • Replacing 55 engineers with 4

    Replacing 55 engineers with 4

    A number of years ago I was hired at a public company as the VP of Engineering. The relatively new CEO had expertise in…

    5 条评论

社区洞察

其他会员也浏览了