The Forward Deployed Engineer, Chapter 6: The Soft Stack — Diplomacy and Strategy

This is Part 6 of a series walking through my book The Forward Deployed Engineer. In the previous chapter, we covered the AI frontier. This one closes Part II with the part of the skillset most often dismissed as soft — and most often the difference between a competent FDE and a great one.

I want to begin by pushing back on the framing of “soft skills” itself. The term is a holdover from an era when engineers were expected to do engineering and managers were expected to do communication, and the soft skills lived with the managers. The FDE has to do both, and the skills involved are as crisp, as testable, and as trainable as anything in the coding rounds. Calling them soft is, in my experience, mostly a way for engineers who never developed them to avoid admitting that they should have.

The two consulting-world disciplines that matter most are MECE decomposition and the Pyramid Principle. MECE — mutually exclusive, collectively exhaustive — is the discipline of breaking a problem into pieces that don’t overlap and don’t leave gaps. It is the antidote to the kind of analysis that sounds thorough until you notice it’s also redundant in three places and missing one whole category. The Pyramid Principle is the discipline of communicating the conclusion first, then the supporting structure, then the detail beneath each branch. It is the discipline that makes the difference between a senior FDE who can hold the attention of a Chief Risk Officer for fifteen minutes and one who loses it in three. Both can be taught. Both can be tested in an interview. And an FDE who can do neither will lose every meeting that matters.

Most engagements begin with a stakeholder map — literally a document, by name and role, that captures who has authority over what, who can block what, who needs to be informed about what, and what each one of them is personally motivated by. The map sounds trivial. It is not. The FDE who skips it is the FDE whose deployment runs into a stakeholder in week eight that nobody had identified in week one, and whose objections turn out to be the load-bearing ones. Related to the stakeholder map is the skill of translating the customer’s goals into a PRD that their own team can sign and execute against. This is more PM work than engineering work, and it is one of the most under-trained skills in the entire function.

Managing the Skeptic, and the Diplomatic Register

Of all the stakeholder patterns, the one that deserves its own treatment is the Skeptic. Every long enterprise engagement has one, and they are usually the most senior technical person in the room. They have watched technology promises fail before. They are not going to be sold to. The instinct of most vendors is to either avoid the Skeptic or to try to win them over with charm and demos. Both moves lose. The move that works is to give the Skeptic a real role — usually as the first stress-tester of the smallest piece of the deployment — and to treat their objections as load-bearing data rather than political resistance. Done well, the Skeptic becomes the deployment’s strongest internal advocate. They have, after all, personally verified it.

Around all of this is what I call the Diplomatic Register: the specific tone an FDE has to operate in, somewhere between platform engineer and management consultant, that holds technical credibility while reading the political room. Engineers who are too casual in this register lose authority; engineers who are too formal lose connection. The register is learnable, and most senior FDEs I’ve worked with arrived at it by deliberate imitation of someone they admired. There is no shortcut, but there is a model to copy.

Stress, Composure, and Politics on Both Sides

The role is high-stress in a specific way. The engagements are long, the stakes are real, and the political pressure runs in two directions at once — from the customer’s side, and from your own company’s side. Stress inoculation is a learnable discipline, and the chapter walks the small number of moves — structured downtime, rotation, peer support — that prevent the burnout death spiral I describe in Chapter 13. The internal politics deserve their own paragraph: the FDE operates not only inside the customer’s politics but also inside their own company’s, and the second front is the one that produces the most surprise for engineers who joined expecting the role to be customer-facing in a single direction. Tomorrow: discovery, where all of this skillset gets put to work in the first two weeks of an engagement.