CVs and interviews tell you what a developer says they can do. A short paid trial shows you how they actually work with your code, your tools and your team. Forty hours, roughly one working week, is enough to judge the things that decide whether a remote hire will work out.
Before the trial starts
- Pick one real task from your backlog that is small, useful and finished within the week.
- Prepare access in advance: repository, staging environment, task board and team chat.
- Write a short brief: what done looks like, who to ask, and your coding standards.
- Agree the hours that overlap with your team, and the time of a daily check-in.
Day 1: setup and questions
Watch how quickly the developer gets the project running and what they ask. Good questions about edge cases, data and existing patterns are a strong early sign. Silence on day one is often a warning.
Days 2 to 4: the work
- Do they push small, frequent commits with clear messages?
- Do they write a short update each day without being chased?
- Do they follow your existing structure, or rewrite things that did not need changing?
- Do they raise blockers early, or wait until the deadline?
Day 5: review and handover
Ask for a pull request with a short description of what changed, how it was tested and what is left. Review it together on a call. How someone takes feedback in that call tells you a lot about the next six months.
How to score the trial
- Quality: is the code readable, tested and in line with your standards?
- Communication: were updates clear and on time?
- Ownership: did they move the task forward without hand-holding?
- Fit: would your team be happy to work with this person every day?
After the trial
If the trial went well, start with a clear first month: goals, a regular review and one person on your side who owns the relationship. If it did not, you have lost one week instead of three months, and you know exactly what to look for in the next candidate.



























