AI-Powered Candidate Sourcing Tool
Paste your requirements.
Get a ranked shortlist.
Not a one-shot search. An AI sourcing agent that learns and improves with each cycle.
Each cycle refines its queries based on where the best candidates came from. You can steer it at any point.
Asks calibration questions to understand what good really looks like
Maps the ecosystem and runs targeted queries from multiple angles
Evaluates every profile against your criteria with transparent reasons
Analyses where the best candidates came from and refines its approach
Repeat until shortlist is complete
refine & repeat
A real completed AI sourcing search for a Forward Deployed Engineer role — 54 candidates found, scored against hiring criteria, and ranked in minutes. Candidate details have been redacted for privacy.
Scroll through the conversation to see the agent’s reasoning, then explore the shortlist.
Forward Deployed Engineer, Applied AI
Thought for a few seconds
Here’s my read before I start searching:
- This is a deployment-builder hire, not a classic pre-sales SE search — the closest matches will be people who still code, work inside customer environments, and turn messy enterprise problems into production AI systems.
- I see three real candidate lanes — career FDEs / forward-deployed builders, applied AI engineers with consulting or post-sales delivery depth, and technical founders or early startup engineers who’ve done customer-facing implementation. I’d start with the first lane unless you want more 0→1 founder energy than title fidelity.
- The hardest trade-off is frontier AI depth vs enterprise delivery polish — the market often splits those between AI-native builders and cloud/consulting operators. Your preference there will change both target companies and how I score adjacent profiles.
- “Founding FDE” likely means high-agency ICs, not heavyweight leaders — I’ll bias toward hands-on builders who can shape the motion, unless you want someone meaningfully more senior than the title suggests.
Which profile lane should I anchor on first?
Prioritize former founders or early startup engineers who built AI products and can work directly with customers.
If I have to trade off, what matters more?
Prioritize real production LLM / agent experience even if enterprise vertical depth is lighter.
How wide should I cast geography at the start?
“London”
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Here’s what I’m seeing in the market:
- London is a real target pool, not just a fallback geography — Anthropic, OpenAI, Palantir, Faculty, Arva AI, and Mistral all show applied AI or forward-deployed talent in-market there. That means I can stay tight on London rather than widening to Europe immediately.
- Palantir-style forward-deployed builders are still the cleanest translation — that ecosystem consistently produces engineers who embed with customers, ship in production, and operate well under ambiguity. I’m treating that lane as a benchmark, even though you want founder-heavy coverage first.
- The founder lane is viable, but only if I stay strict on hands-on LLM evidence — plenty of startup founders look strategic; far fewer show production agents, evaluations, Python builds, or enterprise deployments. I’ll screen that lane hard for real build depth.
- The best adjacent pool is applied AI delivery, not generic solutions engineering — Databricks-, OpenAI-, and Faculty-style profiles with RAG, agent orchestration, and evaluation work are much closer than classic pre-sales architects. I’m biasing toward builders who happened to be customer-facing, not sellers who learned AI vocabulary.
Thought for a few seconds
Founder-heavy profiles will only be worth it if they show real build depth, so I’m testing that lane against cleaner FDE and applied-AI delivery pools rather than assuming the founder title itself is enough.
Thought for a few seconds
The early read is clear: Palantir/OpenAI-style forward-deployed profiles are the most reliable lane, while founder backgrounds only work when the profile still reads like a hands-on builder rather than an executive.
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
I’ve got enough signal now: the London pool is real, but the market splits between clean forward-deployed operators and founder/builders who only sometimes translate into customer-embedded delivery.
Thought for a few seconds
The market is splitting the way I’d expect: the cleanest fits are Palantir/OpenAI-style forward-deployed operators, while the founder lane only works when the profile still reads like a builder, not a startup executive.
Shortlist Summary — Forward Deployed Engineer, Applied AI, Anthropic
36 candidates sourced
🟢 Tier 1 — Contact First These are the profiles I’d put at the top of outreach because they either already do the closest version of this job, or they give you the founder-style builder angle without losing hands-on AI delivery credibility.
| Name | Current Status | Why They Stand Out | Must Watch |
|---|---|---|---|
| Casey Edwards | Technical Deployment Lead, OpenAI | Probably the cleanest external translation: OpenAI deployment work plus Palantir heritage, which is exactly the embedded enterprise-build motion Anthropic wants. | Screen for how hands-on he still is vs program/lead scope. |
| Blake Lawson | Forward Deployed Architect / Technical Lead, Palantir | Strongest pure operator shape in the pool: long Palantir deployment history, London-based, and still technically credible. | May be edging toward architect/lead rather than founding IC. |
| Remy Beaumont | Independent Applied AI Engineer / Consultant | Best founder-adjacent wildcard: visible MCP work, agentic workflows, Python depth, and recent customer-facing delivery in London. | Less repeated enterprise stakeholder ownership than the classic FDE lane. |
| Ellis Donovan | Independent Consultant & Engineer, ex-Palantir | Strong Palantir-to-independent path, with visible NHS deployment work and enough LLM/RAG substance to make the story credible. | Consultant framing may mean he prefers flexibility over a full-time embedded role. |
| Morgan Anderson | Founding AI Engineer, Plexe AI | Best true founder-lane hit so far: on-prem enterprise LLM stacks, startup build energy, and still close to the code. | Customer-embedded delivery is thinner than the Palantir/OpenAI group. |
| Charlie Chen | Senior Software Engineer, Apple; former Founding Engineer | One of the better “builder first” profiles: visible agent systems, MCP servers, evals, and 0→1 product instincts. | Strong technical fit, but less proof of repeated enterprise deployment at customer sites. |
🔵 Tier 2 — The Rest of the Pool (30 candidates)
The remaining shortlist breaks into three usable groups.
About a dozen are Palantir/OpenAI/Databricks-style forward-deployed or deployment-strategist profiles — the cleanest title translation, though some skew a bit junior or a bit lead-heavy.
Another meaningful cluster is founder / founding-engineer talent with real agent, eval, and LLM build depth — stronger on 0→1 energy than on repeat enterprise delivery.
The rest are applied AI engineers and hands-on consultants in London who show solid RAG / GenAI shipping evidence, but need screening on whether they were actually embedded with customers or mostly building internal tools.
The best outreach angle across this group is “come build Anthropic’s field engineering motion from the beginning,” especially for people currently doing adjacent work inside OpenAI, Palantir, or independent AI delivery roles.
One especially notable reserve profile is [Kai Kowalski](https://www.linkedin.com/in/slate-connors-72b1d6 who bridges OpenAI and Palantir well but reads a bit more solutions-architecture than pure FDE.
What I learned
- Palantir is still the cleanest factory — that ecosystem produces the most obvious customer-embedded operators in London, and it keeps outperforming broader “applied AI” phrasing.
- Founder fit is narrower than it sounds — the good founder profiles are very good, but most founder results drift too strategic, too senior, or too light on enterprise deployment ownership.
- London is workable without widening yet — there’s enough density across Palantir, OpenAI, founder-led AI companies, and independent builders that I don’t think geography is the bottleneck right now.
- The biggest interview question won’t be visible on LinkedIn — for many of these candidates, the real screen is how much white-glove customer deployment they’ve personally owned versus advising, architecting, or managing around it.
Take a look through the shortlist and tell me which lane feels most right to you. If you want, I can do the next pass either tighter on Palantir/OpenAI-style operators or more aggressively into founder/builder profiles with strong MCP-agent depth.
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
I put together a shareable market brief for the hiring manager that explains:
- how the London market splits across the main candidate lanes
- where the strongest talent clusters sit
- what backgrounds translate best to Anthropic
- what looks close but usually isn’t
- the practical implications for calibrating interviews and expectations
If you want, I can also turn it into a shorter one-page version with a more executive tone.
Thought for a few seconds
Tightened it into a shorter version. If you want, I can make it even more exec-style — closer to a half-page brief.
Pipeline
Former Palantir FDE now leading Azure connectivity work, with the strongest customer-deployment shape in the batch.
OpenAI deployment lead with Palantir FDE heritage and serious enterprise AI delivery experience.
London-based applied AI engineer with production LLM deployment, MCP work, and customer-facing consulting experience.
Hands-on London engineer shipping LLM agents, MCP servers, and production AI workflows end to end.
Palantir Deployment Strategist in London with direct customer-embedded enterprise delivery experience.
Founding AI engineer in London with clear LLM tooling, agents, and hands-on build work.
Palantir FDE lead in London with NHS deployments and hands-on Python, RAG, and customer delivery experience.
OpenAI and Palantir FDE veteran in London with the strongest functional match for embedded enterprise AI deployment.
Palantir engineer who built LLM features and spent time as a deployment strategist in London.
Hands-on London AI engineer building production agent workflows and MCP integrations.
OpenAI Solutions Architect who has already done Palantir-style embedded AI delivery in London.
London-based Palantir FDE with recent MLOps, deployment, and evaluation work across production ML systems.
London-based GenAI platform engineer with production ML pipelines and regulated financial-services delivery.
London-based founder with hands-on LLM shipping and enterprise deployment themes.
Palantir FDE who has already taken LLMs to production across commercial customers.
Palantir FDE veteran with finance systems depth and strong Python, Java, and C# engineering.
Palantir FDE veteran in London with real customer-facing build experience.
Ex-Palantir FDE now building at ElevenLabs, with strong London-based product and production engineering evidence.
London engineer with full-stack and AI delivery depth who already builds and prototypes LLM applications.
Palantir FDE with seven years of Python and finance delivery, plus clear London-based customer-embedded engineering experience.
Ex-founder building production LLM systems and MCP-style workflows in London.
Palantir FDE with London experience, but the profile is too sparse to judge AI depth.
Young Palantir FDE with explicit LLM infrastructure work and enterprise delivery exposure.
Technical founder with shipping AI agents and evaluation frameworks, plus real product and startup execution.
Strong London builder with AI product engineering and direct client-debugging experience, a good FDE translation.
Senior AI engineer with regulated-domain deployment and LLMOps depth, close to the enterprise applied AI target.
Microsoft customer-success and industry agents background gives real forward-deployed flavor with strong Python and Azure depth.
Delivery-focused AI engineer with repeated production GenAI work across consulting and enterprise teams.
OpenAI FDE with prior Palantir AI deployment work and enterprise GenAI delivery in London and New York.
Ex-Palantir FDE in London who has already done the exact customer-embedded deployment motion Anthropic wants.
Palantir AI deployment strategist with applied ML and testing experience in London.
London-based applied AI builder who has shipped production GenAI products with RAG and client-facing delivery.
Hands-on AI engineer in London with RAG, agents, and production backend delivery.
London-based LLM engineer shipping RAG and forecasting systems with strong full-stack delivery.
London-area Palantir FDE with production software and AI-adjacent experience, close to the target operating model.
London FDE already building AI systems on Palantir Foundry and AIP.
Thought for a few seconds
Here’s my read before I start searching:
- This is a deployment-builder hire, not a classic pre-sales SE search — the closest matches will be people who still code, work inside customer environments, and turn messy enterprise problems into production AI systems.
- I see three real candidate lanes — career FDEs / forward-deployed builders, applied AI engineers with consulting or post-sales delivery depth, and technical founders or early startup engineers who’ve done customer-facing implementation. I’d start with the first lane unless you want more 0→1 founder energy than title fidelity.
- The hardest trade-off is frontier AI depth vs enterprise delivery polish — the market often splits those between AI-native builders and cloud/consulting operators. Your preference there will change both target companies and how I score adjacent profiles.
- “Founding FDE” likely means high-agency ICs, not heavyweight leaders — I’ll bias toward hands-on builders who can shape the motion, unless you want someone meaningfully more senior than the title suggests.
Which profile lane should I anchor on first?
Prioritize former founders or early startup engineers who built AI products and can work directly with customers.
If I have to trade off, what matters more?
Prioritize real production LLM / agent experience even if enterprise vertical depth is lighter.
How wide should I cast geography at the start?
“London”
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Here’s what I’m seeing in the market:
- London is a real target pool, not just a fallback geography — Anthropic, OpenAI, Palantir, Faculty, Arva AI, and Mistral all show applied AI or forward-deployed talent in-market there. That means I can stay tight on London rather than widening to Europe immediately.
- Palantir-style forward-deployed builders are still the cleanest translation — that ecosystem consistently produces engineers who embed with customers, ship in production, and operate well under ambiguity. I’m treating that lane as a benchmark, even though you want founder-heavy coverage first.
- The founder lane is viable, but only if I stay strict on hands-on LLM evidence — plenty of startup founders look strategic; far fewer show production agents, evaluations, Python builds, or enterprise deployments. I’ll screen that lane hard for real build depth.
- The best adjacent pool is applied AI delivery, not generic solutions engineering — Databricks-, OpenAI-, and Faculty-style profiles with RAG, agent orchestration, and evaluation work are much closer than classic pre-sales architects. I’m biasing toward builders who happened to be customer-facing, not sellers who learned AI vocabulary.
Thought for a few seconds
Founder-heavy profiles will only be worth it if they show real build depth, so I’m testing that lane against cleaner FDE and applied-AI delivery pools rather than assuming the founder title itself is enough.
Thought for a few seconds
The early read is clear: Palantir/OpenAI-style forward-deployed profiles are the most reliable lane, while founder backgrounds only work when the profile still reads like a hands-on builder rather than an executive.
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
I’ve got enough signal now: the London pool is real, but the market splits between clean forward-deployed operators and founder/builders who only sometimes translate into customer-embedded delivery.
Thought for a few seconds
The market is splitting the way I’d expect: the cleanest fits are Palantir/OpenAI-style forward-deployed operators, while the founder lane only works when the profile still reads like a builder, not a startup executive.
Shortlist Summary — Forward Deployed Engineer, Applied AI, Anthropic
36 candidates sourced
🟢 Tier 1 — Contact First These are the profiles I’d put at the top of outreach because they either already do the closest version of this job, or they give you the founder-style builder angle without losing hands-on AI delivery credibility.
| Name | Current Status | Why They Stand Out | Must Watch |
|---|---|---|---|
| Casey Edwards | Technical Deployment Lead, OpenAI | Probably the cleanest external translation: OpenAI deployment work plus Palantir heritage, which is exactly the embedded enterprise-build motion Anthropic wants. | Screen for how hands-on he still is vs program/lead scope. |
| Blake Lawson | Forward Deployed Architect / Technical Lead, Palantir | Strongest pure operator shape in the pool: long Palantir deployment history, London-based, and still technically credible. | May be edging toward architect/lead rather than founding IC. |
| Remy Beaumont | Independent Applied AI Engineer / Consultant | Best founder-adjacent wildcard: visible MCP work, agentic workflows, Python depth, and recent customer-facing delivery in London. | Less repeated enterprise stakeholder ownership than the classic FDE lane. |
| Ellis Donovan | Independent Consultant & Engineer, ex-Palantir | Strong Palantir-to-independent path, with visible NHS deployment work and enough LLM/RAG substance to make the story credible. | Consultant framing may mean he prefers flexibility over a full-time embedded role. |
| Morgan Anderson | Founding AI Engineer, Plexe AI | Best true founder-lane hit so far: on-prem enterprise LLM stacks, startup build energy, and still close to the code. | Customer-embedded delivery is thinner than the Palantir/OpenAI group. |
| Charlie Chen | Senior Software Engineer, Apple; former Founding Engineer | One of the better “builder first” profiles: visible agent systems, MCP servers, evals, and 0→1 product instincts. | Strong technical fit, but less proof of repeated enterprise deployment at customer sites. |
🔵 Tier 2 — The Rest of the Pool (30 candidates)
The remaining shortlist breaks into three usable groups.
About a dozen are Palantir/OpenAI/Databricks-style forward-deployed or deployment-strategist profiles — the cleanest title translation, though some skew a bit junior or a bit lead-heavy.
Another meaningful cluster is founder / founding-engineer talent with real agent, eval, and LLM build depth — stronger on 0→1 energy than on repeat enterprise delivery.
The rest are applied AI engineers and hands-on consultants in London who show solid RAG / GenAI shipping evidence, but need screening on whether they were actually embedded with customers or mostly building internal tools.
The best outreach angle across this group is “come build Anthropic’s field engineering motion from the beginning,” especially for people currently doing adjacent work inside OpenAI, Palantir, or independent AI delivery roles.
One especially notable reserve profile is [Kai Kowalski](https://www.linkedin.com/in/slate-connors-72b1d6 who bridges OpenAI and Palantir well but reads a bit more solutions-architecture than pure FDE.
What I learned
- Palantir is still the cleanest factory — that ecosystem produces the most obvious customer-embedded operators in London, and it keeps outperforming broader “applied AI” phrasing.
- Founder fit is narrower than it sounds — the good founder profiles are very good, but most founder results drift too strategic, too senior, or too light on enterprise deployment ownership.
- London is workable without widening yet — there’s enough density across Palantir, OpenAI, founder-led AI companies, and independent builders that I don’t think geography is the bottleneck right now.
- The biggest interview question won’t be visible on LinkedIn — for many of these candidates, the real screen is how much white-glove customer deployment they’ve personally owned versus advising, architecting, or managing around it.
Take a look through the shortlist and tell me which lane feels most right to you. If you want, I can do the next pass either tighter on Palantir/OpenAI-style operators or more aggressively into founder/builder profiles with strong MCP-agent depth.
Thought for a few seconds
Thought for a few seconds
Thought for a few seconds
I put together a shareable market brief for the hiring manager that explains:
- how the London market splits across the main candidate lanes
- where the strongest talent clusters sit
- what backgrounds translate best to Anthropic
- what looks close but usually isn’t
- the practical implications for calibrating interviews and expectations
If you want, I can also turn it into a shorter one-page version with a more executive tone.
Thought for a few seconds
Tightened it into a shorter version. If you want, I can make it even more exec-style — closer to a half-page brief.
What recruiters say about AI-powered sourcing
“11 or 12 very good calls booked in for strong-looking candidates, and I've already sent one across. The results are clearly there.”
“Manual sourcing for this kind of search is a nightmare. Nova just handed me a shortlist I'd have spent a week building myself.”
Ready to automate candidate sourcing?
Paste your job requirements and let Nova’s AI sourcing agent build a ranked candidate shortlist while you get on with your day.