Most advice about remote work is either "it's amazing, you'll never go back" or a list of productivity apps. Neither one is very useful when you're actually trying to decide whether to take a remote job, or trying to make one work once you have it.
Here's what actually matters.
The job itself has to fit remote work, not just allow it
Some roles were built for an office and just got a "remote OK" label stapled on. If your job depends on quick hallway conversations, whiteboard sessions, or reading a room, remote makes it harder, not easier. The roles that thrive remote are ones where the output is written down anyway: code, documents, tickets, designs. If most of your job already lives in a doc or a tracker, remote barely changes anything. If it doesn't, remote adds friction nobody warned you about.
Async is a skill, not a setting
A lot of "remote doesn't work for us" is really "we never learned to write things down clearly enough that people don't need to ask." Good async communication means:
- Writing the context, not just the ask ("here's what I'm trying to do and why" beats "can you look at this?")
- Defaulting to a shared doc or channel over a DM, so the answer helps the next person too
- Being honest about when something actually needs a live conversation, and just booking the 15 minutes instead of a 40-message thread
The hours are yours, but the boundary is your job
Nobody is going to protect your evening for you. Remote work removes the natural signal of "everyone's leaving, I should too." Some people thrive with that flexibility. Others end up working more hours than they did in an office, just spread out and harder to notice. Decide your actual working hours on purpose, and treat them like a real boundary, not a suggestion.
Watch for postings that are remote in name only
"Remote" that actually means "remote, but must relocate to our metro area" or "remote, but core hours in a timezone eight hours from yours" is common enough that it's worth reading the fine print before you get excited. A posting that's genuinely remote usually says so plainly, without a location requirement buried two paragraphs down.
None of this is a reason to avoid remote work. It's just the part that doesn't fit in a listicle: it works when the role fits it, when communication is deliberate, and when you draw your own lines, because nobody else is going to draw them for you.