Who are FDSE?

 

                                                                Generated by Gemini

For the last 28 years and more I have been working as Solutions Engineer / Solutions Architect (SE/SA) + Professional Services / Implementation Engineer + Customer-Facing Software Engineer together combined.

Various companies I have worked on pre-sales technical scoping & integration design resembled SE/SA work or/and FDSEs inherit full production-grade coding responsibilities and Enterprise deployment & customisation tasks.

From understanding requirements from internal domain expert like here in BNY or from pre sales team of a SaaS or AI company. Never thought about what exactly my role or position is. Responsibilities always came first.

Despite being a hard-core computer science student with vast fundamental knowledge, including microprocessor architecture, operating systems, compiler design, various types of networking, protocols, and programming in various environments and languages from mainframes to microcontrollers to IoT applications. I always solve the real problem smartly. Recent years my roles named Forward-Deployed Engineer = Solutions Engineer + Implementation Engineer + Full Software Engineer, merged into one high-ownership role.

According to multiple analyses of the FDE role's evolution, especially the history of Palantir’s “Deltas” (the original forward‑deployed engineers), the modern FDE function grew out of three older roles blended together:

1. Solutions Engineer / Solutions Architect (SE/SA)

Before the FDE concept existed, companies relied heavily on Solutions Engineers or Solutions Architects to scope problems, design integrations, and work with customers during implementation.

  • These roles handled pre‑sales technical scoping, early prototypes, integration discussions, and acted as intermediaries between clients and product teams.
  • They were customer-facing, but rarely wrote large amounts of production code.

This corresponds to the FDE’s product scoping, architecture, and integration responsibilities.

2. Professional Services / Implementation Engineer

Enterprise software companies traditionally used Professional Services Engineers or Implementation Specialists for deployment and custom setup.

  • They installed systems, configured environments, migrated data, and ensured the product worked in a messy customer infrastructure.
  • This is exactly the “embedded implementation” aspect that FDEs now own.

This implementation-heavy model is referenced as the predecessor to the FDE paradigm.

3. Traditional Software Engineer (but customer-aligned)

Palantir explicitly blended full software engineering responsibilities — designing, building, debugging, and deploying production systems — into a customer-embedded role.

  • Traditional SWE: builds “one capability for many customers.”
  • Early Palantir “Delta” / modern FDE: solves “one customer’s many problems” with real production code.

This SWE component became essential because typical Professional Services or Solutions Engineers could not write and ship production-grade code, which Palantir desperately needed for complex government and enterprise deployments.

Due to not came from pure engineering background never got the opportunity or position I deserved. However, I always love the challenges to solve other facing whether customer, client or else. Continue learning and taking on challenges to learn entirely new fields and solve real problems with ownership felt great.

Comments

Popular posts from this blog

Self-contained Raspberry Pi surveillance System Without Continue Internet

COBOT with GenAI and Federated Learning

AI in Education: Embracing Change for Future-Ready Learning