FORMWEFTBusiness diagnosis
Ability to interview owners and users, and break down triggers, steps, inputs, outputs, exceptions, value, and stop conditions.
FDE Capability Guide
Six capability dimensions to judge the real starting point of an enterprise FDE engineer.
It doesn't matter how many hours of courses you've watched; what matters is whether you can provide evidence of tasks, systems, evaluations, launches, and handovers in real business.
Six-Dimension Capability Map
Each dimension should correspond to real artifacts. Being able to explain concepts does not equal being able to take on on-site delivery.
Data and Systems
Can trace sources, fields, permissions, interfaces, update frequency, conflicts, failures, and existing technical debt.
AI workflow building
Can design models, retrieval, tool calls, state, human confirmation, and fallback - and turn them into a runnable version.
Evaluation and governance
Can establish representative samples, quality and permission checks, rollout criteria, audit, and human disposition.
Production and operations
Can handle deployment, monitoring, cost, performance, alerts, knowledge updates, versioning, and support.
On-site delivery
Can manage scope, communication risk, push for confirmation, document evidence, train users, and complete internal handover.
Four levels, no certificates as evidence
Levels are used to choose the next real task, not as a permanent identity. Re-assess whenever the system and scope of responsibility change.
L1 Can understand
Can restate business processes, identify data and system boundaries, and complete structured records under mentor guidance.
L2 Can build
Can build a bounded workflow, tool connections, and representative tests with pair support.
L3 Can go live
Can complete permissions, evaluation, monitoring, rollback, and human takeover, and go into production within a limited scope.
L4 Can hand over
Can independently lead business interviews, technical decisions, launch retrospectives, and knowledge transfer, and mentor the next engineer.
What to prepare for a capability re-assessment
Choose a real business line you recently worked on, bring all materials, then decide the next stage.
Task evidence
Problem map, flow diagram, responsible person, and clear success and stop conditions.
Engineering evidence
System map, code or configuration, interface and permission records, versions, and failure handling.
Validation evidence
Normal and abnormal samples, evaluation results, human judgment, rollout criteria, and unresolved issues.
Operations evidence
Release, monitoring, alerts, rollback, usage feedback, retrospectives, and internal handover records.
Use one real project as a capability baseline
State the background of the person to be developed, the target business line, and the current system; we design the development starting point based on verifiable artifacts.