Most failed VA hires fail on a job nobody wrote down. I'm building https://t.co/Hsecu96gVb to fix the finding half: describe the role in plain English, get matched with vetted Filipino specialists. The managing half I post about here, for free.
Interview question that actually predicts anything: ask them to describe the last thing they got wrong at work and what changed afterwards. You learn more from that than from any strengths answer.
@__Churchgirl The hard part isn't deciding to delegate, it's writing down a task you've only ever done on autopilot. I'd record myself doing it once and hand over the video.
Stop lengthening the interview and pay for a small test task instead. Two hours of real work tells you more than an hour of questions, and it respects the time of someone who is probably doing this after their day job.
@e_janitors_001 The trap isn't refusing to delegate, it's delegating the task without the context. Then you're stuck fixing it, which feels like proof you should've done it yourself.
@carsondimond A generalist recruiter can't screen a Shopify dev because they can't read the test. I'd have someone technical write the trial task, not the recruiter.
@vineerpasam@flytradr_guy AI doesn't cover the judgment calls though. A tool won't tell you the invoice looks wrong. That's still the reason to hire, not the ticket volume.
@andywalkerhq The flip side nobody budgets for: hiring ahead means paying someone to be underused for a month while you feed them work. Cheaper to test the seat with a part-timer first.
@sachintwtss One paid trial task on a real ticket tells you more than six rounds ever will. I'd give them a scoped bug from your actual backlog and see how they ask questions.
@ahmedafatah@Oliver_Clingain The trick I use: hand over the whole task, not the fast half. If you keep the "I'll just do this bit" part, they never learn where it actually breaks.
@WojteksGrandson The 5-minute read tells you if you like them, not if they can do the work. Different signals. I'd still make the confident ones do a paid task before the offer.
@nico_jeannen@__cski Bad ones ask you what to do next. Good ones tell you what they did and where they weren't sure. Watch that in week one, not the interview.
Job posts asking for a rockstar ninja unicorn get you applicants who are good at reading job posts. Describe the actual tasks in plain words. The people who can do them will recognise themselves.
@Killertom63 Yep. Ask for their retention graph on a video they cut, not a reel. If they can't tell you where people dropped and why, they're editing pretty, not editing for watch time.
@virtualbacon Hiring going up while openings fall usually means backfills, not growth. Companies replacing one seat, not adding three. That's the tell.
@Rachels_Midlife The tell is if you can't write their first-week tasks without inventing them. If you're guessing at the to-do list, the role isn't the gap yet.
If you cannot describe what the person does on a normal Tuesday, you are not ready to hire. You are ready to write that down, which is a different job and takes an afternoon.
@KuanHing@hustle_fred Depends what broke though. Skill gap you can fix in a week, judgment or honesty you can't. I'd only coach the first kind, cut the rest fast.
@ugcwithmichelle The VPN gap is the real killer here. I'd have whoever posts log in from the same static IP every time, not just any VPN node, so Meta reads it as one consistent location.