What a remote hire needs in week one, and what to withhold

A remote hire needs one shippable task in week one, not a tour of the org chart. Tomas spent his first five days in fourteen video calls and produced nothing at all.

The first week that went wrong

Tomas joined a twelve-person engineering team in March, three hundred miles from the nearest colleague. Nobody had met him, so the calendar filled with introductions before anyone assigned him work.

Each call was friendly and each call ended without a deliverable. He learned names rather than systems, and by Thursday he was apologising for asking basic questions about the repository layout.

The team meant well, and the schedule looked generous on paper. A week of meetings feels like onboarding to the host and like probation to the newcomer sitting alone.

Give one task that ships

The fix was a single ticket, small enough to finish in two days and real enough to reach production. His manager chose a logging change nobody had found time for.

It touched three files, needed one review, and forced him through the deployment path. That taught him more about the system than four slide decks about the system.

A shipped task also produces evidence. By day five he could point at something that existed because he had been there all week.

Withhold the org chart tour

The original schedule held eleven introductory calls, one per function. Each explained what a department did and none explained what Tomas needed from it on Monday morning.

Org charts are cheap to present and expensive to absorb. Nothing sticks until a task creates a reason to care who owns the build pipeline.

We cut the tour to two calls and let the ticket introduce the rest. He met the same people, in the order the work demanded rather than the order of seniority.

Written context beats a welcome call

Week one now opens with a document rather than a meeting. It lists the systems he can touch, the ones he cannot, and who to ask when a permission fails.

Writing it takes a manager ninety minutes. Reading it takes the hire twenty, and he can return to it in week six when the memory of a call has gone.

A welcome call is pleasant for an hour and then evaporates. The document is still there when the first incident lands on a Sunday evening.

A named person for the first ten days

Every new hire gets one named colleague for the first ten working days. The choice is patience rather than seniority, because the job is answering small questions quickly.

Tomas asked his buddy about branch naming, holiday requests, and whether the morning call was truly optional. None of that justified a manager’s calendar.

The buddy is neither mentor nor reviewer, and the separation matters. Combining the three roles makes a hire reluctant to admit confusion to any of them.

What the buddy should not be

We first gave the job to the team lead, and the hire hid problems from him. Confessing a broken laptop to your manager reads as a competence signal.

We then gave it to the engineer who had joined eight weeks earlier. He knew the friction points and had no stake in looking organised.

The buddy’s authority should stop at unblocking a task. Anything touching pay, scope, or standing goes back to the manager, who is paid to hold it.

The equipment list is onboarding

His laptop arrived on day three and the monitor on day eleven. Between those dates he worked on a thirteen-inch screen in a shared flat.

Hardware belongs in onboarding rather than in procurement. A hire who cannot read code comfortably is not being onboarded, whatever the calendar claims.

We now ship the screen before the start date. It costs the company nothing extra and removes a week of squinting from the first impression.

Silence is not abandonment

For the first month his manager sends one short message each morning and expects no reply. The message names what she is working on that day.

That habit gives the hire permission to be quiet without fearing neglect. It also models the shape of an ordinary working day.

Constant check-ins teach a new person that silence is risky. A weekly rhythm teaches the opposite, and the opposite is what a distributed team needs.

Three checkpoints, not fifteen meetings

Week one holds three fixed conversations: the task, the context, and the person. Each lasts twenty minutes and each has one question to settle.

Everything else is optional and requested by the hire. That inversion matters, because a newcomer cannot easily decline an invitation from his manager.

By Friday the calendar is nearly empty and the ticket is closed. Empty space is the part of onboarding that most teams forget to schedule.

The first feedback should be small

His first review came on day nine and covered one thing: the commit message style. It was specific, checkable, and finished in four minutes.

Small feedback early sets the price of feedback low. A hire who hears nothing for six weeks learns that judgement arrives rarely and late.

We deliberately withheld the larger conversation about scope. Two corrections in one week would have read as a verdict rather than as a note.

What week two should look like

Week two adds a second ticket with a dependency on someone else. That is the first real test, because it requires him to ask across a boundary.

He also joins one review as an observer, with a written note afterwards. Watching a decision being made is cheaper than reading its outcome.

The load stays light on purpose. A hire who is busy in week two is often a hire who will be silent in week six.

The cost of a soft first month

Tomas stayed two years. He told us later that the logging ticket was the reason he believed the job was real rather than a rumour.

The soft version of onboarding looks kinder and costs more. It spends a month of salary to produce a person who still needs a tour.

Fourteen calls cost the team eleven hours and bought nothing that a document and a ticket could not buy. We have not repeated the experiment.

A soft first week is easy to defend and hard to notice at the time. If your last remote hire cannot name what they shipped, what would you take off the calendar first?