# Remote Engineering Team Onboarding Checklist

Use this outline to prepare a distributed teammate's first days. Confirm access and practices against your own security policies.

## Before the start date
- Assign an onboarding owner and a day-to-day product contact.
- Share product goals, users, workflows, architecture notes, and current priorities.
- Confirm role expectations, working hours, overlap, meeting cadence, and escalation paths.
- Prepare approved accounts for the repository, issue tracker, communication, documentation, and development environment.
- Apply least-privilege access; do not send personal credentials or secrets in chat.
- Explain code review, testing, release, privacy, and data-handling requirements.

## First week
- Introduce the product, team, decision owners, and key stakeholders.
- Walk through one representative user workflow and the relevant system boundaries.
- Confirm local setup and access using approved processes.
- Choose a small first task with clear acceptance criteria and a named reviewer.
- Explain where blockers and decisions should be recorded.

## Second week
- Review the first delivery and give specific feedback.
- Identify missing context, access, or documentation and assign owners.
- Confirm the normal planning, demo, and reporting cadence.
- Agree the next goals and how progress and quality will be evaluated.

## Ongoing
- Review access as responsibilities change and remove it promptly when no longer needed.
- Keep product, security, and delivery documentation current.
- Revisit working agreements as the team or project changes.