Start with the work your FDE will do, then look for people who have done that work under another title. Forward deployed engineering overlaps with implementation, solutions engineering, backend and data engineering, technical customer delivery, and deployment strategy. A title is a search term. It is not a qualification.
Build a sourcing map from the job
Break the role into four parts: what the person builds, who they work with, what stage they own, and how they work. Search for evidence in each part.
- For production delivery, look for shipped integrations, services, data workflows, reliability work, and the decisions behind them.
- For customer work, look for requirements gathered from users, technical plans explained to non-specialists, and clear handoffs.
- For evaluation or pre-sales, look for experiments that tested a use case and moved it toward a decision. Do not assume that a proof of concept became a production system.
- For internal deployment, look for tools or processes that helped operating teams deliver a product.
Use several candidate sources
Keep a source record for each person: the role or project that caught your attention, the evidence you read, the date you checked it, the location, and the reason the person may want this kind of work. Do not convert a public profile into assumptions about availability, compensation, work authorization, or interest.
Check the work before you contact someone
Read enough to answer these questions:
- Did the person own implementation, or only advise the team that did it?
- Did they write or operate production code, configure an integration, or work only on prototypes?
- Who used the result: an external customer, an internal team, or both?
- Did they handle unclear requirements and trade-offs themselves?
- Does the location and travel expectation fit the open role?
The same care applies to remote work. The method page notes that a bare “Remote” label is not enough to establish that a role can be performed from the United States. Confirm the permitted location, customer travel, and time-zone expectations directly.
Write the first message around the work
Tell the candidate what the team is trying to deliver, who they would work with, and what the role owns. Include the location, travel expectation, and published base range when available. Say why their specific project or responsibility prompted the message. Ask whether the problem is relevant before asking for a resume or a call.
Do not claim that the employer is a partner, that the candidate is a fit, or that the role will advance their career unless you have evidence for that statement. A job listing shows an employer's public request. It does not prove that the role is still open or that an introduction can be arranged.
Learn which sources are working
Track the same steps for every source: people reviewed, people contacted, replies, qualified conversations, and candidates who permit an introduction. Keep the role, geography, seniority, and message visible so that a low response rate has a useful explanation. Do not call a source effective from a small number of contacts, and do not turn listing counts into candidate-supply estimates.
The goal is a repeatable way to reach people with the required experience and permission to discuss a specific role. When the evidence does not support a conclusion, change the search terms or ask the employer which requirement can move. Do not widen the role silently.