Distributed teams shouldn't mean broken hiring.
Helping TA leaders, CTOs and senior engineers navigate global coordination.
When teams span continents, more recruiters won't fix it.
Scaling a distributed organisation isn't a headcount problem. It's an information problem: how market knowledge, candidate signal and decisions move across time zones.
I solve it with systems. AI tooling, automation and repeatable frameworks that turn global coordination from a "tax" on your growth into a sustainable competitive advantage.
Read My Writing
Real scenarios from distributed hiring at scale
-
Frameworks
Time to Hire Is Four Problems, Not One
Most TA teams try to fix time to hire by pulling a single lever. It rarely works. Time to hire isn't one problem. It's four problems stacked on top of each other, and each one needs a different owner, a different target and a different intervention. Here's a framework for decomposing the metric and building your team around what it reveals. -
Strategy
Why Distributed TA Leaders Must Think Like Business Partners
When the CTO demanded 25 GPU engineers by year end across two continents, I didn't say yes. I ran a discovery meeting instead. That conversation shifted hiring from order-taking to business partnership. We ended up hiring 36 engineers instead of 25. Here's the framework. -
Operations
How I use AI to Hire Engineers Across San Francisco, London and Hyderabad Without Local Knowledge
You've never hired in San Francisco, London, and Hyderabad. The CTO wants the team live next quarter. Most TA leaders spend weeks researching. I've built an AI framework that gets you market-ready in days with insights most hiring consultants don't have. -
Systems
The Interview Capacity Check That Saves TA Directors From Overpromising
Your CTO demands 12 SREs in 10 weeks across three time zones. You have two choices: say yes and burn out, or push back without data and lose credibility. I built a 10-minute framework that shows you exactly what's actually blocking you so you can lead with numbers instead of guessing. -
Systems
How to Bar Raise When You Can't Be in the Room
Seniority norms vary by market. An IC3 in San Francisco and an IC3 in Hyderabad might both be strong engineers, but they've been measured against completely different benchmarks. Here's how to maintain consistent hiring standards across distributed teams without being in every interview room. -
Strategy
Building an EVP That Works Across SF, London, and Hyderabad
One EVP pitch won't work across every market. An engineer in San Francisco is asking different questions than one in Hyderabad or London. Here's how to localise your employer brand without losing what makes your company compelling.
Speaking Topics
Pragmatic frameworks for building distributed teams at scale.
AI & Market Knowledge
How to become an instant market expert in regions you've never recruited in through rapid AI discovery.
Distributed Capacity
The mathematical models behind hitting hiring targets when your interviewers span multiple continents.
Time Zone Choreography
Moving beyond timezone stalling patterns to create interview cadences that work across 8+ hour spreads.
Context Compression
How to maintain hiring quality when information asymmetry is your biggest constraint.
Building for Global Coordination
Technical frameworks and organizational structures that accommodate time zones, context gaps, and international business constraints.
Built at scale. Teaching the playbook.
I build hiring systems at DigitalOcean, where I hire for distributed, niche and leadership roles globally.
Alongside the searches, I build AI tooling, workflows, automation and enablement that turn hiring craft into repeatable systems. The frameworks I share here come straight from that work.
The mentality is 10x, not 10%. That AI work has cut my time from job description to outreach by up to 90% and turned weeks of market research into days, with quality going up, not down.
Free Tools
01
Requisition Intelligence
Paste a job description, get a full sourcing toolkit back.
More
The problem it solves
The gap between the JD landing in your inbox and you actually sourcing is hours of reading, decoding requirements you half understand, and second-guessing who is really a fit. This closes it in one paste.
What one paste gives you
- A plain-English requisition breakdown, plus the hidden requirements and red flags
- Ready-to-send clarification questions for the hiring manager
- A realistic, sourceable candidate persona, not a unicorn
- LinkedIn Boolean strings, a primary and a broadened variant
- Free sourcing channels beyond LinkedIn you can open in a browser
- A character-counted InMail and follow-up, and a LinkedIn post
- ATS screening questions tuned to gate to roughly the top 15%
02
Candidate Shortlister
Point it at a folder of CVs and a JD, get back a ranked shortlist you can send.
More
The problem it solves
You pull a batch of profiles and then read every one against the JD to decide who to put forward. It is slow, it is inconsistent, and your reasoning, which requirements matter and which can flex, rarely reaches the hiring manager.
What you get
- A shareable shortlist message for Slack, Teams or email, with a short rationale per candidate
- A scored table of everyone considered, as an audit trail
- An honest "nobody clears the bar" verdict when that is the truth, no forced shortlists
Let's Work Together
I start with discovery. We spend time understanding where your distributed hiring is actually breaking—timezone coordination cost, context gaps, information asymmetry. Then I work with your team on frameworks that fix your specific constraints, not generic best practices.
When you book me to speak, your audience walks away with concrete frameworks they can implement immediately. I'm not there to inspire—I'm there to give them the mental models and structures for distributed hiring that actually work.