Day 208 — The Evolving SDLC: From Software Engineers to AI Engineers to Forward Deployed Engineers
4th October 2026, Netherlands — For decades, the Software Development Life Cycle (SDLC) followed a fairly predictable path:
Requirements → Design → Development → Testing → Deployment → Maintenance
That model is still relevant, but the environment around software has changed dramatically.
Applications are now cloud-native, API-driven, distributed, AI-enabled, highly integrated, and expected to evolve continuously. More importantly, companies are no longer asking only:
“Can we build this software?”
They are increasingly asking:
“Can we solve this business problem quickly, integrate the solution into our existing environment, make it intelligent, secure it, and operate it reliably?”
This evolution is creating a shift from the traditional Software Engineer, to the AI Engineer, and increasingly to the Forward Deployed Engineer (FDE).
Stage 1: The Software Engineer
A Software Engineer primarily focuses on building reliable software systems.
The traditional responsibility is to translate requirements into maintainable software:
Requirement → Architecture → Code → Test → Deploy → Maintain
Software Engineers typically have strong expertise in programming, data structures, APIs, databases, testing, system design, scalability and production-quality software.
Their priorities often include:
- Clean and maintainable code
- Testing
- Reliability
- Scalability
- System architecture
- Performance
- Long-term maintainability
The Software Engineer remains the foundation of modern technology organizations.
But AI has introduced another layer.
Stage 2: The AI Engineer
An AI Engineer takes software engineering principles and combines them with LLMs, machine learning models, retrieval systems and AI workflows.
The development lifecycle starts looking different:
Problem → Data → Model/LLM → Prompt → Retrieval → Evaluation → Application → Production
An AI Engineer may work with:
- LLM APIs
- Prompt engineering
- Embeddings
- Vector databases
- RAG
- Knowledge graphs
- Model evaluation
- Tool/function calling
- Agentic workflows
- Multimodal models
- AI observability
The challenge is no longer deterministic software alone.
Traditional code might behave like:
Input → Logic → Output
Get Alok Rahul’s stories in your inbox
Join Medium for free to get updates from this writer.
AI applications behave more like:
Input → Context → Model → Reasoning → Tools → Retrieval → Output
That introduces uncertainty.
Therefore, AI engineering requires new practices around evaluation, guardrails, hallucination management, retrieval quality, observability and AI security.
The role consequently places much more emphasis on applied AI and LLM systems than a traditional software-engineering position.
Stage 3: The Forward Deployed Engineer
The Forward Deployed Engineer takes this evolution one step further.
An FDE does not simply receive a well-defined requirement and implement it.
Often, the requirement itself needs to be discovered.
The lifecycle becomes:
Business Problem → Discovery → Requirements → Prototype → Architecture → Integration → Security → Production → Feedback → Business Outcome
This is fundamentally different.
Imagine a customer saying:
“We have thousands of internal documents, multiple databases, Jira, old SOAP services and several teams. We want AI to help employees find information and automate workflows — but users must only access information they are authorized to see.”
This is not simply a coding problem.
The engineer needs to understand the business workflow, enterprise data, existing infrastructure, security boundaries and expected outcome before deciding what should actually be built.
That is where the Forward Deployed Engineer becomes valuable.
An FDE may need to combine:
Python + APIs + Cloud + Containers + LLMs + RAG + Agents + Databases + Enterprise Integrations + IAM + Security + Observability
Enterprise integration becomes especially important because real organizations do not consist entirely of modern APIs. AI systems may need to interact with SQL databases, XML/SOAP services, Jira, collaboration platforms and existing internal systems. FDE BootCamp V1.0 (1)
Software Engineer vs AI Engineer vs FDE
The roles overlap significantly. The difference is primarily where each engineer spends their attention.
A Software Engineer asks:
How should we engineer this system?
An AI Engineer asks:
How can AI solve this problem reliably?
A Forward Deployed Engineer asks:
What is the actual problem, what should we build, and how do we make it work inside this customer’s environment?
The FDE role therefore tends to emphasize rapid prototyping, stakeholder interaction, applied AI, enterprise data and integration while still requiring strong system-architecture and production-engineering fundamentals.
The SDLC Is Becoming a Continuous Discovery Cycle
Perhaps the biggest change is that modern SDLC is becoming less linear.
Traditional SDLC:
Plan → Build → Test → Deploy
Modern AI-driven development:
Discover → Prototype → Evaluate → Integrate → Secure → Deploy → Observe → Learn → Improve
And then the cycle repeats.
For engineers, this means knowing one technology deeply is no longer enough.
The most valuable engineers will increasingly be those who can connect software, infrastructure, AI, security and business context.
That is why I see the Forward Deployed Engineer not as a replacement for Software Engineering or AI Engineering, but as an evolution in how engineering expertise is applied to real-world problems.
The future engineer in not asked:
“Can you build this?”
They are asked:
“Here is the problem. Can you figure out what we should build — and make it work in production?”
Thus, it changes the SDLC completely.
