Remote work that does not tank your career

Three years into a fully remote job, Arjun had a performance review that blindsided him. His manager said the work was good. Then the next line: “But the team doesn’t really know what you’re working on.” He had shipped six major features that year. His Jira board was green. His manager, it turned out, barely remembered any of it.

Arjun was not failing. He was invisible. And in most organisations, invisible and overlooked are the same thing.

This is not a post about working from home tips — buy a good chair, set a routine, log off at six. You’ve read those. This is about the specific career risk that remote work creates and how to counter it with deliberate, repeatable practice.

The proximity bias problem

Proximity bias is the tendency for managers and decision-makers to favour people they physically interact with. It is not malice. It is cognitive ease. When a senior leader is deciding who to put on a high-visibility project, their brain reaches for the name that comes with a clear mental image: someone they saw at the last offsite, someone who pops up in Slack threads they’re tagged in, someone whose work they have watched evolve in real time.

Research from Microsoft’s Work Trend Index found that managers rated remote workers as less productive than in-office workers — even when output was identical. The issue was not the work. It was the lack of signal. When you are not in the room, you produce no ambient evidence of your effort, your thinking, or your growth.

In an office, a lot of this signal is accidental. Your manager walks past and sees you deep in a doc. You grab coffee with someone who mentions you to the VP. You speak up in a hallway conversation and someone remembers your instinct. Remote workers get none of that ambient broadcast. Every signal has to be intentional.

The good news: intentional signal is actually more reliable than ambient signal. Once you build the habit, you can direct it precisely, not just hope someone notices.

The two remote workers

Here is the pattern I have seen play out in many organisations — two engineers, two designers, two analysts with comparable skills and similar output, three years apart in career trajectory.

The invisible worker is not slacking. They are working by the assumption that good work speaks for itself. In an office, that assumption is partially rescued by ambient observation. Remote, it is just false.

Four practices that build visibility

1. Write your work down — consistently

The most underused career tool in remote work is the written status update. Not a formal report. A short, regular note: what shipped this week, what is in progress, what is blocked, what is coming next.

This does not have to be long. Four bullets in a shared team channel on Friday afternoon is enough. The goal is not to inform — it is to create a record of momentum. When your manager sits down to write your mid-year review, they are not rewatching the last six months. They are scanning their memory for what surfaces. A weekly note means your work surfaces.

Write for two audiences: your manager and your skip-level. Your manager needs the operational view. Your skip-level — the person two levels above you — needs the strategic one. If your company has an internal all-hands update, summarise one thing your team delivered and why it mattered. One sentence is enough to exist in that person’s awareness.

2. Share progress before anyone asks

The worst signal you can send as a remote worker is silence. It reads as blockage or disengagement, even when neither is true.

“No news is good news” is an office assumption. It works when your manager can see that your Slack status is active and your screen is filled with code. Remote, silence is data — and the data is ambiguous. Ambiguity defaults to the worst plausible interpretation.

The fix is simple: over-communicate progress at a ratio that feels slightly unnecessary. If a project is going well, say so once a week. If it hits a snag, say so the day you know, not on the deadline. “Running into a dependency on the API team — flagging early so we have options” is one Slack message. It takes 20 seconds. It completely changes how your manager perceives your ownership of the work.

The phrase “proactive status update” sounds like corporate filler. The underlying behaviour — sharing good news and bad news before the question is asked — is one of the highest-trust signals a remote worker can send.

3. Build relationships deliberately

In an office, relationships are built by proximity: you are in the same room repeatedly, you share a lunch run, you see someone frustrated at a whiteboard and offer a hand. None of that happens remotely. If you do not construct the relationship intentionally, it does not form.

This sounds clinical. It does not have to be. The practice is smaller than it sounds.

Pick five people outside your immediate team who matter to your career — peers in adjacent functions, people in roles you aspire to, colleagues who are well-connected across the organisation. Schedule a thirty-minute call with each one every quarter. Not a project call. A conversation about what they are working on, what they find hard, what they have learned. Do not ask for anything. Just be genuinely curious.

Over a year, that is twenty calls. It costs ten hours. It builds the kind of cross-functional awareness that managers describe as “executive presence” and “stakeholder management” at performance review time — neither of which is mystical, both of which are just accumulated relationships.

Follow people’s work in writing too. If a colleague posts an update about a project they are proud of, respond with a specific reaction — not a thumbs-up, but a sentence. “That approach to the latency problem is clever — I hadn’t thought about caching at that layer.” It takes thirty seconds and it tells them you are paying attention.

4. Be intentional about face time

This one is uncomfortable to say but important: face time still matters. Not all face time. Not the performative kind where you show up to be seen. The kind that happens at moments when relationships get formed — the offsite, the planning week, the first meeting with a new executive stakeholder, the team dinner.

If your company does two offsites a year, be at both of them. If you have to choose, be at the one where strategy is discussed, not the one where operations are reviewed — strategy is where the informal conversations about who is ready for what happen. If there is a team dinner, go, even if you are introverted and it drains you. You can recover in quiet time the next day. The relationship that forms over a shared meal in a foreign city does not form on a Zoom call.

Face time is not about grinding visibility. It is about compressing the relationship-building that remote work makes slow. One week in person does the work of three months of async interaction. Prioritise it accordingly.

What this is not

Visibility is not self-promotion in the cheap sense — not broadcasting your wins to seem indispensable, not engineering opportunities to be seen by senior leaders so they notice you. That version is obvious and it backfires. People can tell.

The version described here is quieter and more durable. It is about making your thinking legible, your progress traceable, and your relationships real. All three are things that would have happened naturally in an office through accumulated ambient contact. Remote work just requires you to produce them deliberately rather than accidentally.

The underlying principle is this: your manager cannot advocate for you in rooms you are not in if they do not have a clear picture of what you are doing and where you are headed. Your job is to give them that picture, regularly, without waiting to be asked.

Arjun figured this out in his fourth year. He started a weekly five-bullet note in his team channel, spent fifteen minutes every Friday reviewing what his manager knew and what was still opaque, and booked a quarterly call with his skip-level to discuss career direction. Six months later his review described him as someone with “strong strategic communication.” The work had not changed. The signal had.

That is the whole game.