The Proximity Effect

Opportunity does not flow to the best person in the org chart. It flows to whoever is standing nearby when it appears.

Most engineers model opportunity allocation as a search problem: leadership has a task, they scan the roster, they pick the most qualified person. That model is wrong. In practice, opportunity allocation is a proximity problem. A director walks out of a sync with an urgent problem and hands it to the first competent person she encounters — in the hallway, in the thread she's already reading, in the meeting that just ended. Nobody opens the directory. Nobody runs a fair search. The staffing decision is made in seconds, from whatever names are already in working memory.

Proximity has three dimensions, and you can be strong or weak on each independently:

Physical — you sit on the same floor as the people who decide things. You are in the whiteboard session that continues after the meeting officially ends.
Temporal — your working hours overlap with the hours when decisions get made. You are awake and responsive during the decision-making timezone's afternoon.
Ambient — you are visible in the Slack channels leaders actually read, you respond fast, your name appears attached to useful artifacts. Leaders "see" you regularly even if they never see your face.

Miss all three and your work can be excellent while your opportunities quietly dry up.

Mechanics

The availability heuristic does the staffing. When a leader needs someone for a new initiative, their brain does not enumerate candidates — it surfaces whoever they have recently seen, heard, or read. This is the availability heuristic: ease of recall substitutes for a real search. The person who spoke in yesterday's review, the name on this morning's incident summary, the engineer who answered a question in #eng-leads twenty minutes ago — these names come up. The objectively stronger engineer three floors away or nine timezones east does not, not because anyone dislikes them, but because recall never reached them.

Trust is built by repetition, not magnitude. Mere-exposure effect: repeated low-stakes contact makes people feel familiar, and familiarity reads as trustworthiness. Fifty two-minute interactions build more trust than one brilliant quarterly presentation. The engineer who is casually present — a hallway question here, a quick Slack answer there — accumulates trust continuously. The remote engineer gets a handful of scheduled, formal touchpoints per quarter, each carrying the full weight of their reputation. Formal contact is high-variance; ambient contact compounds.

Decisions happen in the interstitial spaces. The official meeting produces the official decision, but the framing — who's credible, which option feels risky, who should own it — gets shaped before and after: the pre-meeting coffee, the walk back to the desks, the whiteboard session that starts when the recording stops. If you attend only the scheduled block, you receive decisions; you don't shape them.

The remote tax

Two engineers do identical work. One sits near leadership; one is remote or offshore. The nearby one gets systematically more stretch assignments, more visibility projects, more sponsorship. This is proximity bias, and it is documented in hybrid-work research, not a grievance narrative — studies of hybrid organizations consistently find remote workers receive fewer promotions and less development investment at equal performance. It is rarely malicious. It is the availability heuristic running at organizational scale.

The temporal version is the timezone tax. If you are asleep when the decision-making timezone has its afternoon — when the syncs happen, the threads get resolved, the "who can take this?" moments occur — you wake up to conclusions. You read the summary; you never touch the framing. Over a year, this compounds into a career where you execute other people's decisions and are described, accurately but fatally, as "a strong executor."

Counter-moves

You cannot abolish the bias. You can engineer around it.

If remote, manufacture presence. Camera on. Speak in the first ten minutes of the meeting — early airtime anchors you as a participant rather than an attendee. Post substantive things in the channels leaders read, not just your team's channel. Respond fast during the hours that matter.
Pay the timezone tax selectively. You don't need full overlap. Identify the two or three recurring meetings where staffing and direction actually get decided, and shift your hours to be present for those. Being awake for the right ninety minutes beats being awake for the wrong eight hours.
Go to the office on the days that matter, not by quota. Three badge-swipes on days leadership is remote buys you nothing. One day when the director is in and the roadmap review is live is worth the week. Optimize for coincidence with decision-makers, not attendance metrics.
Volunteer for roles that put you in the room. Incident commander, demo presenter, the person who writes the review doc. These roles come with structural proximity — leaders must interact with you — and they arrive with substance attached.
Build ambient presence through artifacts. A crisp design doc, a widely-shared postmortem, a weekly update leaders actually read — written artifacts circulate through timezones while you sleep. They are the one form of presence that scales asynchronously. A good doc is a version of you sitting in a meeting you couldn't attend.

Caution

Proximity without substance is loitering. Presence is an amplifier: it multiplies whatever reputation your work has already earned. If the work is strong, proximity converts it into opportunity. If the work is thin, proximity just gives more people a front-row view of the thinness — and leaders notice the person who is always around but never load-bearing. Do the work first. Then make sure the work, and you, are where decisions can see them.

Diagnostic test

When something urgent and career-shaping landed on your team in the last quarter, were you in the conversation where it was assigned — or did you find out afterward?