No shared definition
The same title describes builders, advisers, account managers, and something in between.
Open standard / Version 0.1.0
The role is real. The standard isn't.
The open community and competency framework for forward deployed engineers. A shared vocabulary for the engineers who make software land inside organizations they don't control.
Framework v0.1.0 / Updated
Section 01: THE PROBLEM01 02 03 04
The missing standard is the work.
A role this consequential shouldn't be reinvented inside every company and every hiring loop.
No common ladder
Experience is flattened into seniority labels that say little about what someone can do with a customer.
No observable language
“Strong communicator” can't tell a practitioner what good looks like or what comes next.
No return path
Hard-won customer knowledge stays trapped in one engagement instead of changing the product.
Section 02: THE FRAMEWORK
A mirror, not a bouncer.
Six independent competencies. Four observable levels. Read across to see the whole role; read down to find the next behavior.
01
Customer Context
Reading the organization you are deployed into
FDE IFDE IIFDE IIIFDE IV
Read this axis →02Technical Breadth
Many capabilities for one customer
FDE IFDE IIFDE IIIFDE IV
Read this axis →03Problem Framing
Turning a complaint into a solvable problem
FDE IFDE IIFDE IIIFDE IV
Read this axis →04Delivery Under Constraint
Shipping inside someone else's world
FDE IFDE IIFDE IIIFDE IV
Read this axis →05Communication and Influence
Moving people who do not report to you
FDE IFDE IIFDE IIIFDE IV
Read this axis →06Product Feedback Loop
Turning one deployment into everyone's product
FDE IFDE IIFDE IIIFDE IV
Read this axis →Section 03: START WHERE YOU ARE
Three ways into the work.
The route changes with the experience you already carry. These aren't courses. Each one starts with what you know and targets what the role demands next.
From Backend / product engineer
From Backend or Product Engineer
You can build. The gap is customer context, framing, and delivering inside an environment you don't control.
- Estimate
- 12 weeks
- Sequence
- 5 modules
From Consultant or Solutions Engineer
You already read rooms well. The gap is the engineering bar, and it's not negotiable.
- Estimate
- 20 weeks
- Sequence
- 5 modules
From Platform or Infrastructure Engineer
You're already good at other people's environments. The gap is product judgement and the customer-facing half.
- Estimate
- 14 weeks
- Sequence
- 5 modules
Section 04: WRITING
What practitioners are writing.
Practical notes, open arguments, and methods another practitioner can test.
Section 05: CHAPTERSYour city / Proposed
Start local. Stay honest.
This is early. One chapter is forming; there's no network to pretend already exists.
formingAsia Pacific
Hyderabad
The first chapter, and the one where we work out what a chapter actually is. Hyderabad has a deep bench of engineers working inside enterprise deployments, which makes it a good place to test whether this format is useful before we ask anyone else to run it.
Start one where you are.
Use the public playbook, name the first organizer, and build only what your local practitioners need.
Start a chapterThe standard stays open