What companies are learning from the forward-deployed engineer model after a year

# The forward‑deployed engineer model: what's working so far

Where speed shows up

The on‑site approach compresses the feedback loop: day one often ends with a working integration, day two focuses on user training and monitoring, then the team iterates with weekly virtual check‑ins.

Concrete examples of what FDEs deliver

• Superhuman: Baucom transformed a 400‑page style guide for a multinational publisher into a set of custom agents—one per sub‑brand—that flag deviations, underline suggested corrections and link to the guide entries for writers to review. This is a bespoke productivity feature built around the customer's existing workflow.

• Infor: An FDE built a system for an industrial manufacturing customer that flags itself when it needs attention, reducing the need for constant dashboard monitoring and adapting to the customer's tolerance for automated alerts.

These examples show the FDE role blends product engineering, integration work and user training to create tailored solutions that fit specific operational and trust thresholds.

Demand and enterprise commitments

Job listings for FDE roles rose sharply—Indeed data showed an increase of more than 729% between April 2025 and April 2026 (reported to Business Insider). Large vendors are committing money and teams: Amazon announced a $1 billion FDE unit and Microsoft a $2.5 billion initiative. Anthropic, OpenAI and Salesforce have also announced similar efforts.

Practical challenges organizations are working through

• Trust and customization: Customers have varying comfort levels with AI. FDEs must design solutions that match a customer's stage of adoption and tolerance for automation, especially where false positives or automated actions carry cost or safety implications.

• Staffing and sustainability: Embedding engineers at customers creates scheduling pressure and travel demands. Baucom described his calendar as a constant Tetris of calls and on‑site work. Companies need rotation plans, clear role definitions and career paths for engineers who split time between product teams and deployments.

• Scope control: Rapid turnaround raises expectations. Firms must define clear project boundaries so FDEs can deliver quick wins without creating an unsustainable stream of bespoke features.

How teams operate day to day

The current, effective cadence reported by practitioners is straightforward: get everyone together on site to finish integration, train users immediately, monitor performance, collect feedback, iterate quickly and maintain weekly check‑ins. That sequence shortens delivery cycles and focuses early work on user adoption as much as technical delivery.

Bottom line

The FDE model shows measurable benefits in speed and customer satisfaction when applied to well‑scoped problems that require close coordination. Early adopters are proving the approach works in practice, while also learning the organizational practices—staffing models, travel cadence, boundary setting and trust calibration—needed to scale it beyond pilot projects.