The brief.
An early-stage US AI product company needed founding-level engineers who could own a feature from UI through API, data layer, and deploy without a hand-off in the middle — and needed them without opening US payroll for three more people. The work wasn't ticket-picking. Specs arrived ambiguous, product thinking was part of the job, and AI (LLM calls, retrieval, agents, MCP tools) was a first-class part of the product rather than a bolt-on.
The catch: this wasn't a remote-and-forget arrangement. The team runs hot — roughly twelve hours a day, six days a week — and every engineer would work with the US client in real time. That moved two résumé-soft requirements onto the hard list: a workflow genuinely rewired around AI tooling, and spoken English fluent enough to hold a live technical conversation unsupervised. Either gap, technical or communicative, would break the engagement. They wanted the engineers embedded and directed by their own leadership, with employment, payroll, statutory compliance, hardware, and performance management sitting somewhere else entirely.
- React + Next.js + TypeScript + Tailwind — production-grade, not template-grade
- Node.js + Express, with Next.js API routes or FastAPI where they fit
- PostgreSQL (incl. pgvector) + Redis — reasoning about data, not just CRUD
- LLM APIs, retrieval and vector search, ideally hands-on MCP
- REST, GraphQL, WebSockets, OAuth2 / JWT, rate limiting
- AWS, Docker, CI/CD — ships their own work to production
- Early-stage background: small teams, real ownership, ambiguous specs
- Demonstrated AI-native workflow — a provable habit, not a résumé claim
- Spoken and written English strong enough for direct, unsupervised client contact
- Real-time overlap with the US team — roughly twelve hours a day, six days a week
The funnel.
Sources: Internal database (40,761 candidates), LinkedIn Sales Navigator, Naukri, Indeed, AngelList Talent, niche dev communities (HN Who's Hiring, lobste.rs)
The problem.
Three filters had to pass at once, and each one cut the pool hard. Genuine AI-native workflow was the first. Plenty of candidates could talk fluently about Claude, agents, or MCP in an interview and had never chained tools, written an agentic workflow, or wired a model into a real dev loop. That difference doesn't survive contact with a keyword scan, and the only way to see it was to make candidates show it rather than describe it — which ruled out a large share of otherwise strong technical profiles early.
Communication was the second. Because every engineer would work directly with the US client, spoken fluency under live technical conversation became a hard gate rather than a nice-to-have, and it eliminated a meaningful number of technically excellent engineers who simply weren't comfortable thinking out loud in English under pressure. It is a skill almost no technical screen tests, and written English gave no signal either way — a résumé and an assignment read the same from a hesitant speaker and a confident one.
Mindset was the third and the hardest. Twelve-hour days, six days a week, full ownership, no hand-offs: that asks for someone senior enough to own a feature alone but still hungry to build at founder pace. Most engineers at that level have earned the right to optimize for balance, and rightly do.
Underneath all three sat the structural problem. Three founding-level engineers on US payroll — a Staff engineer at thirteen years and two seniors at four and five — is a fixed commitment an early-stage company makes once and lives with for years, and it would have consumed the runway this team needed for the product itself.
What we did.
We calibrated against the JD's own split between must-haves and good-to-haves before sourcing began, so the rubric reflected what this client actually needed rather than a generic full-stack-plus-AI checklist. From there the funnel ran wide and cut deep: 7,833 profiles sourced across two tracks, screened to 3,569, then 2,780 through deeper résumé and background evaluation, then 346 at Internal L1 where technical range was checked against the must-haves.
The assignment stage is where the AI-native filter did its real work. 116 candidates worked a hands-on problem designed so that describing AI usage wouldn't get them through it — they had to use the tooling, chain the steps, and leave the working visible. Candidates who had genuinely rewired how they build finished with artefacts that showed it. Candidates who had read about it produced something slower and hand-made.
Internal L2 took the surviving 82 into live conversation: spoken communication, thinking out loud under an unscripted technical question, and work-mode fit — which is where we ruled out strong engineers who wanted a comfortable senior-IC role rather than founder-pace ownership. That conversation was the only place either signal could be confirmed, so we didn't compress it. 12 candidates reached the client for final technical and cultural rounds; 3 cleared their bar, and all three were hired: a Staff Engineer at thirteen years, and two Senior Software Engineers at four and five. Every stage past Internal L1 ran the technical check and the communication check in parallel rather than in sequence, so neither dimension could be waved through on the strength of the other.
All three run on managed EOR. We hold the employment entity, payroll, statutory filings, and hardware; the client's own leadership directs the technical work and owns the roadmap. A dedicated account manager sits between the two — daily standups in the client's window, monthly performance reviews, weekly client sync — so nothing about employing three people in another country lands on the client's engineering leadership.
What changed.
The client got three founding-level engineers who cleared both bars: technical depth across the full stack plus AI integration, and the spoken fluency to work directly with the US team without friction in between.
Running the team on managed EOR saves them $53,000 a month against the loaded US cost of the same three roles — a Staff engineer at thirteen years and two seniors at four and five — which is roughly $636,000 a year that stays in the product instead of going to US payroll and overhead. Compliance overhead from the client's side: zero. Statutory filings: zero. Hardware logistics: zero.
The screening numbers underneath that are worth stating plainly. 7,833 profiles produced 3 hires — a 0.04% yield on the sourced pool, which measures how narrow the real intersection of hands-on AI-native and client-ready communicator is rather than a bar raised for its own sake. 45.6% of the sourced pool made it into screening, but only 12.4% of the internally evaluated pool reached Internal L1, and only 12 of the 82 candidates who cleared L2 were ones the client wanted to meet.
536 hours went into sourcing, screening, and interviews to fill three seats. For a team built on full ownership, direct client contact, and no hand-offs, those hours bought the one thing a faster search can't: confidence that all three would hold up in live, unsupervised conversation with the client's own team from day one.
How we ran it.
Brief & calibration
Mapped the JD's must-haves against its good-to-haves on a single page before any sourcing started, with explicit weight on the two dimensions résumés overstate most: demonstrated AI-native workflow and spoken communication.
Sourcing & screening
7,833 profiles across two tracks — 4,550 full stack, 3,283 backend. Screened to 3,569, then 2,780 through deeper résumé and background evaluation. 346 reached Internal L1, where technical range was checked line by line against the must-haves.
Assignment & client rounds
116 candidates worked an assignment built to surface AI-tool fluency by making them use it, not describe it. 82 cleared Internal L2 on live communication and founder-pace work fit. 12 reached the client; 3 cleared their final bar.
Onboard & manage on EOR
All three onboarded on managed EOR — contracts, payroll, statutory filings, and hardware handled by us. A dedicated account manager runs daily standups in the client's window, monthly performance reviews, and the weekly client sync.
What made this work.
Treating AI-native and client-ready communicator as hard filters rather than soft preferences is what kept this funnel honest. The pull in the other direction is constant — it's tempting to relax on communication when a candidate's technical answers are strong, and just as tempting to relax on demonstrated AI fluency when their spoken English is excellent. Screening both dimensions in parallel at every stage past Internal L1 is what stopped a false positive from reaching the client. It also explains the shape of the funnel: a far steeper drop than a technical-only search, and 536 hours of screening to land three seats.
The second lesson is narrower and more portable. For AI-native roles, the assignment has to make candidates use the tooling rather than talk about it. Every other stage in a standard funnel — résumé, screen, live coding — rewards the candidate who can describe the workflow well. Only the assignment tells you whether they actually work that way.
The third is about the structure rather than the search. 536 hours to fill three seats is only rational because of how the engagement is held: on managed EOR the employment risk sits with us, so a hire who doesn't hold up is our problem to replace rather than the client's to unwind. That aligns the incentive to screen properly instead of quickly — which is exactly the incentive a contingent, one-time placement fee does not create.