The 30 Day Geo Agnostic Hiring Sprint

Who This Is For

• Founders and COOs who need leverage yesterday and are tired of recycling the same domestic candidate pool.
• Ops and CX leaders battling “accent rejection” loops and looking to hire for skill without inflating costs.
• Team leads who want a structured way to run paid trials and ramp hires fast across time zones.

Before You Start

What you gather now saves you weeks later. Start with the messy docs you already have and the truth you usually ignore.

Pull your latest job description or role notes for 1–2 roles. Don’t beautify them yet. I want the raw list of tasks, tools, and “it’d be nice if...” lines. That rawness shows where bias and fluff hide.

Grab the last 10 candidate rejections and, if you have it, the reason each one was passed on. If you don’t store that ... start today. We’ll use this to spot “style over substance” patterns that quietly block great offshore hires.

Pull your onboarding checklist or new hire docs. Even if it’s a Notion graveyard, it tells me what access, SOPs, and tools actually gate productive work.

Write your top 3 must have outcomes for the role in the first 60 days. Not activities. Outcomes. “Reduce churn on Tier 1 tickets by 10%.” “Ship 3 production ready features.” “Book 15 qualified demos.” These are your north stars.

What You'll Build

By the end of this tutorial, you will have a week by week hiring machine that ignores accents and optimizes for output. Picture this: your role scorecard lives in a one pager. Your job post is geo agnostic, localized for three regions with realistic time zone expectations and comp bands. Your screening kit runs on rails with async video, structured questions, and a paid skills test with a clear rubric.

You’ll run a simple weighted scoring model that ranks candidates objectively. No “great energy” hand waves. Tie breakers are explicit. Red flags are named. And when you make an offer, your 14 day ramp unlocks access, sets daily goals, and tracks outcomes with a lightweight dashboard.

In 30 days, you’ll know if your new hire is a keeper. You’ll also have a repeatable playbook you can hand to a coordinator and say “run the sprint.”

1) Week 1: Define and De Bias the Role

Start here because unclear roles create bad hires at any price point. If you don’t define outcomes up front, you’ll hire the smoothest voice on Zoom and wonder why nothing ships.

First, convert your job description into an outcomes based scorecard. Read your JD once and highlight verbs that map to business results. Ship. Resolve. Book. Reduce. Ignore “excellent communication” unless it ties to a measurable outcome like “CSAT 4.6+.”

Write 5–7 outcomes the role must deliver in 60 days. Make them specific and measurable. Include how you’ll verify them. This becomes your north star for sourcing, screening, trials, and onboarding.

Remove location and accent language entirely. Replace with time band expectations and collaboration windows. “You must be online 2 hours overlap with EST” is valid. “Must be US based” is lazy unless there’s a legal or customer contract reason.

Define must haves and nice to haves. Must haves are non negotiable for day 1 performance. Nice to haves go in the tie breaker bucket. Keep this honest or you’ll shrink your talent pool for no reason.

Map tools and environment. If your stack is Jira, Linear, HubSpot, Zendesk, or Asana ... name it. But don’t overfit on brand names. “Issue tracker experience” beats “must have Linear.”

Name the three risks that historically tank hires in this role. Missed deadlines. Poor QA. Inability to work async. Call them out in the scorecard. You’ll design your trial to test these.

Here’s a copy paste scorecard template you can fill in now:

Role Scorecard

• Role: [Title]
• Manager: [Name]
• Collaboration Window: [e.g., 2–4 hours overlap with EST]
• Must Haves:

- [Skill] at [level] with [years or proof type]

- [Skill] at [level] with [years or proof type]

• Nice To Haves:

- [Skill or domain]

- [Language or tool]

• 60 Day Outcomes:

1) [Outcome] measured by [metric] target [X]

2) [Outcome] measured by [metric] target [X]

3) [Outcome] measured by [metric] target [X]

4) [Outcome] measured by [metric] target [X]

5) [Outcome] measured by [metric] target [X]

• Risks To Monitor:

- [Risk 1] detection signal [how you’ll see it]

- [Risk 2] detection signal [how you’ll see it]

- [Risk 3] detection signal [how you’ll see it]

• Trial Project:

- Summary: [1–2 lines]

- Deliverables: [list]

- Acceptance Criteria: [bullet list]

Now sanity check compensation and region. Pull benchmarks for three regions that match your role and language needs. For example: Philippines, India, and LATAM for CX roles. Eastern Europe, India, and LATAM for engineering. Do not copy US bands into global markets. You’ll either underpay and repel or overpay and decimate margins.

Pick 2–3 target regions based on skills availability, comp bands, and time zone fit. You’re not excluding others ... you’re focusing your outreach copy and platform selection.

Run a bias scrub. Anywhere you wrote “exceptional English” rewrite to “clear written documentation and concise updates.” Anywhere you wrote “native level” rewrite to “able to resolve customer issues at CSAT 4.6+ with low repeat contacts” or “able to write production ready code meeting our test coverage.”

Close Week 1 by socializing the scorecard with your team. Get alignment now. Vibes later. If someone pushes for “but they really need a neutral accent” ... ask how that ties to outcomes and metrics. If the answer is “our customers hang up on accents” ... great. We’ll address that with workflows and tooling in onboarding rather than pre filtering 90% of the talent pool.

By the end of this step you have a crisp one pager that defines success. This is the foundation for sourcing at scale next week.

2) Week 2: Source and Screen at Scale

Now that you know what “good” looks like, publish like you mean it. Volume without structure is chaos. Structure without volume is crickets. We want both.

Start with a de biased, geo agnostic job post. Lead with outcomes and growth. Name your collaboration window, comp range tailored per region, and hiring timeline. Avoid “must be native,” “North America only,” or “perfect accent.” You’re hiring for output and clarity, not phonetics.

Localize copy for 3 target regions. Same role ... different norms. In India, mention UPI payroll options and flexibility across IST evenings. In the Philippines, mention HMO stipends and 13th month alignment. In LATAM, mention USD payouts and public holiday swaps. Always publish comp ranges. It signals seriousness and filters faster.

Choose platforms by role. For CX and back office: OnlineJobs.ph, JobStreet, Upwork project catalog, and local Facebook groups curated by BPO alumni. For engineering: LinkedIn, Wellfound, Stack Overflow Jobs, Djinni, WeLoveDevs. For GTM roles: LinkedIn, Remotive, and niche communities like GrowthHackers Jobs.

Post with platform specific hooks. On LinkedIn, lead with outcomes and a short loom link. On OnlineJobs.ph, add the word “MANGO” in the subject line to filter skim readers. On Upwork, publish as a short term contract linked to your paid trial with conversion to full time.

Here’s a copy paste job post you can adapt per region:

Role: Customer Support Specialist Remote

We help [ICP] solve [problem]. You will own outcomes not tickets.

What You’ll Achieve in 60 Days

• Reduce repeat contacts by 15% through better first reply resolution
• Maintain CSAT 4.6+ across email and chat
• Document 10 new macros and 5 help center articles

How We Work

• Collaboration window: 2 hours overlap with EST
• Tools: Zendesk, Notion, Slack
• Clear daily goals ... async first ... paid trial included

Compensation

• Philippines: PHP [range] monthly plus HMO stipend and 13th month
• India: INR [range] monthly plus performance bonus
• LATAM: USD [range] monthly plus internet stipend

How To Apply

• Share 3 examples where you reduced customer effort
• Record a 90 second async video answering: “Tell me about a time you fixed a broken process”
• Complete our 60 minute paid skills test within 72 hours of invite

Next, set up a structured screening kit. This is non negotiable. It’s how you scale without drowning.

Write 5 screening questions tied to your scorecard. Ask for specifics and proof. “Describe a macro you wrote that reduced handle time by X.” “Link to a loom where you walked a teammate through a fix.” “Share a before after metric you influenced.”

Design one async video prompt. Keep it short. The goal is how they structure information and whether you can understand them clearly enough to collaborate ... not whether they sound like a Netflix narrator. Provide a simple script and a 90 second limit.

Create a 60–90 minute paid skills test. Make it realistic, small, and evaluable. For CX: a mock inbox with 10 tickets including one ambiguous edge case and one angry customer. For engineering: a small feature with tests and a simple bug to fix. For SDR: write 3 emails to different personas with one objection handling task.

Standardize your evaluation rubric. For each element ... define what a 1, 3, and 5 looks like. Tie each to outcomes, not style. Put this into a simple form your reviewers can complete in under 5 minutes per candidate.

Here’s a screening kit you can copy:

Screening Questions

1) Share a metric you improved in your last role. What changed and how did you do it

2) Link to an example of documentation you wrote or improved

3) Describe a complex customer issue you solved. What made it complex

4) What hours can you overlap with EST daily

5) What’s your monthly compensation expectation in [local currency] and USD

Async Video Prompt

• Record up to 90 seconds answering: “Tell me about a process you optimized. What was broken, what did you change, and what result did it drive” Use loom or phone. We evaluate clarity and structure.

Paid Skills Test Summary

• Deliverables: [list]
• Time Cap: 60–90 minutes
• Pay: [fair rate] upon submission
• Acceptance Criteria: [explicit bullets]

Finally ... operationalize. Use an Airtable or Google Sheet with status stages: Applied ... Screen Qs ... Video ... Skills Test ... Panel ... Offer. Limit WIP to avoid bottlenecks. Calendar blocks daily to review batches. If a candidate stalls 72 hours at any stage ... auto close.

End Week 2 with 15–30 candidates in process, 5–10 at skills test, using the same rubric across reviewers. Next week we score and select.

3) Week 3: Skills First Assessment

This is where you make or save thousands. Paid trial projects reveal truth quickly. Be generous. Be clear. Be objective.

Start by crafting a paid trial brief anchored to your scorecard outcomes. Keep it scoped to 60–90 minutes for assessment and 6–10 hours for finalist trials. Both are paid. Respect time and word will travel ... your funnel gets better.

Define acceptance criteria like a contract. For each deliverable, write what “good” means. Include examples and red lines. “We expect 90%+ macro coverage across the 10 mock tickets.” “We expect green tests with 80% coverage and no lints.” “We expect 3 emails that reflect persona pain from these 2 sources.”

Give all candidates the same data pack. For CX: a sample knowledge base, tone guide, macro examples, 10 mock tickets in CSV. For engineering: a repo with README, failing test, and feature spec. For SDR: ICP blurb, 2 ideal customer profiles, and a call objection list.

Set a clear clock. 72 hours to accept and return the assessment. State the pay and payment process up front. Pay fast. Your reputation compounds.

Create a weighted scoring model that prioritizes work samples and outcomes over communication style. You are not selecting radio hosts. You are selecting people who produce results in your environment.

Here’s a scoring model to copy:

Candidate Weighted Score Model 0–100

• Skills Test Quality 35 points

- Meets acceptance criteria 0–15

- Decision making and edge case handling 0–10

- Documentation clarity 0–10

• Experience Relevance 20 points

- Similar environment or tools 0–10

- Demonstrated outcome improvements 0–10

• Async Communication Clarity 15 points

- Structured updates 0–10

- Understandable spoken summary 0–5

• Speed and Reliability 15 points

- On time delivery 0–10

- Responsiveness 0–5

• Cultural and Work Style Fit 10 points

- Async discipline and collaboration window match 0–10

• Bonus Impact Signals 5 points

- Proactive improvement suggestions 0–5

Tie Breakers

• If scores are within 3 points: run a 6 hour paid live mini project
• If still tied: select the candidate with stronger outcome evidence in past roles

Red Flags

• Missed deadlines without notice
• Overconfident answers with poor artifacts
• Unable to follow brief or acceptance criteria

Run calibration. Have two reviewers score the first five assessments independently ... then compare deltas. Adjust rubric language so both reviewers land within 5 points on each dimension. Calibration now prevents chaos later.

Invite top 2–3 candidates to a finalist paid mini project. Make it a small piece of real work you need done anyway. Time box it. Ship the accepted output internally. You learn fast whether they can produce value in your actual stack.

When you select your offer recipient, send a clear offer email with role, comp, collaboration window, trial to full plan, and the 14 day onboarding outline. Also thank and pay non selected finalists quickly. They might be your next hire.

End Week 3 with a signed offer, a backup candidate warm, and your onboarding plan queued.

4) Week 4: Onboard Fast ... Measure Faster

Most teams think onboarding is doc access and a welcome call. That’s the appetizer. We want the main course: measurable outcomes inside two weeks.

Start with a 14 day ramp plan. Break it into daily goals, tool access, SOP links, and three outcome checkpoints. Keep the footprint small and focused. New hires shouldn’t read 200 pages to do one task.

Here’s a copy paste 14 day plan: