Build a Network of Peers
selt networking peers community learning staffeng
Status: Notes complete
Overview
Staff engineers face a structural isolation problem. Within their company they sit above the level where direct reports can offer peer feedback, and managers have different concerns and incentives. The result: there is often no one nearby who can give calibrated, high-quality feedback on the actual problems Staff engineers face.
The solution is deliberate network-building — both internally across teams and externally across companies. Larson argues that a peer network is not a career accessory but a core professional tool: the primary mechanism by which Staff engineers get honest feedback, calibrate their assumptions against broader reality, and continue growing after reaching a level where formal career development structures largely disappear.
Core Concepts
Structural Isolation at Staff Level — At senior individual contributor levels, the normal feedback mechanisms break down:
- Direct reports are not peers; their relationship with you is not symmetric.
- Your manager is often focused on business outcomes and organizational dynamics rather than your technical or strategic judgment.
- Teammates at lower levels may not have the context to evaluate your decisions.
- The result: Staff engineers can go months or years without anyone genuinely challenging their technical or strategic thinking.
A peer network directly addresses this gap.
Internal Peers — Other Staff+ engineers at the same company on different teams. These peers share your organizational context (company strategy, culture, constraints) but bring different domain perspectives. Internal peer relationships are built through:
- Attending cross-team architecture reviews and planning sessions
- Proactively offering help on non-critical problems in adjacent domains
- Sharing relevant knowledge without being asked (a short summary of something you learned, an interesting postmortem, a useful technique)
- Regular informal contact — coffee chats, quick messages — with no specific agenda
External Peers — Staff+ engineers at other companies doing comparable work. These peers provide something internal peers cannot: a view from outside your company’s assumptions and blind spots. The value is calibration — understanding whether the problems you face are universal or specific to your situation, and how other organizations have solved them.
Why External Peers Are Uniquely Valuable
External peers offer information that is essentially unavailable through any other channel:
- Reality-checking assumptions: Is our deployment process genuinely unusual or is this how everyone does it? Is this organizational dysfunction normal or a fixable local problem?
- Access to solutions your company hasn’t tried: The way your company approaches on-call rotations, technical strategy, or Staff-level promotion is one approach among many. Peers at other companies have tried different things; some of those things work better.
- Industry context: What are the trends shaping the technical landscape that your company-internal perspective makes it hard to see clearly?
- Job market calibration: Understanding what Staff-level roles at other companies involve, what they pay, and what they value — even if you are not looking to change jobs.
- Unfiltered honesty: External peers have no political stake in your company’s decisions. They can tell you when something sounds broken without managing their own career interests in the process.
How to Build the External Network
Larson identifies several practical mechanisms:
Writing publicly — Blog posts, essays, and articles attract peers who are thinking about the same problems. The asymmetry is favorable: you invest once in writing, and it continues generating connections over time. Writing does not require a large audience to be effective — it requires the right audience: people who care about the same problems you do.
Conference talks — Similar leverage to writing, with the addition of real-time conversation. A talk attracts people who found your framing valuable and want to continue the discussion. Conferences also concentrate peers geographically for a few days, making relationship initiation much lower-friction.
Open source contribution — Working on shared infrastructure or tooling puts you in ongoing collaborative contact with engineers across companies. The collaboration creates natural peer relationships grounded in shared technical work.
Engaging with communities — The staffeng.com community (and the associated Slack, newsletter, and interview archive) is a specific example Larson cites: a deliberate attempt to create a shared space for Staff+ engineers to exchange experiences and calibrate against each other. Engaging with communities like this — not just reading but commenting, sharing, and contributing — builds relationships at scale.
Direct outreach — Reaching out to someone whose writing or talk you found valuable, with a specific message about what resonated, is underused and effective. Most people at this level receive fewer genuine peer-connection requests than you might imagine.
The Reciprocity Principle
Networks require giving before receiving. This is not a cynical strategy — it reflects how genuine professional relationships work: people help those they know, trust, and have received value from.
Practical forms of leading with value:
- Share insights freely: If you learned something from a production incident, a reorganization, or a technical trade-off, write it up and share it. You cannot know in advance whose problem it solves.
- Make introductions: When you can connect two people who would benefit from knowing each other, do it without being asked.
- Comment thoughtfully on others’ writing: A substantive comment that engages with someone’s actual ideas is a relationship initiation that costs almost nothing.
- Answer questions in communities: Answering a question in a forum or Slack channel builds your reputation and relationships simultaneously.
The failure mode is approaching network-building as extraction: reaching out only when you need something. People notice, and the contacts never warm into actual relationships.
Maintaining Relationships Without an Agenda
Strong professional networks are maintained through low-intensity regular contact, not through high-stakes periodic requests. The goal is to keep relationships warm — so that when you do need something (a reference, a perspective, a collaboration), the relationship is already real.
Low-intensity maintenance mechanisms:
- A short direct message when you read something the person wrote (“This resonated — I’ve been dealing with exactly the same thing”)
- Reacting to or sharing something they published with a brief note about why
- A biannual check-in with no specific purpose — just an update on what you’re working on and asking about them
- Mentioning their work or ideas in contexts where it is genuinely relevant
The test of a maintained relationship is whether it would feel natural to reach out with a real question today. If the answer is no, the relationship has gone cold.
The Asymmetric Network
Your “peer” may not yet see you as their peer. Relationships at this level are not established by title — they are established through demonstrated value and genuine exchange. An engineer who reads your work, shares perspectives you find genuinely useful, and engages substantively with the problems you’re working on is a peer, regardless of title. Conversely, having a matching title with someone creates no actual peer relationship.
The practical implication: do not wait until you “deserve” to reach out to someone whose work you respect. Reach out because you have something genuine to contribute to the conversation. The asymmetry will resolve over time through the relationship itself.
The Staffeng.com Community as a Model
Will Larson’s own staffeng.com project is a deliberate operationalization of this principle. The site compiles interview transcripts with Staff+ engineers across dozens of companies, explicitly intended to:
- Show Staff+ engineers what the role looks like across different company contexts
- Provide a shared vocabulary and set of reference points for a level that has no textbook
- Connect Staff+ engineers who would otherwise be isolated in their individual companies
The community it spawned (Slack channel, newsletter) exemplifies Larson’s argument: a peer network at scale, built around shared publication, common language, and mutual investment in the others’ understanding of the role. It is also a direct result of one person leading with value (publishing) before receiving anything.
The Network as a Learning Mechanism
What you learn from peers about how other companies solve problems is, Larson argues, uniquely valuable and largely unavailable in books. Books describe patterns after they’ve stabilized; peers describe what they’re currently trying, including what is failing. The information is:
- More current than any published source
- More specific to your actual context (because your peer knows your situation)
- More candid (because they have no stake in presenting a sanitized version)
- More varied (because you hear multiple approaches, not one authoritative answer)
A well-maintained peer network is a continuously updated, highly relevant curriculum that no formal learning program can replicate.
Key Takeaways
- Staff engineers face structural isolation — above the level of direct-report feedback, below the level of manager calibration — and peer networks are the primary way to address it.
- Internal peers (Staff+ engineers across different teams at your company) provide calibrated feedback with organizational context; external peers provide an outside view that corrects for company-specific blind spots.
- External peers are uniquely valuable for: reality-checking assumptions, accessing solutions your company hasn’t tried, industry calibration, and unfiltered honesty.
- The most scalable ways to build external networks are writing publicly, conference talks, open source contribution, and engaging with communities like staffeng.com.
- The reciprocity principle: lead with value (share insights, make introductions, answer questions) before expecting anything in return.
- Networks are maintained through low-intensity regular contact — short messages, reactions, biannual check-ins — not just high-stakes periodic requests.
- The asymmetric network: peer relationships are established through demonstrated value, not matching titles. Reach out when you have something genuine to contribute.
- Staffeng.com exemplifies the peer network at scale: one person leading with value (publishing) creating an entire community of mutual calibration.
- What peers teach you is often more current, more specific, and more candid than any published source — the peer network is a living curriculum.
- Approaching network-building as extraction (only reaching out when you need something) ensures the network never develops; genuine relationships require mutual investment.
Related Resources
- sec08-create-space-for-others — Network relationships are how you discover who needs sponsorship beyond your immediate team
- sec02-work-on-what-matters — Writing publicly (network-building) is also a scaled form of high-leverage work
- sec05-present-to-executives — External peers provide calibration for how to communicate at senior levels at other companies
- ch05-being-visible — Complementary framework on visibility as a component of Staff-level career development
- staffeng.com — Will Larson’s community site; the practical instantiation of peer network building at scale
Last Updated: 2026-05-30