The Context
The company was remote-first — no offices, a distributed team across three time zones, and a culture built around async-first communication. They needed a VP of Product. The CEO had a strong conviction that the best VP of Product candidates were not concentrated in their primary hiring market (San Francisco) — and that a US-only search would produce a weaker shortlist than a global one.
That conviction was correct. The eventual placement came from a candidate in London, operating 8 hours ahead of the company's West Coast core team — a gap that required explicit design, not hope, to work.
What Changed in the Search Process
Async work style became a primary filter
A VP of Product who has only worked in co-located or sync-first teams will struggle in a remote-first environment — not because of skill, but because of operating system mismatch. The assessment included specific evaluation of whether each candidate had operated effectively in async environments: do they write well? Do they make decisions without waiting for a meeting? Do they create clarity in documents rather than relying on real-time conversation?
Time zone overlap was a structural requirement
The search brief specified a minimum of 4 hours of working-hour overlap with the West Coast team. That ruled out candidates in Asia Pacific but opened the full European market. The brief was honest about the constraint — which actually helped candidate self-selection: candidates who did not want to start early for the overlap window removed themselves from consideration.
Visa and contractor structure required early resolution
Before a non-US candidate could be on the shortlist, the company needed clarity on whether they would engage them as an employee (requiring entity establishment or an EOR) or a contractor. That decision was resolved in the intake, not at offer stage — which prevented the most common cross-border search failure: a preferred candidate who cannot be hired in the required timeframe because the legal structure has not been designed.
Compensation was structured in local currency with clear USD equivalent
Offering a UK-based candidate a USD-denominated salary introduces currency risk they will price into their decision. The offer was structured in GBP, benchmarked against UK VP Product market rates with equity calculated at the prevailing exchange rate and floor-protected. The candidate received an offer that made financial sense in their context, not a conversion exercise.
The Onboarding Adjustment
A cross-border executive who starts a remote role without deliberate onboarding design is set up to fail. The placed VP of Product had two weeks of intensive overlap: synchronous working sessions at the boundary of both time zones, structured relationship-building with key cross-functional stakeholders, and an explicit written brief on decision rights — who could act autonomously and who needed alignment before moving. Six months in, they are the most organised VP-level executive the team has worked with. The async discipline that made them a strong candidate made them a strong leader.
Search Parameters
What This Search Teaches
International and remote placements are structurally different from domestic searches — not harder, but requiring design decisions that most searches do not face: employment structure, compensation denomination, time zone architecture, and async-first assessment. Companies that treat a global search as a domestic search with a wider geographic filter produce failed placements at a higher rate. The design decisions need to be made at intake, not at offer.
Related case studies and resources:
Remote-First Executive SearchWhat Is Executive Onboarding?What Is Offer Acceptance Rate?What Is a Counter-Offer?Executive Search Methodology