本页以 FDE FAN 的第一视角讲解知识：先讲概念，再讲方法、图表、训练任务。底部保留参考来源，方便继续阅读。 This page teaches in FDE FAN's own voice: concepts first, then methods, visuals, and practice tasks. References are kept at the bottom for further reading.
知识结构地图Knowledge Structure Map
| 知识层级Knowledge Layer | 我们要掌握什么What We Need to Master | 训练产物Training Artifact |
|---|---|---|
| 核心论点Core thesis | FDE 位于客户、产品和工程之间，把业务问题带到现场解决。FDEs sit between customer, product, and engineering and solve business problems in the field. | 定义岗位边界。Define role boundaries. |
| 角色能力Role capabilities | 既要沟通业务，又要具备工程实现和部署能力。They need both business communication and engineering/deployment ability. | 训练跨界交付。Train hybrid delivery. |
| 区别岗位Role distinction | FDE 不等同于售前、实施、前端或客服，但会借用这些岗位的部分能力。FDEs are not presales, implementation, front-end, or support, though they borrow capabilities from each. | 我们需要岗位地图。We need a role map. |
| 交付责任Delivery accountability | FDE 要让方案可运行、可验证、可移交，而不是只给建议。FDEs make solutions runnable, testable, and transferable, not merely advisory. | 评分要看产物。Assessment should inspect artifacts. |
核心观点Key Takeaways
FDE 是跨界角色，不是传统售前、实施、前端或客服的简单替代。FDE is a hybrid role, not a simple replacement for presales, implementation, front-end, or support.
真正的能力在于把模糊业务问题变成可运行、可验证、可移交的系统。The real skill is turning ambiguous business problems into running, testable, transferable systems.
角色边界要清楚：能做试点和交付包，但不能无授权承担企业核心系统责任。Boundaries matter: FDEs can build pilots and delivery packages, but should not own core enterprise systems without mandate.
FDE 与相邻岗位FDE and Adjacent Roles
| 层级Layer | 含义Meaning | FDE 产物FDE Artifact |
|---|---|---|
| 售前Presales | 证明价值、赢得信任Prove value and build trust | FDE 还要把方案做出来并上线验证FDEs also build and validate the solution |
| 传统前端Front-end engineer | 实现页面和交互Implement UI and interactions | FDE 还要理解业务流、Agent 和交付文档FDEs also understand workflow, agents, and delivery docs |
| 实施顾问Implementation consultant | 配置系统和培训客户Configure systems and train customers | FDE 还要能补齐轻量工程和自动化FDEs also fill lightweight engineering and automation gaps |
深度讲义Deep Study Notes
1. FDE 的难点是跨界，而不是“什么都会一点”1. The difficulty of FDE is hybridity, not shallow generalism
FDE 不是简单把售前、产品、前端、实施和客服揉在一起，而是在客户现场承担一个清晰责任：把模糊业务问题转成可运行解决方案，并把解决方案反馈给产品和工程体系。跨界不是泛泛而谈，而是围绕交付责任组织能力。An FDE is not a casual blend of presales, product, front-end, implementation, and support. The field responsibility is clear: convert ambiguous business problems into running solutions and feed those solutions back into product and engineering systems. Hybridity is organized around delivery accountability.
2. 与相邻岗位的边界2. Boundaries with adjacent roles
售前证明价值但通常不负责长期维护；传统前端实现界面但不一定进入客户业务流；实施顾问配置系统但不一定补工程缺口；产品经理定义需求但不一定现场部署。FDE 的独特性在于同时接触客户现场和工程产物，并对试点交付的闭环负责。Presales proves value but usually does not maintain the solution; front-end engineers build interfaces but may not enter customer workflows; implementation consultants configure systems but may not fill engineering gaps; product managers define requirements but may not deploy in the field. The FDE is distinctive because they touch both field context and engineering artifacts while owning the pilot delivery loop.
3. 我们训练哪些行为3. Behaviors we train
我们不只考察学生会不会写页面，而要观察学生是否会问澄清问题、是否能指出数据缺口、是否能画出业务流程、是否能设计最小可行 Demo、是否能部署到稳定 URL、是否能写清楚边界和测试方法。这些行为才构成 FDE 的岗位能力。We do not only check whether a student can build a page. We observe whether the student asks clarifying questions, identifies data gaps, maps workflows, designs a minimum viable demo, deploys to a stable URL, and documents boundaries and tests. These behaviors form the FDE role capability.
4. 对招生承诺的约束4. Constraints on enrollment promises
因为 FDE 接近客户现场，我们必须明确边界：学员可以做试点、Demo、交付包和复盘，但不承诺就业、薪资、接单成功，也不能让初学者独立承担企业核心系统。这不是弱化课程价值，而是建立可信度。Because FDE work approaches the customer field, we state boundaries: learners can build pilots, demos, delivery packages, and retrospectives, but we do not promise jobs, salaries, contracting success, or allow beginners to independently own core enterprise systems. This does not weaken the course; it builds trust.
本课训练目标Training Goal
我们在首页和评分标准里继续强调边界：FDE 是轻量工程交付岗位，不承诺就业、接单或独立承担核心系统。We keep the boundary clear in the homepage and assessment standard: FDE is a lightweight engineering delivery role, not a promise of employment, contracting, or independent core-system ownership.
课堂任务Classroom Assignments
画出 FDE 与售前、前端、实施、产品经理的责任边界图。Draw a responsibility map separating FDE, presales, front-end, implementation, and product management.
为一个项目写“我能负责什么 / 不能负责什么”的边界声明。Write a boundary statement for a project: what I can own and what I cannot own.
把一次客户需求改写成可运行 Demo、验收标准和移交说明。Turn a customer request into a running demo, acceptance checks, and handoff notes.
引用Citation
Invisible Technologies. What Is Forward Deployed Engineering?. https://invisibletech.ai/blog/what-is-forward-deployed-engineering. Accessed 2026-06-28.