How do you make sure your work stays visible when your team is fully remote?

## Common wordings This prompt appears in remote and hybrid loops under several wordings: - "how do you stay visible without an office" - "how do you communicate progress to people you never see" - "how do you know what your teammates are working on" It is occasionally inverted as "how do you tell when a remote teammate is stuck". They are all asking the same thing: does this person have a deliberate practice for making state legible in writing, or do they assume the work speaks for itself. ## The assumption is the trap In a room, presence is a signal — people see you at a whiteboard, overhear a debugging session, notice you leave late. Distributed, none of that reaches anyone. What reaches people is what you wrote. Candidates who answer that they simply do good work and trust it to be noticed are describing a **co-located instinct**, and interviewers on distributed teams have watched exactly that instinct produce engineers who are silently blocked for a week and engineers whose contributions nobody can account for at review time. ## Specificity plus a filter What separates a strong answer is **specificity plus a filter**. Two or three named habits beat a list of eight: - an end-of-day written state - a rule about how long you sit on a blocker before saying so publicly - asking in a shared channel rather than a direct message so the answer is searchable - writing a short decision record when a call gets made verbally Then, critically, say what you leave out. Visibility practices fail in both directions — the engineer nobody hears from, and the engineer whose updates are so long that nobody reads them, which is functionally the same outcome. Naming your filter, even in one sentence, tells the interviewer you have run this practice long enough to have trimmed it. ## A moment with a consequence The second thing that separates strong answers is **a moment**. An abstract description of rituals scores as theory; one occasion where something you wrote changed what another person did converts the whole answer to evidence: - someone found your note and stopped duplicating your work - a written risk got picked up before it became a problem - a decision record ended a debate that had already been settled once It does not have to be dramatic. It has to be real and it has to have a consequence outside your own head. ## Watch the framing carefully This question sits uncomfortably close to self-promotion, and candidates often lean one of two wrong ways. - **Some describe visibility purely as career management** — making sure the manager knows what I did — which reads as optimising for perception rather than delivery. - **Others over-correct into modesty** and describe nothing at all. The framing that lands is **coordination**: I write so that other people can act without waiting for me, and a side effect is that my work is legible. Then the promotion-adjacent benefit is real but not the stated motive. ## How the bar moves with level - **Early on**, personal habits are the whole answer, and knowing that silence reads as stalled is genuinely the signal being checked. - **In the middle**, the expectation is that your updates are shaped for their readers rather than being a diary, and that you can cite the moment. - **Senior candidates** are expected to make the team legible, not just themselves — a status artifact someone can read without asking you, credit distributed by name, risks escalated in writing before they are urgent. - **Above that**, the answer becomes information architecture for an organisation: what is written by default, where decisions live so that a newcomer can reconstruct them, and how you stop a good practice from calcifying into reporting theatre that everyone performs and nobody reads.