Most remote hires that fail don't fail because of skill. They fail in the first two weeks, when a capable developer sits waiting for access, guessing at priorities, and wondering whether anyone noticed they started.
Here's the first-week checklist we use when placing developers with startup teams. It works whether your new hire is in the next time zone or eight hours away.
Before day one
Accounts ready, not requested. Repo, CI, cloud console, issue tracker, chat, password manager. If access takes three days of tickets, that's three days of paid waiting.- A working local setup doc. Have the last person who joined update it. If nobody can get the app running from the README in an hour, fix the README before the hire starts.- A named buddy. Not the CTO. Someone at their level who expects questions and has time blocked to answer them.- Agreed overlap hours. Write down the two to four hours when they'll be reachable live.…