Forward Deployed Engineer — My Learning Roadmap

FDE sits where software, infrastructure, AI, and the customer meet. A roadmap for learning the job, not a title change.

A Forward Deployed Engineer (FDE) sits at the intersection of software engineering, infrastructure, AI, and the customer. The job isn’t simply to write code—it is to understand a real-world problem, figure out how the pieces fit together, and build a working solution.

This is the skill set I’m working toward.

The Core Skills

Programming

  • Python for automation, scripting, AI integrations, and rapid development
  • Rust for systems, backend services, and high-performance applications
  • JavaScript/TypeScript for modern web applications
  • SQL and PostgreSQL for working with data

Web & APIs

  • HTTP/HTTPS
  • REST APIs
  • JSON
  • Authentication and OAuth
  • WebSockets
  • Backend/frontend architecture
  • API integration

Linux & Infrastructure

  • Linux administration
  • Bash
  • SSH
  • Networking
  • DNS and TLS
  • Processes and services
  • systemd
  • Git
  • Docker
  • Kubernetes fundamentals
  • CI/CD
  • Logging and troubleshooting

Cloud

  • AWS, Azure, or GCP fundamentals
  • Compute
  • Storage
  • Networking
  • IAM
  • Containers
  • Cloud databases
  • Monitoring and logging

AI & LLM Systems

  • LLM APIs
  • Prompting
  • Structured outputs
  • Embeddings
  • Vector databases
  • RAG
  • Tool/function calling
  • AI agents
  • Evaluation and observability

Problem Solving

An FDE must be comfortable entering an unfamiliar environment and figuring out why something isn’t working.

The mindset is:

Browser → API → Authentication → Network → Service → Database → External System

Find where the problem is, understand why it is happening, and build the solution.

The Customer Side

This is what makes an FDE different from a traditional software engineering role.

An FDE needs to be able to:

  • Understand business requirements
  • Ask good questions
  • Communicate with technical and non-technical people
  • Explain complicated systems clearly
  • Prototype quickly
  • Work with ambiguity
  • Adapt when requirements change
  • Demonstrate solutions
  • Translate business problems into engineering solutions

My Practical Learning Path

Rather than trying to learn everything at once, the roadmap is:

Linux → Networking → Python → APIs → SQL → Docker → Cloud → AI APIs → Rust → Web Applications → Customer/Problem Solving

The goal isn’t to become an expert in every technology.

The goal is to become the engineer who can walk into a complicated technical environment and say:

Give me the problem. I’ll figure out how the pieces fit together and build a working solution.

Projects That Build the Skill Set

A practical FDE portfolio could grow from one project:

  1. Build a Rust/Axum API
  2. Build a Leptos frontend
  3. Add PostgreSQL
  4. Dockerize the application
  5. Deploy it to the cloud
  6. Add an LLM API
  7. Add authentication
  8. Add logging and monitoring
  9. Document the architecture
  10. Write a case study explaining the original problem, the solution, and the results

That becomes more than a collection of tutorials.

It becomes evidence that I can understand a problem, integrate technologies, build a solution, deploy it, troubleshoot it, and explain it.

The FDE Mindset

The technology will change.

The fundamental skill won’t:

Understand the problem → understand the systems → build the solution → deploy it → troubleshoot it → explain it.

That’s the direction I’m working toward.