Which Remote Engineering Roles Are Actually Good
The good ones are at companies that were built to work asynchronously rather than companies that permit working from home. Judge it by whether decisions are written down, whether documentation is real, whether meetings are optional by default, and whether people who are not in a hub get promoted.
The distinction that matters
A remote-friendly company has an office and permits people to work elsewhere. A remote-first company was designed on the assumption that nobody shares a room.
Both advertise as remote and the experience differs enormously.
At a remote-friendly company decisions get made in hallway conversations and meetings that remote people join as observers. Context lives in people's heads and is available by being nearby. Career progress tracks visibility, which tracks proximity. None of this is malicious and all of it is structural, and it happens even where leadership genuinely intends otherwise.
At a remote-first company decisions are written because writing is the only medium everyone shares. Documentation exists because it has to. Meetings have agendas and notes because half the participants will read rather than attend. Someone in a different time zone can reconstruct what happened and why.
The second is better to work in, and it is also rarer than postings suggest, because building it requires discipline that a co-located company never had to develop.
So the assessment question is not does this company allow remote work. It is has this company built the machinery that makes remote work equivalent.
Five questions that reveal it
Where were the last three promotions, geographically? The most useful question available. If they were all near the office, you have your answer regardless of what the policy says. Listen to the pause before the answer as much as the answer.
How are decisions recorded? Ask to see an example of a written decision. A company with real async practice produces one immediately. A company without one will describe a process rather than show an artefact.
What happens when someone is offline for four hours? In a mature setup, work continues because it does not depend on immediate response. In an immature one, things block, and the answer will describe how people usually stay available, which is the tell.
What is the meeting default? Meetings that require a stated reason and produce notes indicate one culture. Recurring meetings everyone attends indicate another.
What is the time zone policy? Not how many hours of overlap, but whether it is enforced consistently and whether teams are assembled around it. A four-hour overlap requirement applied to everyone is more workable than a nominal two-hour one that quietly expects presence at the hub's convenience.
Asking these does not read as difficult. It reads as someone who has worked remotely before, which is exactly what a good remote company wants.
What to weight less
Home office stipends, coworking allowances and retreat budgets are pleasant and tell you almost nothing about whether the work will be good. They are cheap to offer and are frequently offered by companies that have not solved any of the structural questions. Perks are what a company buys instead of changing how it operates.
The risks worth pricing in
Isolation is a design problem, not a personality one. Teams where an individual is the only person in their time zone, or the only remote member of an otherwise co-located group, produce isolation regardless of how sociable anyone is. Ask about the shape of the team, not about the social calendar.
Learning slows without deliberate structure. A significant part of early-career growth is ambient: overhearing, watching someone debug, asking a small question without scheduling anything. That evaporates remotely unless replaced deliberately with pairing, reviews that explain rather than approve, and someone whose job includes your development.
Visibility requires effort you did not have to make before. Work that is not seen is work that is not credited. In a written culture this is easier because the record exists; in a hybrid one it becomes a second job.
Time zone drift is permanent. A role that works at a three-hour difference may not survive a team reorganisation that shifts the centre of gravity. Ask what happened last time that occurred.
None of these argue against remote work. They argue for choosing the company rather than the arrangement, because the arrangement is the same everywhere and the company is not.
Frequently asked questions
- How do you tell if a remote engineering job is actually good?
- Assess whether the company is remote-first or merely remote-friendly. Look for written decision records, real documentation, meetings that require a reason, and promotions going to people outside any hub. Perks like stipends and retreats indicate nothing about whether the work will be good.
- What is the best question to ask in a remote job interview?
- Where the last three promotions were located. If they all clustered near an office, the policy does not describe the reality regardless of how it is written. The pause before the answer is often as informative as the answer itself.
- Is a remote-friendly company as good as a remote-first one?
- Usually not. A remote-friendly company has an office and permits working elsewhere, so decisions happen in rooms and context lives in people's heads. A remote-first company was built assuming nobody shares a room, so decisions are written because writing is the only shared medium.
- What are the real risks of a remote engineering role?
- Isolation, which is a team design problem rather than a personality one. Slower learning, since ambient growth from overhearing and watching does not happen unless replaced deliberately. Visibility becoming a second job. And time zone drift when a team's centre of gravity shifts.