Engineering Teams Are Just Networks

Marianne Bellotti
7 min readSep 30, 2021

To be a great hiring manager don’t be distracted by rockstar engineers, study up on network theory.

As a manager I like to build teams out of spare parts. I hire candidates who are rejected from other pipelines, I pick up people with middling performance in other teams, sometimes I even hire people whose skills are weak or out of date. My proudest accomplishments all involve teams constructed in such a manner completely out performing best-of-the-best rockstar teams assembled elsewhere. I’ve often struggled to explain how I tell the difference between a diamond in the rough and a mediocre software engineer. It’s an instinct.

But that’s a terrible answer because in hiring the line between instinct and bias is razor thin.

Recently, I was watching an interview with network theorist Damon Centola and he made a comment that hit me like a bolt of lightning:

“People always want to talk about the characteristics of a node that lead to success but the position in the network is much more important.”

And I thought “Holy shit, that’s it. That’s what I’m looking at.” Engineering teams are networks, you need to hire based on the shape of the network.

Baselines and Contagions

Eventually I’ll release a much longer, more in depth, piece of writing about this idea (possibly a follow up to my screed Hiring Engineers) but while I’m working on that I wanted to outline the basic concept, because at the core of it is an assertion that many will find difficult to get used to:

After a baseline level of competency is satisfied, who you hire does not matter.

Of course competency includes both technical characteristics and EQ characteristics, but … yeah … once you’ve filtered on technical qualifications and removed toxic personalities, you can choose a candidate at random and have a successful hire.

The trick is figuring out what that baseline of competency should be. It is determined by the shape and structure of the network and is not static, but it’s not arbitrary either. The features that will lead to a successful hire are the features that can form advantages out of the structural incentives surrounding the position, those structural incentives are determined by the network the team forms internally and how it connects to other teams as part of a larger organization.

How to Think About Your Career

9 min read

Jul 23, 2016

A Lesson in Confidence: What I’ve Learned From Working at Google as a Software Engineer

8 min read

Jun 14, 2022

We Don’t Sell Saddles Here

12 min read

Feb 16, 2014

How to Become the Best in the World at Something

7 min read

Aug 9, 2019

The best resume template based on my 15 years experience sharing resume advice

9 min read

Jan 30, 2017

20 Lessons learned going from Junior Data Scientist to Chief Data Scientist

15 min read

Apr 24, 2021

Reaching Peak Meeting Efficiency

37 min read

Apr 2, 2018

When Black Women Go From Office Pet to Office Threat

9 min read

Jan 15, 2020

How Top-Performing College Grads Fall Into the ‘Prestige Career’ Trap

9 min read

Dec 28, 2018

The 12 Signs: How to know when you’re slowly but surely becoming a bad manager

7 min read

Mar 6, 2018

Marianne Bellotti

Author of Kill It with Fire Manage Aging Computer Systems (and Future Proof Modern Ones)

Recommended from Medium

Lists

See more recommendations