Consider an engineer who joined a 400-person engineering org at a well-known company. Two years in, the manager knew him. The team knew him. Almost nobody else did. Solid work, average performance ratings, and a feeling of being invisible.

He made a few specific changes. Eighteen months later he had been promoted, led a cross-team initiative, and been specifically named in an all-hands as a contributor to a major product launch.

The work he was doing was not dramatically different. The way he was working had changed.

Why Large Orgs Create Invisibility

In a 10-person team, everyone knows what everyone is working on. In a 300-person org, most people know their immediate team and have a vague sense of a few others. The default is invisibility.

This is structural. There is no malice in it. Your manager’s manager may not know your name. The tech lead on the adjacent team may have heard your name mentioned once. You are a node in a graph with very few edges to the people who make decisions about your career.

The question is how to add meaningful edges without becoming “that person who is everywhere.”

The Legitimate Paths to Visibility

Write Things Up

Large orgs run on written communication. Design docs, postmortems, RFC proposals, technical analyses. Engineers who write well and share widely get read by people two or three levels above them without any awkward networking.

The formula: every time you make a non-trivial technical decision or learn something from a production incident, write a short doc (500-1000 words) and share it with the relevant channels. Not with your team only. With the broader engineering channel, or the team whose domain is adjacent to yours.

This is not self-promotion. You are sharing useful information. The byproduct is that people start to associate your name with competent thinking.

Own Something Visibly

Every large org has cross-cutting concerns that nobody quite owns. An internal tool that is slightly broken but used by everyone. A runbook that needs updating. A documentation gap. A recurring process that is inefficient.

Taking clear ownership of one of these - not just fixing it once, but visibly improving it and maintaining it - creates a specific kind of reputation. You become “the person who owns X.” That is more memorable than “a good engineer on the payments team.”

Present in Larger Forums

Tech talks, demo days, architecture reviews, all-hands. Volunteer to present, even when it is not required. A 15-minute presentation on a technical choice you made, shown to an audience of 50 engineers, creates more awareness of your work than six months of tickets in a private project.

The quality bar for these does not need to be high. It needs to be honest and clear.

Help People Across Teams

When someone from a different team asks a question in the broad engineering Slack channel and you know the answer, answer it publicly and clearly. Do this consistently and you start to become someone who people outside your team recognize.

This costs almost nothing and creates a reputation as someone knowledgeable and generous with their knowledge.

What Not To Do

Attend meetings you are not relevant to just to be visible. This is transparent and annoying.

Drop your name into processes you had no meaningful part in. Gets noticed negatively.

Make every Slack message a performance. People can feel when someone is optimizing for visibility rather than contribution.

The Sponsor Relationship

In large orgs, the career-changing move is finding one or two senior people (ideally director or principal engineer level) who know your work specifically and will advocate for you in rooms you are not in.

These relationships are built through direct work interaction, not through networking events. Get assigned to a project that a senior person leads. Do exceptional work. Follow up with a doc or analysis that shows your thinking. Do this across a 6-month period and you have a sponsor, not just a connection.

Calibrating Visibility Across Levels

Audience What Works
Immediate team Regular, high-quality work + good communication
Adjacent teams Shared docs, public Slack contributions, cross-team projects
Senior leadership Design doc authorship, presenting at larger forums, sponsor relationships
Company-wide Speaking at all-hands, major incident ownership, org-wide tool improvements

You do not need company-wide visibility to get promoted. You need the right people to know your name and your work. Be intentional about who those people are.

The Time Investment

All of the above should fit within your normal working hours. If you are spending significant extra time on visibility work at the expense of actual work quality, you have the balance wrong.

The target is roughly: 85% great work, 15% intentional communication of that work. The 15% is not separate from the job - it is part of the job at any level above junior.

Bottom Line

Visibility in a large org is not about politics or brown-nosing. It is about making your work legible to people who cannot see it directly. Write things up, own something clearly, present in larger forums, and help people across teams. Do these consistently for 12 months and the right people will know who you are. That is what changes the career trajectory - not doing more work in silence.