See How A Developer Works Before You Commit
Interview the developer, give them real tasks in your own repository and judge the result. Continue only if you are satisfied.
The Real Problem With Hiring Developers
An interview shows how someone talks about work. It does not show how they do it.
Interviews Reward Talking
A confident answer about architecture is not the same as a clean pull request.
Tests Are Not Your Codebase
A take-home task is tidy. Your system has history, shortcuts and constraints.
You Find Out Too Late
By the time a poor fit is clear, you have spent onboarding time you cannot get back.
How The Trial Runs
- 1
Tell Us The Role
Share the stack, the seniority and the work you need done.
- 2
Interview The Developer
We shortlist. You interview and choose the person.
- 3
Work On Real Tasks
After the NDA is signed, the developer joins your repository and tools.
- 4
Decide
At the end of the trial, continue month to month or stop.
Pay Only If You Are Satisfied
The trial exists so you can judge real work before you commit to anything.
If you are satisfied at the end, the engagement continues on month-to-month terms. If you are not, you stop. There is no exit fee.
The exact terms, including the length of the trial and what happens at the end, are set out in the agreement you sign before the trial starts. Read it, and ask us about anything that is unclear.
What Is Included
A Developer You Chose
You interview the developer before the trial begins.
Work In Your Tools
The developer works in your repository, tracker and chat.
NDA Before Code Access
Confidentiality is signed before anyone sees your code.
Code You Own
All code written for you belongs to you.
Ready To See Real Work?
What Success Looks Like
Decide what you are looking for before the trial starts. It makes the decision at the end easier.
Signs to continue
- Questions are asked early, before work goes the wrong way
- Pull requests are small and easy to review
- Review feedback is acted on
- The developer follows your conventions
- You spend less time explaining as the trial goes on
Signs to stop
- Long silences followed by large changes
- The same review comment has to be made twice
- Blockers are reported late or not at all
- Work passes locally and fails in your pipeline
- You are doing the thinking for two people
Who This Is For
Teams Burned Before
You have hired remote developers who looked good on paper. You want proof this time.
Founders Hiring For The First Time
You are not sure how to judge a developer. A trial lets the work speak.
Engineering Leads Under Pressure
You need capacity, and you cannot afford a wrong hire in the middle of a release.
Start Your Trial
What we need from you
- The stack and the role
- The kind of tasks you have in mind
- Who will review the work
What happens next
- We reply within two working days
- You review a shortlist
- You interview, then the trial begins
Prefer To Talk It Through First?
Speak with our team about the role before you request a trial.
Related Insights
View All Articles- HiringHow to brief a remote developer so week one is productiveA short checklist covering access, context and a first task that is small enough to finish.
- Project ManagementStaff augmentation or a dedicated team: a decision you can make in ten minutesFour questions about ownership, runway and management time that settle the choice.
- ModernisationSigns your legacy platform has become a business riskWhat to look for in release frequency, incident history and hiring difficulty.
Frequently Asked Questions
You pay only if you are satisfied and choose to continue. The exact terms are set out in the agreement you sign before the trial starts.
Yes. You interview every candidate and choose the person you want to work with.
You do. All code written for you belongs to you, and the work happens in your repository.
You tell us and the engagement ends. There is no exit fee.
Tell us what is not working. We will propose a replacement for you to interview.