Hiring remotely is not harder than hiring locally. It is less forgiving. You lose the informal signals that paper over a vague brief, so anything you leave unspecified stays unspecified.
This is the sequence we use, whether you run it yourself or we run it for you.
Step 1: Log your week before you write a job description
For five working days, write down every task you do that someone else could do, with a rough time against it. Do not filter. The list will be longer and stranger than you expect.
Then sort it into three piles: work that is repetitive and rules-based, work that needs judgement you can teach, and work that only you can do. The first pile is the seat. The second pile is what the seat grows into in month three. The third pile is what you get back.
A job description written from this list describes real work. One written from a template describes a category.
Step 2: Decide the model before you decide the person
There are three routes, and they fail in different ways.
- Direct on a freelance marketplace. Cheapest headline rate, most work for you. You screen, you test, you onboard, you supervise, and you repeat all of it if the hire leaves. Works well if you enjoy hiring and have the time.
- A staffing or recruitment firm. They find and place someone, then step back. You get a shortlist without the search, but management stays yours.
- A managed team. The specialist is recruited, vetted, onboarded and supervised on your behalf, and replaced if it does not work. You trade a higher rate for not owning any of that. This is how Virtual Level Up works.
There is no universally right answer. There is a wrong one, which is picking a model by price without noticing which tasks it transfers to you.
Step 3: Write a test that looks like the job
This is where most hiring processes quietly fail. A conversation tells you whether someone interviews well. A task tells you whether they work well.
The test should be short, paid, and shaped like the real thing. Some examples that work:
- Admin: here are twelve messy emails and a calendar. Triage them, draft three replies in this tone, flag what needs a decision.
- Cold calling: here is a script and five mock objections. Record yourself handling them.
- Design: here is our brand file and one real brief. Produce two options.
- Development: here is a real ticket from our backlog and repository access to a sandbox. Open a pull request.
- Payroll prep or bookkeeping: here is a month of sample data with three deliberate errors in it.
Pay for it. It takes real time, unpaid tests attract the wrong candidates, and it signals how you will treat the person once hired.
Mark the work for the thing you actually care about. With an admin test, that is usually not whether the drafts are perfect. It is whether they caught the email that needed escalating.
Step 4: Interview for reporting, not just skill
The test covers competence. The interview should cover the thing that decides whether a remote hire works: what happens when they get stuck.
Ask directly. "Walk me through a time you could not finish something on time. What did you do first?" You are listening for whether they flagged it early or went quiet. Going quiet is the single most common failure mode in remote work, and it is very hard to coach out.
Also settle the practical things before anyone is excited: exact working hours in your time zone, internet and power backup arrangements, how they prefer to receive feedback, and what they want to be doing in two years.
Step 5: Get the legal and payment side right
In most arrangements a Philippine specialist works as an independent contractor, which is straightforward but not free of obligations. Put a written agreement in place covering scope, hours, rate, confidentiality, intellectual property assignment and notice on both sides. Decide the payment method and currency before the first invoice, not after.
If you are hiring directly, check your own jurisdiction's rules on contractor classification. If you are hiring through a managed team, this sits with them; confirm that in writing rather than assuming it.
Step 6: Onboard as if they will be there for years
The first two weeks decide the next two years. Three things matter more than anything else.
Access, properly. Use a password manager with role-scoped permissions. Never share credentials in chat or a spreadsheet. Set up the removal process on day one, not on the last day.
Written process, from day one. Every task you explain gets written down as a procedure in your own drive, by the person learning it. This takes about 15% longer in week one and saves you the entire onboarding again when someone moves on. The process should belong to your business, not to one person's memory.
A reporting rhythm. An end-of-day note covering what is done, what is in progress and what needs you. Two minutes to write, two minutes to read, and it removes almost every "what is happening with..." message.
A realistic timeline
Scoping takes a few days of paying attention. Sourcing and testing takes one to three weeks depending on how specialised the seat is, and a senior developer takes longer than an admin assistant. Onboarding to genuine independence takes four to eight weeks for most seats.
Anyone promising a specialised hire placed and productive in 48 hours is describing a body, not a match.
If you would rather not run this yourself, that is the whole job we do. Tell us which seats you need and we will run steps two through six for you.
