Which engineering skills matter most?
Not the fashionable ones. The work is integration: reading documents in inconsistent formats, matching records across systems that disagree, connecting to interfaces designed for people rather than software, and wrapping all of it in permissions, logging and fallbacks. An engineer who has only built greenfield products will struggle. One who has spent years making old systems talk to each other will recognise every problem on day one.
AI-specific skill matters, but less than people assume. Choosing and prompting a model is learnable in weeks. Knowing when a model is confident enough to act without a person, and building the review step for when it is not, takes experience of systems failing.
Why does temperament matter so much?
Because half the job is sitting with an operations team and understanding their day. An engineer who finds that boring, or who treats the team as users to be managed rather than experts to learn from, will miss the detail that decides whether the system works. The best forward deployed engineers are curious about other people's jobs. They ask what happens at month-end. They notice the workaround nobody mentions. They are comfortable being the least knowledgeable person in the room about the business, for a week, and they use that week well.
What does judgement look like?
Saying no. A team can list twenty things that could be automated; two of them will pay for the engagement and the rest will consume it. A good forward deployed engineer picks the two, explains why the others are not worth it yet, and resists the pressure to do everything at once. Judgement also means knowing when the answer is not AI at all: a changed form, a small script, an off-the-shelf tool. Engineers who need every problem to be an AI problem are expensive.
What are the six skills, in short?
Skill | What it looks like |
|---|---|
Integration engineering | Has made systems that disagree work together, more than once |
Production habits | Permissions, logging, review steps and a kill switch come up unprompted |
Curiosity about operations | Asks what happens on a bad day, not only a normal one |
Plain communication | Can explain a design to a head of operations without jargon |
Judgement about scope | Has a story about something they refused to build |
Staying power | Has run what they built, and answered the phone when it broke |
How do you tell in an interview?
Ask for a system they shipped, who uses it today, and what has gone wrong with it since launch. A strong candidate answers all three without hesitation. Ask what they turned down on their last project and why. Ask them to explain a past system to you as if you ran the team that uses it. The engineers who can do that are the ones who will do it for your team. FetchSky's own engineers are selected on the same questions; see forward deployed engineers, and the engineering partner guide for how the role fits alongside other engagement models.
Frequently asked questions
Do forward deployed engineers need to be senior?
Usually. The judgement about scope and the production habits come from experience, and the role carries decisions a junior engineer should not have to make alone.
Is domain knowledge essential?
Helpful but not essential. The first week exists to acquire it. Curiosity matters more than prior knowledge.
Can a data scientist be a forward deployed engineer?
If they can take a system into production, yes. Many cannot, and the gap between a notebook and a running system is the whole job.
Where can I read about hiring one?
How to hire a forward deployed engineer.