Your First 30 Days in a New Remote Job: A Practical Plan

Your first month in a remote job comes down to three things: getting your accounts and devices set up securely, finding where the team keeps its written knowledge, and agreeing with your manager how you will work together. Nobody sees you settling in at a desk, so you have to make your progress visible in other ways. This plan takes you through the first few weeks in roughly the order things come up, with questions to ask and habits worth starting early.

Before day one: what to ask for

Well-run onboarding usually starts before your first day. Carnegie Mellon University's guidance tells supervisors to send new staff an onboarding schedule before day one so they know what to expect in their first week. At 37signals, the company behind Basecamp, the handbook says your manager emails first-day instructions a day or two before you start.

If a few days before your start date you still have no instructions, a short, friendly email to your manager or HR contact is normal. Ask for:

• the time and link for your first meeting, and who will be in it;
• whether a company laptop is being sent, when it should arrive and who to contact if it is delayed;
• which accounts will be created for you and which you set up yourself;
• whether you will have an onboarding buddy or a named person for day-to-day questions;
• any documents to read before you start.

Check your internet, power backup and headset before day one too; our home office guide covers that setup in detail.

Week one: accounts, devices and two-step verification

Expect a burst of new accounts in your first days: email, chat, a password manager, project tools and perhaps a VPN (a virtual private network that gives you secure access to internal systems). Secure each one as you create it, not later. The UK's National Cyber Security Centre (NCSC) calls turning on two-step verification one of the most effective ways to protect online accounts. Also known as two-factor authentication (2FA) or multi-factor authentication (MFA), it keeps criminals out even if they know your password.

• Turn on two-step verification for every work account that offers it, using the method your company specifies, such as an authenticator app or a security key. The NCSC notes the option is usually in an account's security settings.
• Save the backup or recovery codes somewhere safe that is not the same laptop, so a lost device does not lock you out.
• Never reuse a personal password for a work account. The NCSC says the most common way passwords are stolen is a data breach at an organisation holding your details.
• Install system updates when prompted, and set a screen lock.

Company laptop or your own device?

If your employer gives you a laptop, treat it as theirs. The 37signals handbook, for example, asks staff not to keep personal files on company computers, says work code, secrets and VPN access belong only on a work device, and explains that managed laptops can be wiped remotely if lost or when someone leaves. Other employers have their own policies, so read yours in week one.

If you are asked to use your own laptop or phone, the NCSC's guidance on bring-your-own-device schemes is a useful reminder of the trade-off: the organisation owns the work information on the device, while the device remains yours. Before you install anything, ask what the company's software can see, whether it can wipe the whole device or only work apps, and what happens to work files when you leave. A separate browser profile or user account for work keeps the two apart.

Where does the team's written knowledge live?

Remote teams depend on writing far more than offices do. The 37signals guide to internal communication puts it simply: speaking only helps whoever is in the room, writing helps everyone. Its handbook asks staff to make posting a message, a to-do or a document their first choice of action, so others can reply on their own schedule.

In your first two weeks, build your own map of where things live. Find out:

• where the handbook, wiki or main reference documents are kept, and how current they are;
• where project work and tasks are tracked;
• where decisions are written down, and who usually writes them up;
• which chat channels exist and what each one is for;
• where meeting recordings, transcripts, chat logs and shared files are stored, which the NCSC suggests every meeting user should know.

The same 37signals guide makes a point worth remembering: when someone has to search for something, it is often because it was not where they expected it to be. So when you post a question or a document, ask where it belongs rather than dropping it in the nearest chat.

Agreeing working hours and response times with your manager

Unspoken expectations cause more early friction in remote jobs than almost anything else. The University of Kansas new-employee checklist includes confirming work hours, agreeing the preferred method for reporting updates, and identifying who to go to for questions. Companies differ widely here. The 37signals handbook asks staff to collaborate as though most requests will get an answer eventually, not necessarily right away, while other teams expect quick replies on chat during set hours.

Settle these questions with your manager in your first week or two, and confirm them in a short written message afterwards:

1. Which hours are you expected to be available, and is there a fixed overlap window with the team? If your team is spread across time zones, agree the overlap in your own local time; our async communication guide covers the rest.
2. How quickly should you reply on chat, on email and in the project tool?
3. What counts as urgent, and how should people reach you, and you them, when something is?
4. How should you share progress: a written daily or weekly update, a stand-up call, or both?
5. How do you mark leave, and which public holidays apply to you?

Making your first one-to-ones count

At 37signals, a new starter and their manager meet on the first day to set up a recurring one-to-one schedule and review onboarding expectations. Carnegie Mellon's supervisor guidance likewise asks managers to discuss job duties and expectations early and to check in regularly through team and one-to-one meetings. If no recurring meeting appears in your calendar in week one, ask for one.

Keep a shared running document for your one-to-ones, add topics during the week, and bring these to the first few:

• What would a good first month look like, and what should I have delivered by the end of it?
• Who are the people I most need to meet, and in what order?
• Which decisions can I make on my own, and which should I check first?
• How do you prefer to receive questions: saved up for our meeting, or as they come?
• Is there a small, real piece of work I can take on this week?

That last question matters. The 37signals handbook says new staff start on real projects within their first week, with support, and gives its new starters a list of people to meet over their first few weeks, including a buddy from outside their immediate team. If your company offers a buddy, use them for the questions you feel awkward asking your manager.

Getting early feedback and keeping a written record

Remote feedback rarely arrives unprompted. The 37signals communication guide says that if you want an answer, you have to ask a question, and that applies to feedback too. Ask specific questions about recent work rather than 'How am I doing?', for example:

• On the document I shared on Tuesday, what would you have done differently?
• Is the level of detail in my updates right, or should they be shorter?
• What is one thing I should do more of, and one thing I should stop?
• Is there anything people have mentioned about working with me that I should know?

Keep your own expectations realistic. 37signals says most of its new staff feel up to speed and fully part of the team in about three months. That is one company's experience, not a rule, but it is a fair reminder that the first month is for learning, not proving everything at once.

Writing down what you learn

Writing things down helps you and the next person who joins. 37signals asks staff a daily 'What did you work on today?' question and expects an answer at least twice a week, alongside a Monday plan for the week. Even if your team has nothing like this, a short written note to your manager at the end of each week covering what you finished, what you learned and where you are stuck keeps you visible.

• Note setup steps that were missing or wrong in the onboarding instructions, and offer to update them.
• Keep a glossary of the team's acronyms, product names and internal tools.
• After any call where something is agreed, post a two-line summary where the team works.
• Record answers to questions you asked, with a link to where the answer lives, so you never need to ask twice.

Early mistakes that are easy to avoid

• Staying stuck in silence for days. Try first, then ask in writing, saying what you tried and what you need.
• Mixing personal and work use on the same device or accounts, or copying company files to personal storage to work faster.
• Replying to messages at all hours in your first weeks, which sets an expectation you cannot keep later.
• Agreeing something on a call and never writing it down.
• Moving city, state or country without telling your employer first. The 37signals handbook asks staff to tell its People Ops team when they move, because a move can affect the employee's or company's tax position.

Your 30-day remote onboarding checklist

1. By the end of week one, have two-step verification on every work account, recovery codes stored safely, and your company's device policy read.
2. Also in week one, get a recurring one-to-one in the calendar and send your manager a short written summary of agreed hours, reply times and update format.
3. By the end of week two, finish your map of where documents, decisions, recordings and tasks live.
4. During weeks two and three, meet the people on your list and finish your first small piece of real work.
5. In week four, ask your manager for specific feedback and agree what you should focus on next month.