Forward-Deployed Engineer (FDE) role definition and responsibilitiesFDE as a return to customer-driven business models vs. product-driven approachesInformation processing and data collection as core FDE work vs. interface customizationComparison of FDE model to historical development methodologies (Waterfall, Agile)FDE emergence as a consulting service and potential business model evolutionChallenges and limitations of scaling the FDE approach

Participants: rafa_0x, sachbenny, thewanderingeditor, timber1997, holajorge, mihir0k, stevebeans., oneiromancer2665

The SIGPfB group discussed the emerging role of Forward-Deployed Engineers (FDEs) and its implications for software business models. The conversation revealed that FDEs primarily conduct information processing and context collection for customers rather than traditional implementation work, reversing the product-driven approach that has dominated Silicon Valley. Participants noted that this model represents a return to customer-driven business practices, exemplified by Palantir's Foundry platform, and functions as an extended, machine-augmented version of Waterfall development. The role requires significant in-person engagement and trust-building, making it difficult to scale with traditional staffing approaches.

The group explored whether FDEs signal a revival of Waterfall methodology's value or represent an entirely new design space, with mixed conclusions. Key observations included that FDEs function similarly to traditional service providers (consultants, craftspeople) and may crystallize into a standalone consulting service. Notably, FDEs are granted the ability to 'break protocol' on both sides, suggesting their value lies in navigating and bridging organizational and technical boundaries. The discussion concluded that this model may be particularly effective for medium-sized organizations (10-100M revenue) adopting AI and agent-based solutions, where rapid, iterative customer engagement is more valuable than pre-defined specifications.

  • FDE work is primarily information processing and context collection rather than interface customization, representing a shift from product-driven to customer-driven business models similar to Palantir's approach.
  • The FDE role resembles traditional service-based relationships (handymen, gardeners, consultants) and may evolve into a standalone consulting service comparable to Big Four consulting firms.
  • FDEs are uniquely positioned to 'break protocol' both internally and with clients, requiring significant in-person trust-building and contextual knowledge that creates high social barriers to scaling.
  • The rise of FDEs may indicate that Waterfall-style development could regain value in certain contexts, or represent an entirely new design space that challenges the Agile dominance of Silicon Valley.
  • AI models function as customer-driven collections of stable behavioral patterns rather than explicit problem-solving tools, enabling FDEs to bridge the gap between generalized AI capabilities and specific customer needs.
View discussion in Discord →