10 Mistakes US Employers Make Hiring Filipino VAs (and How to Avoid Them)

The 10 Most Expensive Mistakes US Employers Make Hiring Filipino VAs

After watching hundreds of small-business owners hire Filipino virtual assistants, the same ten mistakes come up over and over. None of them are obvious in advance. All of them waste money, erode trust, and often end in a failed hire that leaves the employer convinced "outsourcing doesn't work for us" — when the real problem was a correctable process issue.

This is the candid version of the hiring playbook. Read it before your first hire if you can. If you're already mid-hire, read it to course-correct.

Mistake #1: Optimizing for the Cheapest Rate

The single most expensive mistake. Employers see "hire a Filipino VA for $3/hour" and convince themselves that's the right target. The reality: at $3/hr, you're competing against zero serious candidates. The good Filipino VAs are already working for US clients at $6–$12/hr.

What you get at $3/hr: someone who just quit the BPO industry, has never worked directly with a US SMB, and will leave the moment they land a $5/hr gig elsewhere. You'll spend 40 hours of your own time training them, then repeat the cycle in 4 months.

The fix: budget $6–$9/hr for a first hire. This puts you in the top 25% of employers and attracts experienced candidates who'll stay for years. For complete cost analysis, see our real cost breakdown.

Mistake #2: Writing a Vague Job Post

"Looking for a virtual assistant to help with various tasks" is a non-post. It attracts spray-and-pray applicants who apply to 50 jobs a day with a boilerplate cover letter.

What to write instead: a specific role title, the 5–10 tasks they'll own, the tool stack, expected hours and timezone, required experience, and an explicit rate range. "CS Lead for a Shopify apparel brand, 40 hrs/week on 9 PM–6 AM PHT shift, Gorgias + Shopify experience required, $8–$10/hr depending on experience."

Specificity attracts serious candidates and filters out everyone else. Applications may drop from 100 to 25, but quality rises 5x.

Mistake #3: Skipping the Paid Test Task

Interviews tell you who's good at interviews. Paid test tasks tell you who's good at the work.

Every hire, without exception, should include a 1–3 hour paid test ($25–$75) on a realistic piece of work. Not a contrived test ("write a poem about our brand") — an actual task you'd assign in week one.

The paid test catches 30–40% of candidates who sounded great in the interview but can't actually do the work. It also tells you how they ask questions, how they handle ambiguity, and how polished their deliverables are. The $75 cost is cheap insurance against a $2,000 mis-hire.

Mistake #4: Day 1 Without Proper Access

A surprisingly common failure mode. You extend the offer, they accept, day one arrives, and they're locked out of half the tools they need because IT access takes three days.

Result: they sit idle, bill hours for setup, and feel undervalued on their first day. Momentum lost.

The fix: do access provisioning 3–5 days before start. Shared password manager, email alias, Slack, CRM, Gorgias, Shopify — all live on day one. If there are security approvals needed, front-load them.

Mistake #5: Unclear Expectations About Shift Timing

Manila is 12–15 hours ahead of US time zones, depending on DST. If you need US business hours coverage, your VA works 9 PM–6 AM PHT or similar. This is a meaningful life choice for them — working through the Philippine night.

Some candidates agree to overnight work in the interview because they're desperate, then quit 2 months in because they can't sustain it. Other employers assume "remote" means the VA works whenever; the VA assumes the opposite; responses disappear for 8 hours and the employer panics.

Fix: write the exact shift into the job post, confirm it in the interview, and confirm it again in the offer. "This role requires 9 PM–6 AM PHT availability Monday–Friday" — ambiguity-free.

Mistake #6: Under-Documenting

Many founders treat documentation as "busywork" and try to operate on tribal knowledge. This works at 0–1 VAs. It fails at 2+. At 5, it's crisis-level.

What proper documentation looks like: every recurring process has a Loom video paired with a short written SOP. Every tool has a cheat sheet with login details (in a password manager), common tasks, and escalation paths. Every decision worth documenting is in a running decision log.

Make the VA a partner in documentation — they can write SOPs from your Looms, then you edit. Within 90 days of a new hire, you should have 20+ core SOPs written by them.

Mistake #7: Managing Like They're in the Room

Remote management is different from in-person management, and different again when there's a timezone flip. Founders who rely on ad-hoc drive-by questions burn out both sides.

The async communication pattern that works:

• Daily standup in writing (3 bullets, takes 3 minutes)
• Overnight Loom recordings for context rather than video calls at inconvenient hours
• One scheduled weekly live sync per week, not scattered daily meetings
• Clear ownership of tasks in a project tool — no "Slack message = task"

For the full management framework, see our remote team management guide.

Mistake #8: Not Giving Feedback

Filipino professional culture is deferential. They won't tell you your instructions are unclear. They won't push back when you change direction. They'll often absorb blame for your process issues.

You have to actively invite feedback: "If anything I asked for didn't make sense, please tell me. It's my job to give you clear direction — your job is to flag when I don't." Repeat this monthly.

Equally: you have to give feedback. Filipino VAs are motivated by growth and clear expectations. Silence is interpreted as disapproval. A weekly written "here's what's working, here's one thing to improve" is the minimum bar.

Mistake #9: Skipping the 13th-Month Pay

In Philippine labor culture, a 13th-month pay (one month's salary paid in December) is standard for employees and strongly expected even for contractors with long-term clients. US employers often don't know this exists.

Not offering it signals you don't understand (or don't care about) their context. Offering it — especially voluntarily, without prompting — signals you treat them as part of the team.

The cost is trivial (one month's pay once a year), the retention impact is enormous. See our Philippine holidays and cultural guide for the full expectations around Philippine workforce practices.

Mistake #10: Treating Them as Replaceable

The cheapest-feeling instinct — "if this one doesn't work out I'll just hire another" — is also the most expensive.

Every time you cycle through a Filipino VA you lose: 30–60 days of productivity, the training investment, the context they've built, the relationships with your customers and team. The replacement has to learn everything from scratch.

Retention-focused employers outperform churn-and-burn employers by roughly 3x on actual productivity per dollar spent. Pay above market, invest in growth, give real feedback, preserve cultural norms, and promote from within. A Filipino VA who stays 5 years is often more productive than the same employer's third US hire.

The Fix Summary

1. Pay mid-market, not rock-bottom
2. Write specific, tool-named job posts
3. Always run a paid test task
4. Provision all access before day 1
5. Lock in shift expectations in writing
6. Document everything with Looms + SOPs
7. Run async-first management rhythms
8. Invite and give feedback explicitly
9. Pay 13th-month in December
10. Treat retention as a metric

Do these ten things and your Filipino hiring experience will look radically different from the horror stories. Most "outsourcing doesn't work" stories trace back to 2–3 of these mistakes, not to the talent.

Ready to Hire Right?

Post your role on WorkFil — write a specific job post, budget fairly, and you'll have quality applications within 48 hours. For the full hiring playbook, see our complete Filipino VA hiring guide.