Remote Hiring Checklist: 25 Steps Before Your First Remote Hire Starts
Before a remote hire's first day, 25 things need to be in place — from tool access provisioned to a written 90-day output expectation to a defined daily standup format. Companies that complete this checklist consistently see remote professionals reach full productivity in 30 days versus 60–90 days without it.
In summary
Before a remote hire's first day, 25 things need to be in place — from tool access provisioned to a written 90-day output expectation to a defined daily standup format. Companies that complete this checklist consistently see remote professionals reach full productivity in 30 days versus 60–90 days without it.
The 25-Step Remote Hiring Checklist
Organized into 5 phases: before the offer, before the start date, day one, week one, and day 30.
Phase 1: Before Making the Offer (5 Steps)
☐ 1. Write the role brief with stack specifics. Not "developer with 4+ years experience" — "React 18 + TypeScript + Node.js + PostgreSQL, senior level, 5–7 years, U.S. EST overlap." The specificity of the brief determines the quality of candidates you see.
☐ 2. Define the U.S. overlap schedule. Start time, end time, time zone. State it in the job brief and confirm it in the offer. No ambiguity.
☐ 3. Write the 90-day output expectation. One paragraph with 3 milestones (day 30, 60, 90). Specific deliverables. Share with candidates before the offer — the right candidates will be energized by clarity, not threatened by it.
☐ 4. Identify the technical assessment. For technical roles: a 2-hour take-home task covering real work (not leetcode). Defined before the interview so you evaluate consistently across candidates.
☐ 5. Define the escalation protocol. What does the hire escalate vs. handle independently? What type of questions go to whom? Defined before the hire starts, communicated on day one.
Phase 2: Before the Start Date (10 Steps)
☐ 6. Provision all tool access. Slack, GitHub or Jira, any specialized software. All invites sent 3 days before start date.
☐ 7. Create the standup channel. #standup or #[team]-updates. Post the format (Done/Doing/Blocked). Set expectations for when it's read and responded to.
☐ 8. Write the onboarding document. Architecture overview, team structure, tool links, local environment setup, definition of "done," escalation protocol. One Notion page.
☐ 9. Prepare the first task. A small, bounded task for day one — reveals how they navigate an unfamiliar codebase or system without the pressure of a deliverable. Not "implement the payment system" — "fix this specific minor bug."
☐ 10. Schedule the day-one orientation call. 30 minutes, video. Block it on both calendars before day one.
☐ 11. Schedule the weekly check-in. Same time, same day, every week. Block it now so it's never a scheduling puzzle.
☐ 12. Write the brand voice or style guide (for non-technical roles). For support, EA, VA, or content roles: a 1–2 page document describing tone, phrases to use, phrases to avoid. Without it, training takes 3× longer.
☐ 13. Build the macro library (for support roles). 20–30 response templates for the top ticket types. Have them ready before day one.
☐ 14. Document the top 15 recurring workflows (for ops roles). Step-by-step instructions with screenshots for the most common processes. This is the single biggest accelerator for operations, legal, and admin role onboarding.
☐ 15. Confirm equipment is configured (F5 handles this). For F5-placed professionals: F5 configures dedicated hardware with all required software before the professional's start date. Confirm with F5 that setup is complete 2 days before start.
Phase 3: Day One (4 Steps)
☐ 16. 30-minute orientation video call. Cover: company context, product overview, team introductions, first task assignment, standup format reminder. Record it for future reference.
☐ 17. Codebase or system walkthrough. For technical roles: architecture overview, key patterns, where things live. For ops roles: the primary systems they'll use and how workflows connect.
☐ 18. First standup post from the hire. Ask them to post their first standup at end of day one — Done (orientation completed, environment set up), Doing (first task), Blocked (anything blocking the first task). Sets the habit immediately.
☐ 19. Confirm all tool access is working. Ask at the end of the orientation call: "Is everything working? Any access issues?" Resolving access problems on day one prevents lost days.
Phase 4: Week One (3 Steps)
☐ 20. Review every standup within 2 hours. This establishes that standups are read and acted on — not performative. Unread standups become useless within a week.
☐ 21. Give specific feedback on the first task within 24 hours. Specific, written, actionable. Not "looks good" — "the error handling on line 47 should catch the specific exception type, not the general one. Here's why." Specific feedback in week one establishes quality standards.
☐ 22. Identify and resolve any blockers immediately. If the day-one standup says "Blocked: waiting on database credentials" and you don't respond for 3 days, you've taught the hire that blockers don't matter. Resolve same day.
Phase 5: Day 30 (3 Steps)
☐ 23. Run the 30-day check-in call. 30 minutes, video. Four questions: How is the work going from your perspective? What's working in our communication setup? What's making it harder than it needs to be? How does the actual work compare to what you expected?
☐ 24. Assess against the day-30 milestone. Review the 90-day expectation document. Did they hit the day-30 milestone? If yes: what's on track for day 60? If no: is it a capability gap or a process gap? Most day-30 misses are process problems, not capability problems.
☐ 25. Decide: proceed, adjust, or escalate. If the hire is on track: proceed with the plan. If there are gaps: adjust the onboarding structure and give explicit feedback. If performance is consistently below standard: contact F5 — F5's replacement guarantee covers this exact scenario within 7–14 days at zero cost.
Learn how F5's managed hiring process works from brief to day 30 or contact F5 to start the hiring process.
Frequently Asked Questions
What is the most important thing to prepare before a remote hire starts? A written 90-day output expectation — specific deliverables at 30, 60, and 90 days.
What tool access should be provisioned before day one? Communication (Slack), project management (Linear/Jira), version control or primary software, and any specialized tools. All before start date.
How do I set up a daily standup? Slack channel, Done/Doing/Blocked format, manager reviews within 2 hours and responds to blockers same day.
How do I write a 90-day expectation? One paragraph, three milestones, specific deliverables not vague qualities.
What should be in an onboarding document? Architecture overview, team structure, tool links, local setup guide, definition of done, escalation protocol.
What do I do at the day 30 check-in? Four questions: how's the work going, what's working in communication, what's harder than expected, how does it compare to expectations.
What if the hire isn't working out at day 30? Contact F5 — replacement within 7–14 days at zero cost is included in the engagement.
Frequently Asked Questions
What is the single most important thing to prepare before a remote hire starts?
A written 90-day output expectation — one paragraph describing what a successful hire will have built, shipped, or owned 90 days from their start date. Without a written expectation, neither the manager nor the hire knows what success looks like. Everything else — tool access, communication protocols, onboarding docs — is operational. The 90-day expectation is the foundation.
What tool access should be provisioned before a remote hire's first day?
At minimum: communication tool (Slack invite sent, channel access granted), project management tool (Linear, Jira, or Asana workspace access), version control or relevant software access (GitHub org, Figma, Google Workspace), and any specialized software the role requires (design tools, engineering environments, CRM, ERP). All provisioned before day one — waiting on IT access wastes the first week.
How do I set up a daily standup format for a remote hire?
Choose a Slack channel (or create one — #standup or #[team]-updates). Define the format: 3 bullet points at the start of their workday — Done (completed since last standup), Doing (working on today), Blocked (waiting on someone or something). Ask the manager to read and respond to blockers within 2 hours. Run this from day one — it establishes visibility and discipline simultaneously.
How do I write a 90-day expectation document?
One paragraph, three milestones. Day 30: what they should understand and have completed by the end of month 1. Day 60: what they should be independently producing by the end of month 2. Day 90: what they should own and be measured against by the end of month 3. Specific deliverables, not vague qualities. 'Merged 3 PRs independently' not 'comfortable with the codebase.'
What should be in an onboarding document for a remote hire?
Architecture overview (how systems connect), team structure and who owns what, links to all relevant repositories, documentation, and design files, the tech stack and how to set up a local development environment, the definition of 'done' for tasks in this team, and the escalation protocol (who to contact for what type of question). One well-structured Notion page replaces 3 weeks of questions.
How do I handle time zone expectations with a remote hire?
Define overlap hours explicitly before the hire starts — not on day one, before the offer is accepted. State the expected start time and end time in U.S. time zone. F5 configures all placed professionals on the client's specified overlap schedule before their first day. There should be no ambiguity about when the person is expected to be available for real-time communication.
What performance check-in should I schedule on day 30?
A 30-minute video call with a simple agenda: (1) How is the work going from your perspective? (2) What's working well in our communication setup? (3) What's making it harder than it needs to be? (4) How does the actual work compare to what you expected? This call catches misalignments before they compound. Most remote engagement problems are visible at day 30 if you look for them.