Map forward-deployed work before building an FDE pipeline

The denominator changes the story

CyberMedia Research and Scaler report responses from 1,000 software engineers and 200 enterprise technology decision-makers. Financial Express places the fieldwork in September 2026 across eight Indian metropolitan areas and selected tier-two cities. The study says 88% of surveyed enterprises expect demand for forward-deployed engineering capabilities to rise by 2030, while 1% of surveyed engineers hold an explicit FDE title.

The same research says 56% of enterprises already conduct FDE-like work under other titles. Financial Express adds the important caveat that expectations are not confirmed hiring. The 1% and 56% figures describe different respondent populations and cannot be directly subtracted; the title gap therefore does not equal a capability gap.

Sponsor interests matter. Scaler offers training, and CMR classified respondents' exposure using task and customer-engagement information. Those facts do not invalidate the survey, but they make it important to preserve the questionnaire, classification rules, sample frame and distinction between interest, intention, posting and hire. Global posting growth should not be transplanted to India without a comparable denominator.

Build a task-to-title crosswalk

Start with work, not names. List recurring tasks: discovery with a customer, translating a business constraint, adapting a model, integrating enterprise systems, managing data boundaries, deploying to production, troubleshooting, measuring an outcome and transferring capability back to the client or internal owner. For each task, record frequency, consequence, autonomy, proficiency evidence and current role family.

Then separate four populations. Explicit FDEs hold the title. Embedded equivalents perform most of the task bundle under another title. Adjacent practitioners perform a subset and may need bounded development. Unrelated roles should not be counted merely because they use AI. Publish movement rules between groups so that a training provider, employer and engineer do not use different denominators.

Assess real work. A portfolio, simulation or supervised deployment can test integration, production judgement and customer communication better than a generic AI quiz. Preserve the environment and reviewer because success on a prepared demo does not establish readiness for regulated data, legacy systems or an ambiguous customer constraint.

Do not convert the 88% expectation into headcount. Ask employers for approved requisitions, task volume, delivery backlog, deployment failure modes and the work currently absorbed by solutions, product, consulting and customer-engineering teams. A renamed existing responsibility can improve ownership without creating a net new job; a genuine workload increase may require hiring, redesign or external capacity.

Keep geography and employer type visible. A multinational, services firm, startup and internal capability centre may use the same title for different customer boundaries and delivery risks. Report each group's denominator before comparing readiness or pay.

The counterargument is that a standard title improves market visibility. It can, if the task bundle and progression are explicit. But premature standardisation can hide local differences and create title inflation. Review compensation, travel, customer pressure, on-call expectations and learning time alongside technical requirements.

The immediate decision is a 30-day crosswalk for one business unit before funding an FDE academy or requisition target. This note does not forecast Indian employment or claim that training causes placement. It uses the survey's own title-versus-task contrast to make the denominator auditable.