Remote Onboarding: What to Do in Your First 30 Days at a US Company

In an office, onboarding happens to you. Someone walks you around, drags you into lunch, and you absorb the informal rules by proximity. Remote onboarding does not work that way. Nobody is going to notice on day nine that you still do not know who approves your time off. The people who ramp fast are the ones who treat the first 30 days as a project with deliverables.

Before day one

Ask your manager for three things before your start date: a list of five people you should meet in week one, the one deliverable they would like to see from you in the first month, and which recurring meetings you are expected to attend live versus read afterward. Those three answers eliminate most of the ambiguity that makes remote starts feel shaky.

Get your equipment sorted early, and confirm the expectation in writing. Standard US remote roles usually ship a laptop, and some reimburse a monitor or headset up to a set amount. Ask HR for the policy on day one and buy inside it, or you will be eating the cost of a $200 monitor you assumed was covered. Make sure your home internet meets the minimum upload speed your team needs for video, and test your setup on the actual platform they use, not on Zoom if the company runs everything in Teams.

Week one: build the map

Spend the first week reading rather than asking. Request access to the team wiki, past project docs, and the last two months of release notes or sprint summaries. Take notes in a single file with a section per person: name, role, what they own, and one thing you might need from them.

Schedule 20-minute intro calls with the five people your manager named. Use the same three questions so the conversations are efficient: what are you responsible for, what is the biggest thing on your plate this quarter, and what is something I should know that is not written down anywhere? That third question is where the useful information lives.

Also find the answer to a set of unglamorous questions in week one: who approves expenses, where announcements get posted, what the response-time norm is in your team's chat channel, and what time zone your teammates actually work in. Nothing damages a remote reputation faster than being the person who pings people at 9pm their time.

Week two: ship something small

Ask for a task small enough to finish in a few days and real enough that someone uses the output. Documentation is the easiest win: fix a stale page, write the runbook nobody has written, clean up a dashboard. It gives you a reason to talk to people, it produces visible output, and it teaches you the tooling without the pressure of a deadline that matters.

Over-communicate while you do it. Post a short status update in the team channel when you start, and another when it ships. In a remote team, silence is not interpreted as focus — it is interpreted as nothing happening.

Week three: get outside your own team

Remote employees who only know their immediate team have a fragile position. Book two calls with people in adjacent functions: support, sales, design, whoever your work touches first. Ask what they wish your team did differently. You will learn more about the real priorities of the business in those 40 minutes than in a month of internal docs, and you will have two people who know your name when your work comes up in their planning.

Week four: put expectations in writing

Send your manager a one-page summary: what you have learned, what you shipped, the two things you think you should own next quarter, and the one question you still cannot answer. Then propose your working agreements explicitly — core hours, how you prefer to receive feedback, when you block focus time, and what your response-time expectation is in chat.

This is the highest-leverage document of your first month. It converts you from "new person we are still figuring out" into someone with a defined scope, and it gives your manager something concrete to bring to a planning meeting.

What to do when onboarding feels thin

Some companies have no onboarding process, only a Slack invite. If that is what you get, build the plan yourself: keep a "questions I asked" doc so you do not repeat yourself, set a weekly 30-minute check-in with your manager if none exists, and ask directly for a 30-60-90 day expectation list. Managers respond well to a new hire who arrives with structure.

Watch for two red flags in the first month: nobody can tell you what success looks like in your role, and your messages go unanswered for days with no stated norm. Both are worth raising once, in writing, before the 60-day mark — that is early enough to be read as diligence rather than complaint.