StaffEng Banner

Guides / Build a network of peers

As I talked to more and more Staff-plus engineers about career advice, the most consistent recommendation was to develop a personal network of peers doing similar work. Not every person emphasized this approach, but more than half mentioned it, and for those who did, it tended to be their first and strongest recommendation.

Ritu Vincent said,

What's been most impactful for me is having a lot of people who I think of as mentors, usually friends, former managers, and folks that I've worked with. I have a decent number of recurring monthly lunches, coffee chats, and dinners with people who've worked with me in the past, know me, and I trust. It's those conversations about career challenges and growth that have gotten me to where I am in my career.

Keavy McMinn mentioned her network as an important way to get honest feedback,

The thing that springs to mind is to find your peers or support network. Just like management, it gets lonely the higher up you go, and it's important to find peers that will still challenge you, and you can brainstorm ideas with. It doesn't even matter if they're in your similar area of work or even are in different companies.

Nelson Elhage similarly shared,

It's also been really valuable for me to cultivate a good personal network of other senior engineers. I chat with them informally about whatever it is that we're working on and thinking about. When you have personal connections, you can get very unvarnished views of the problems people are seeing and the solutions they're considering.

While it's helpful to know you should build a network, some folks struggle to figure out how to do it. Among the various tactics to build your network, the two most common strategies are: being easy to find and networking internally.

Be visible

There is so much pent-up demand for community among Staff-plus engineers that the easiest way to build your network is being easy to find as a Staff-plus engineer. One effective approach is contributing to the discussion around Staff-plus engineering itself, like Joy Ebert'z What a Senior Staff Software Engineer Actually Does or Keavy McMinn's Thriving on the Technical Leadership Path. Although there are a good number of folks who've written up their view on the Staff-plus role, each one brings a new, valuable perspective. There's room for your words on the topic.

If writing isn't your jam, there's room for your voice, and speaking at tech conferences is another effective way to become visible in the broader community. Keavy McMinn described her motivation for conference speaking as,

Mostly, I enjoyed the people I met at conferences. Later the speaker networks led to job opportunities for me.

If those both feel high-stakes, even starting a Twitter account or joining a couple of related Slacks (for example, #staff-principal-engineering in the Rands Leadership Slack) can be a good start.

Internal networks, too

Rather than focusing on public speaking and writing, Katie Sylor-Miller 's networking advice was to build your internal network within your current company,

Networking, networking, networking, networking… You have to be really cognizant of who you're talking to and make sure that you have connections across multiple teams and multiple groups to leverage those networks.

Although it's easy to think of networking as something that only happens externally, it's often easier to do at the company you're already in, where it happens semi-organically and semi-deliberately over the course of your work. This approach has the added advantage of directly improving your day-to-day work as well. Longer-term, those folks will eventually leave and spread across the industry, bootstrapping your broader network. This works really well when you're at a decently large or prestigious company and is a bit less effective as your current company gets smaller or less prestigious.

Ambient networks

Among the folks who didn't mention developing a personal network, most mentioned creating an ambient network of learning based on keeping current with industry books and following industry leaders on social networks, particularly Twitter.

Diana Pojar’s comment was

I use Twitter extensively, but I'm mostly a consumer and follow many people in tech. I usually follow people that I saw talking at conferences, or I worked with, and I find their content relevant to me. Here’s a couple, in no specific order: Camille Fournier, Lara Hogan, Josh Wills, Vicki Boykis, David Gasca, Julia Grace, Holden Karau, John Allspaw, Charity Majors, Theo Schlossnagle, Jessica Joy Kerr, Sarah Catanzaro, Orange Book.

Damian Schenkelman mentioned,

I try to follow people on Twitter who I think are doing interesting things and from who I can learn. There are so many people doing interesting things and so much to learn! Some of the names that come to mind: [including Aphyr, Tanya Reilly, and David Fowler].

If the idea of building a network this way feels uncomfortable then building an ambient network can be a good starting step in the right direction. That said, you'll find the personal network more impactful, and finding an authentic way to build one is an important step towards reaching and remaining impactful in senior roles over the long arch of your career.

Quality over quantity

A coworker once told me the story of someone determined to make their name in Business Development, who would fly from SF to NYC with a list of people they wanted to meet. They'd look for tweets and Foursquare check-ins for where those people might be that night, go there, buy a drink, and pretend to serendipitously meet them. On a good night, they'd try to meet six or more new connections this way.

It goes without saying that you shouldn't do that -- it's a total violation of boundaries. Further, doing this doesn't even make sense: when it comes to building a network of peers, the volume doesn't matter. Instead, focus on slowly building with folks you genuinely trust, respect, and are inspired by. That's what'll create a truly powerful network to help you solve the hardest problems and trickiest situations that come your way.

Finally, if you've reached this paragraph and really want to build a network but just aren't sure how to get started, I'll share what's worked for me as an introvert who struggled to craft an authentic approach. Find someone you respect and send them a short 1-2 paragraph email or DM with a specific question asking for advice. If they reply, thank them and send another question in six to twelve months. If they subsequently ask you for a favor or question, do what you can to help. If they don't reply, don't worry about it; just move on without comment. This works surprisingly well, and the worst thing that can happen is totally fine: they'll just never reply.

Read another guide? or Back to the stories?

If you've enjoyed reading the stories and guides on, you might also enjoy Staff Engineer: Leadership beyond the management track, which features many of these guides and stories.

Staff Engineer book cover

Would you like an email when new stories are posted?