Most engineering job descriptions list technologies and responsibilities. For a Forward-Deployed Engineer, that approach attracts the wrong people. FDE roles should lead with the problem, the outcome, and the systems to be built, because that is what great FDEs respond to. Use these templates as starting points and adapt them to your specific problem and engagement model.
A strong Forward-Deployed Engineer role description leads with the business problem and the outcome, lists the systems the FDE will build, states the engagement model and success metrics, and keeps requirements focused on shipped work rather than long tool checklists. Templates below cover project, embedded, fractional, and permanent engagements.
What every FDE role description should include
Lead with the business problem and the outcome you want. Then describe the systems the FDE will build, the engagement model and duration, the success metrics, and the environment they will work in. Keep required skills short and focused on the ability to ship and own outcomes.
Template: short-term project FDE
'We need a working [system] deployed within [timeframe] to solve [problem]. You will own discovery, build, and deployment, and hand over a maintainable system with documentation. Success looks like [metric]. You have shipped similar systems end-to-end and are comfortable working directly with our team.'
Template: embedded / transformation FDE
'You will embed with our [team] for [duration] to transform how we [process]. You will ship a series of AI workflows, automations, and internal tools, prioritising the highest-impact problems first. Success looks like [metrics over time]. You thrive close to the business and can turn ambiguous problems into deployed systems.'
Template: fractional and advisory FDE
'We need [X days per week/month] of forward-deployed engineering capacity to build and maintain [systems] and advise on [decisions]. You will ship working software and help us make sound implementation choices. Success looks like [outcomes]. You are senior enough to prioritise ruthlessly and deliver in limited time.'
Role description essentials
- Problem and outcome stated in the first two lines
- Systems the FDE will build listed clearly
- Engagement model and duration specified
- Success metric included
- Working environment and data access described
- Requirements focused on shipped work, not tool lists
