Looking for work with a US company? Apply to the Rolemote talent roster — free →

At a glance

Highest score first. Scores within 2 points are level: when we had the screener read the same two applications again, the gap between them moved by up to 2. A must-have in the brief (below the list) costs 5 points when the application does not show it and 2 when it only partly does.

  1. Maricel G.Philippines · asking $1,050Goes on to the interviewLevel with Julián P. (86 vs 85 is too close to call), though stronger on the experience (85 vs 82).86/100
  2. Julián P.Argentina · asking $1,250Goes on to the interviewAhead of Rochelle B. mainly on the work sample (84 vs 62).85/100
  3. Rochelle B.Philippines · asking $800Stops here64/100

2 of 3 clear 70, the score an applicant needs to go on to the written interview. A real shortlist only holds people who clear it and then the interview; the one below it is shown so you can see what the screener turns down.

The brief they were screened against

Role: Lead Generation Specialist · Band: $750–1,250/mo

Must-haves: builds B2B prospect lists to a defined ICP, verifies emails before anything is sent, Apollo, LinkedIn Sales Navigator or Clay, can say why a contact qualifies

Nice to have: first-touch sequence writing, deliverability basics (warm-up, bounce rates), CRM hygiene in HubSpot

Scored on 2026-09-23 by the AI screener that grades real applicants: the lead-generation-specialist rubric, run on claude-sonnet-4-6. Nothing below was edited afterwards — including where it went against a candidate. The rubric and weights are published.

Maricel G. · 1 of 3

SCREEN 86/100

Philippines · asking $1,050

How the 86 adds up · Top ~10%

A bar is as long as its part's weight; the filled share is the score out of 100.

  1. Graded work sample 35%84

    Delivers a reusable 7-step framework with catch-all handling, HubSpot import rules, and a concrete 'evidence of the problem' qualifier — client-ready.

  2. Scenario judgment 25%88

    Title-by-headcount split, 180-account buffer, catch-all tab logic, and 85 with a note, not 100 with 15 guesses show sharp, specific judgment.

  3. Experience specificity 20%85

    Three years on one named account, 400 verified contacts/week, sub-1.5% bounce for two years, and a title-cut that moved reply rate from 2.1% to 4.6%.

  4. Written & spoken English 15%82

    Consistently clear, correct, and professional; 'Verified in a database means verified at some point, not today' shows precise, confident register.

  5. Salary-band fit 5%100

    Asks $1,050 a month, inside the $750–1,250 band.

Must-haves in the brief: 4 of 4 shown

  • builds B2B prospect lists to a defined ICP — shown5 years building B2B prospect lists for US companies
  • verifies emails before anything is sent — shownevery email goes through NeverBounce, including the ones Apollo already marks as verified
  • Apollo, LinkedIn Sales Navigator or Clay — shownLinkedIn Sales Navigator, Apollo, Clay (waterfalls and Claygent; still learning its HTTP API steps)
  • can say why a contact qualifies — shownEvery contact gets one line in a 'why' column

The parts, weighted as above, come to 86.

Screening notes

Strongest: The title-cut story (14 → 5 titles, 2.1% → 4.6% reply rate) is the kind of ICP-tightening judgment the role explicitly needs.

Concern: Clay HTTP API steps described as still being learned; depth on sequence writing and deliverability warm-up is thin.

Worth asking: Has the candidate written or iterated first-touch copy, or only fed lists to SDRs who own the sequences?

Verdict: A well-evidenced, process-disciplined list-builder whose ICP-refinement instincts and deliverability habits align closely with the role's core demands.

Experience

5 years building B2B prospect lists for US companies, the last 3 at a Davao outsourcing firm on an account for a US industrial software company that sells to manufacturers and distributors. I build about 400 verified contacts a week for four SDRs and own the list from ICP to CRM; bounce rate has stayed under 1.5% for two years. The change I'm proudest of: I showed the SDR manager that 9 of our 14 target titles almost never replied. We cut to 5, and reply rate went from 2.1% to 4.6% in one quarter.

Tools

LinkedIn Sales Navigator, Apollo, Clay (waterfalls and Claygent; still learning its HTTP API steps), NeverBounce, ZeroBounce, HubSpot, Google Sheets, Instantly (read-only, for bounce and reply data)

Scenario answer

Asked: You are tasked with building a list of 100 decision-maker contacts at US manufacturing companies with 50–500 employees, for a tool that replaces manual purchase-order tracking. You have three working days. Walk through exactly how you'd build it — the sources, the verification steps, and how you'd define whether a contact is qualified enough to pass to the closer.

Day 1, first hour: agree the buyer with the closer before building anything. At 50–150 employees the person who signs is usually the owner, the VP of Operations or the plant manager; at 150–500 it's a purchasing or procurement manager, or a director of supply chain. Buyers and expediters use the tool but don't buy it. My starting titles: Purchasing Manager, Procurement Manager, Director of Purchasing, Supply Chain Manager or Director, Materials Manager, VP Operations, Plant Manager, plus Owner or President under 150 employees. Day 1, rest of the day: accounts, not people. Apollo company search for US headquarters, manufacturing industries, 50–500 employees, exported to a sheet. In my experience headcount runs low on LinkedIn for factories, because a lot of floor staff aren't on it, so I check size against a second source and drop anything clearly outside the range. I also drop distributors and resellers; the company's own site settles most of those in 30 seconds. I aim for about 180 accounts to end with 100 contacts. Day 2: people and emails. Sales Navigator for one or two contacts per account from the agreed titles, skipping anyone who changed jobs in the last 90 days, since they don't own the process yet. Emails from Apollo first, then a Clay waterfall for the ones Apollo can't find. Then every email goes through NeverBounce, including the ones Apollo already marks as verified: - Valid: keep. - Invalid and disposable: remove. - Unknown: run again the next day; still unknown, remove. - Catch-all: separate tab. Those domains accept any address, so no checker can confirm the mailbox. I keep one only if another contact at the same company confirms the email pattern, and flag it for a small separate send. On my last manufacturing list about a quarter came back catch-all, so this matters here. Day 3: qualify and deliver. Every contact gets one line in a 'why' column, for example: 'Purchasing Manager, 140-person machine shop; careers page has a buyer opening that mentions maintaining the open-PO spreadsheet.' If I can't write that line, the contact doesn't go to the closer. My line for qualified: the company makes things and buys materials and parts on POs; 50–500 employees confirmed from two sources; the person owns or approves purchasing; and nothing suggests they already run software that does this. If only 85 clear that line by the end of day 3, I deliver 85 with a note on why, not 100 with 15 guesses.

Work sample

Asked: Describe your list-building process from a cold brief: the tools you start with, how you verify contacts, and the one thing that separates a qualified prospect from a near-match you'd leave out.

MY PROCESS FROM A COLD BRIEF 1. Rewrite the brief as a one-page ICP and get the closer to sign it off. Company: industry, size, location, and the two or three things that must be true. Person: the titles that decide, the titles that influence, the titles we skip. Disqualifiers written down. An hour here saves days of rework. 2. A test list of 30 before the real one. I send the closer 30 contacts with a 'why' line each and ask which they'd actually call. The rejections teach me more than the brief did, usually a title or a company type I'd never have guessed. 3. Accounts first. Apollo company search for the firmographics, then the company websites for what filters can't tell me: what they actually make, and whether they're really a distributor. I cut the account list before looking for a single person. 4. People second. Sales Navigator for one or two contacts per account from the approved titles, in the role long enough to own the process. 5. Emails. Apollo first, then a Clay waterfall for the misses. Then NeverBounce or ZeroBounce on every address, including the ones a database calls verified. Verified in a database means verified at some point, not today. - Valid: keep. - Invalid, disposable: remove. - Unknown: re-run once, then remove. - Catch-all: separate tab, kept only when another contact at the company confirms the email pattern, and flagged for a small separate send. 6. Into HubSpot with the source, the verification result and date, and the 'why' line in its own property. Nothing is imported without a verification date. 7. Watch the first sends. If bounces go over 2% on any batch, that batch stops and gets re-checked before anything else goes out. I'd rather slow the SDRs down for a day than burn a sending domain. THE ONE THING Evidence of the problem. A near-match has the right title at the right size of company. A qualified prospect has that and a reason to believe they have the problem now — for a PO-tracking tool, a buyer or expediter job post that mentions spreadsheets, or 40 suppliers and no purchasing software anywhere I can see. If I can't point to it, the contact goes in the near-match tab, not to the closer.

Availability

Full-time, 8pm–5am PHT (8am–5pm ET), shifting with US daylight saving. Two weeks' notice.

↑ All 3 at a glanceNext: Julián P. ↓

Julián P. · 2 of 3

SCREEN 85/100

Argentina · asking $1,250

How the 85 adds up · Top ~10%

A bar is as long as its part's weight; the filled share is the score out of 100.

  1. Graded work sample 35%84

    Structured five-step framework with concrete rules: two-source employee count, title priority order, Friday feedback loop by segment, and the reason not a match distinction.

  2. Scenario judgment 25%88

    Builds from problem backwards, uses job-post signals to filter intent, flags catch-all domain separation, and offers a pre-send ICP validity check — all specific and defensible.

  3. Experience specificity 20%82

    Six years, named tools, 11 client campaigns, sub-1% hard bounce rate, and a three-provider waterfall with ZeroBounce — specific numbers and decisions throughout.

  4. Written & spoken English 15%83

    Consistently clear and direct; 'build it from the problem backwards' and 'a reason, not a match' show confident, professional register with no errors.

  5. Salary-band fit 5%100

    Asks $1,250 a month, inside the $750–1,250 band.

Must-haves in the brief: 4 of 4 shown

  • builds B2B prospect lists to a defined ICP — shownA typical build pulls accounts, finds contacts, runs a three-provider email waterfall, verifies, and writes a qualification note on every row
  • verifies emails before anything is sent — shownZeroBounce on every address the day before it's loaded, not the week before. Only 'valid' goes into the main campaign
  • Apollo, LinkedIn Sales Navigator or Clay — shownMost of my list work runs in Clay
  • can say why a contact qualifies — shownA contact reaches the closer only if three columns are filled: company fit … role fit … and a reason

The parts, weighted as above, come to 85.

Screening notes

Strongest: Scenario answer — problem-first framing, intent signals from job posts, catch-all domain isolation, and a pre-send ICP sanity check are all operationally mature.

Concern: No explicit mention of first-touch sequence writing or open/reply rate results from past campaigns; deliverability detail is strong but sequence outcomes are absent.

Worth asking: What reply rates or qualified-reply rates have they actually delivered across those 11 campaigns?

Verdict: A technically disciplined list-builder with real tool depth and sound judgment; ask is at the top of the band.

Experience

6 years in outbound: 2 as an SDR at a Buenos Aires software company selling to US mid-market, then 4 building lists and outbound systems for US B2B agencies and their clients. Most of my list work runs in Clay. A typical build pulls accounts, finds contacts, runs a three-provider email waterfall, verifies, and writes a qualification note on every row. I also set up the sending side: separate domains, warm-up, SPF/DKIM/DMARC and bounce limits. Across 11 client campaigns last year, hard bounces stayed under 1%.

Tools

Clay (tables, waterfalls, Claygent, HTTP API), Apollo, LinkedIn Sales Navigator (on client seats), ZeroBounce, MillionVerifier, Instantly, Smartlead, HubSpot, Google Postmaster Tools, n8n

Scenario answer

Asked: You are tasked with building a list of 100 decision-maker contacts at US manufacturing companies with 50–500 employees, for a tool that replaces manual purchase-order tracking. You have three working days. Walk through exactly how you'd build it — the sources, the verification steps, and how you'd define whether a contact is qualified enough to pass to the closer.

I'd build it from the problem backwards: find the companies that show signs of tracking POs by hand, then the person who owns that process. A list of every purchasing manager at a 50–500-person manufacturer is quick to build and mostly wasted on the closer. Day 1: about 300 accounts. Apollo company search for US manufacturers with 50–500 employees, pulled into Clay and deduped on domain. A Claygent step reads each homepage and drops the ones that describe themselves first as a distributor or wholesaler. Then two signals: - Job posts from the last 90 days for buyers, purchasing coordinators or expediters. Claygent reads each posting and flags the ones that mention spreadsheets, Excel, or following up on open POs. - What they already run. If their job posts ask for experience with a full procurement platform, they've probably solved this, so they go to the bottom. Day 2: people. Two contacts per account. First, whoever owns purchasing: Purchasing or Procurement Manager, Director of Supply Chain, VP Operations, or the owner at the small end. Second, the Controller, because the pain also shows up when invoices don't match POs. Sales Navigator on the client's seat to confirm each is still in the role. Emails through a waterfall (Apollo, then two more providers), then ZeroBounce on everything. Only 'valid' goes into the main send. Catch-alls get their own list, sent in a small batch from a separate domain, and the whole segment stops if bounces pass 2%. Unknowns I drop. Day 3: qualify and hand over. A contact reaches the closer only if three columns are filled: company fit (makes things, 50–500 confirmed from two sources, US), role fit (owns or approves purchasing), and a reason, such as the job post, a comment they made or a line on their site. The reason is written in plain English so the closer can use it in the first sentence of a call. A trade-off I'd flag to the client: because most of this runs in Clay, I check about one row in five by hand, not every row. I pick them at random, and if more than 2 in 20 are wrong I stop and fix the rule rather than hand-correct rows. With the list, the client also gets a short note on what the signals found, like how many of the 300 accounts had a spreadsheet-PO job post. That tells us whether the ICP is right before a single email goes out.

Work sample

Asked: Describe your list-building process from a cold brief: the tools you start with, how you verify contacts, and the one thing that separates a qualified prospect from a near-match you'd leave out.

FROM A COLD BRIEF: HOW I BUILD A LIST 1. Turn the brief into rules a person and a machine would apply the same way. 'Mid-size manufacturers' becomes 'US headquarters, 50–500 employees from two sources, makes and sells its own products'. 'Decision-makers' becomes a title list in priority order. If the client can't agree the rules, I don't start the build. I send 20 sample rows and let their reactions write the rules. 2. Tools, in the order I use them. Apollo for the company search, because it exports cleanly. Clay to hold everything: dedupe, enrichment, Claygent checks of company websites and job posts, the email waterfall. Sales Navigator on the client's seat for the people Apollo is unsure about. Google Sheets only for the client review. 3. Verification, in three layers. - Find: a waterfall of three providers, stopping at the first result. - Verify: ZeroBounce on every address the day before it's loaded, not the week before. Only 'valid' goes into the main campaign. - Catch-all: separate campaign, small volume, stopped automatically at 2% bounces. After the first 200 sends I compare the actual bounce rate with what the verifier predicted. If they disagree, the provider or the verifier is wrong for this industry, and I change it. 4. Protect the domain. Never the client's main domain; warmed inboxes; SPF, DKIM and DMARC checked; about 30 emails a day per inbox. A list is only worth what the domain sending it can still deliver. 5. Feedback every Friday. Replies and bounces by segment: title, company size, signal. A segment with 150 sends and no positive replies is out the next week. That's how the ICP gets narrower in a way you can defend. THE ONE THING A reason, not a match. A near-match passes every filter. A qualified prospect has something I can point to that says they have the problem now — a job post, a new plant, a comment about chasing suppliers. If the only reason a contact is on the list is that the filters let them through, they're a near-match and they stay out.

Availability

Full-time, 10am–7pm ART (9am–6pm ET). Available in two weeks.

↑ All 3 at a glanceNext: Rochelle B. ↓

Rochelle B. · 3 of 3

SCREEN 64/100

Philippines · asking $800

How the 64 adds up · Competent but generic

A bar is as long as its part's weight; the filled share is the score out of 100.

  1. Graded work sample 35%62

    Numbered steps are clear and tools are named, but the process is generic and the qualification criterion (job title alone) is thin.

  2. Scenario judgment 25%65

    Covers sources, titles, and a day-three QA buffer, but guessing email formats from domain patterns is a deliverability risk left unaddressed.

  3. Experience specificity 20%58

    Three industries and a weekly volume figure are specific, but no client outcomes, reply rates, or list-quality metrics are given.

  4. Written & spoken English 15%78

    Consistently clear, correct sentences; professional register throughout; phrase 'organised and ready for the closer' fits US business tone well.

  5. Salary-band fit 5%100

    Asks $800 a month, inside the $750–1,250 band.

Must-haves in the brief: 3 of 4 shown, 1 partly

  • builds B2B prospect lists to a defined ICP — shownI have built lead lists for real estate investors, a marketing agency and a software company
  • verifies emails before anything is sent — shownonly include the ones Apollo marks as verified
  • Apollo, LinkedIn Sales Navigator or Clay — shownLinkedIn Sales Navigator (basic), Apollo
  • can say why a contact qualifies — partly shown (−2)A qualified prospect has the authority to make the buying decision, like a director or manager in the right department

The parts, weighted as above, come to 66; must-haves not fully shown cost 2, so 64.

Screening notes

Strongest: Email verification discipline is consistent across both answers — Apollo-verified only, with Hunter as fallback for discovery.

Concern: Qualification logic relies on job title alone; no mention of company-fit signals, intent, or ICP tightening when reply rates stall.

Worth asking: Have they ever adjusted an ICP mid-campaign based on reply or bounce data, and what changed?

Verdict: A competent, reliable list-builder with solid tool coverage and clear English, but not yet showing the analytical layer the role needs.

Experience

3 years as a lead generation specialist and virtual assistant for US clients. I have built lead lists for real estate investors, a marketing agency and a software company, using LinkedIn and Apollo to find contacts and Google Sheets to organise them. I usually deliver 100 to 200 leads a week depending on the client's requirements. I am hardworking and detail-oriented, and I always make sure my leads are accurate.

Tools

LinkedIn Sales Navigator (basic), Apollo, Hunter, Google Sheets, Excel, Canva

Scenario answer

Asked: You are tasked with building a list of 100 decision-maker contacts at US manufacturing companies with 50–500 employees, for a tool that replaces manual purchase-order tracking. You have three working days. Walk through exactly how you'd build it — the sources, the verification steps, and how you'd define whether a contact is qualified enough to pass to the closer.

To build a list of 100 decision-makers at US manufacturing companies with 50–500 employees, I would start with LinkedIn Sales Navigator and Apollo. I would filter for manufacturing companies in the United States with 51–500 employees, then look for decision-makers with titles like CEO, President, COO, Operations Manager, Purchasing Manager and Procurement Manager, because these are the people with the authority to buy a purchase-order tracking tool. I would put the contacts in a Google Sheet with columns for name, title, company, company size, LinkedIn URL, email and phone number. For the emails I would use Apollo and only include the ones Apollo marks as verified. If Apollo does not have the email, I would find the company's email format, for example firstname.lastname@company.com, and create the email from that. To make sure each contact is qualified, I would check that the company really is a manufacturer and in the right size range, and that the person still works there by looking at their LinkedIn profile. With three days, I would aim to finish the list by the end of day two so I have day three to double-check everything and remove duplicates. That way I can deliver the full 100 contacts on time, organised and ready for the closer.

Work sample

Asked: Describe your list-building process from a cold brief: the tools you start with, how you verify contacts, and the one thing that separates a qualified prospect from a near-match you'd leave out.

MY LIST-BUILDING PROCESS 1. Understand the client's target market: industry, location, company size and job titles. 2. Search LinkedIn Sales Navigator and Apollo with those filters. 3. Check each company's website and LinkedIn page to confirm it matches the criteria. 4. Find the decision-maker at each company and add their details to a Google Sheet: name, title, company, website, LinkedIn URL, email and phone. 5. Get the email from Apollo. If it's not there, I use Hunter to find it. 6. Check the email status in Apollo and only keep the ones marked verified. 7. Remove duplicates and check the sheet for errors before sending it to the client. The one thing that separates a qualified prospect from a near-match is the job title. A qualified prospect has the authority to make the buying decision, like a director or manager in the right department. Someone with a junior title or in a different department is a near-match, and I would leave them out.

Availability

Full-time, 9pm–6am PHT (9am–6pm ET). Available immediately.

↑ All 3 at a glance

This is the artifact every search delivers

Post the role and the same screener runs on your real applicants — the questions arrive already written, and you read every finalist in full before any fee is due.

Post a role free Or have us run the search

The same screener, other roles

Sample shortlist: Lead Generation Specialist | Rolemote