Your First 90 Days in a Remote Job

General — Nov 11, 2026

Nobody will tell you how you're doing, and you'll assume the worst. A month-by-month approach to building context, relationships and visibility when you can't read the room.

The first three months of a remote job have a particular emotional shape, and almost everyone goes through it.

Week one is pleasant and slightly unreal. By week three you're fairly sure you're underperforming, because nobody has said anything either way. By week six you've decided the silence means something. It usually doesn't. It means your manager is busy, and the feedback you'd have absorbed by osmosis in an office simply isn't reaching you.

The fix is to stop waiting for signals that won't arrive and start generating your own.

Days 1–30: build context, not output

The temptation is to ship something quickly to prove yourself. Resist it, mostly. A fast early win built on a misunderstanding of how things work costs more than it earns.

Read everything that's written down. Handbook, past decisions, the last six months of the main project channels, onboarding docs even if they're outdated. In a remote company, the written record is the institutional memory. Reading it fast and thoroughly is the single biggest accelerant available to you.

Keep a running "things I don't understand" doc. Every acronym, every process that seems strange, every name that keeps coming up. Batch the questions and ask them in one go to the right person, rather than interrupting someone eleven times a day.

Meet people deliberately. Twenty-minute calls with everyone you'll work with closely, plus two or three people adjacent to your role. Ask each one the same three questions: what are you working on, what's hard about it right now, and who else should I talk to. The third question builds your map of the company faster than any org chart.

Agree what success looks like, in writing. By the end of week two, have a short document with your manager covering what you should have done by day 30, 60 and 90. If they haven't proposed one, draft it yourself and ask them to correct it. This is the most important document of your first quarter, because it turns "am I doing okay?" into something you can check.

Days 31–60: take something small and finish it

Now ship. Pick something contained, visible and genuinely useful: a fix, a process improvement, a piece of documentation people keep asking for. Finish it completely, then write up what you did and why in the channel where people will see it.

The point isn't the size. It's demonstrating, early, that you close loops. Remote colleagues form their view of you from very little evidence, and a finished thing with a clear write-up is the best evidence you can give them.

Start a weekly written update now if your team doesn't have one. Three lines: what shipped, what's next, what's blocking you. Send it to your manager even if nobody asked. It answers their unspoken question about how you're doing, and it gives you a record you'll be glad of at review time.

Days 61–90: own something

By month three you should be moving from tasks to ownership — an area, a metric, a recurring piece of work that's recognisably yours.

Ask for it explicitly. "I'd like to own the onboarding emails end to end. Does that work?" Managers are usually relieved to be asked, and ownership is what changes how people see you.

Run the 90-day check yourself. Go back to the success document. Book thirty minutes with your manager, go through it honestly, and ask two direct questions: what should I do more of, and what should I stop doing? Ask exactly that. "Any feedback?" invites "you're doing great", and that tells you nothing.

The thing that catches most people out

Silence in a remote company is not a verdict. It's the default state, and it's the same for everyone.

New starters routinely interpret the absence of praise as criticism and either withdraw or overwork to compensate. Both are mistakes. The people who settle in fastest are the ones who decide early that they'll generate the feedback loop themselves: written plans, written updates, direct questions at fixed intervals.

You can't read the room. So build a room you can read.

More articles