From d8ca3e3bb0ca58eea5b5fc41421636de607cfdb2 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 3 Jun 2026 15:12:11 +0200 Subject: [PATCH] chore: sync content to repo (#10042) Co-authored-by: nilbuild <4921183+nilbuild@users.noreply.github.com> --- .../ai-engineering-skills@tTTDizQfuACFUoAAsTCt1.md | 8 ++++++++ .../content/backend-skills@kK16boEALRDQdRmFRphso.md | 8 ++++++++ .../content/communication@iaNbLDFrEDYEKwpkGFWts.md | 2 +- .../content/devops-skills@LRBwP7EQj4byox7yKdPAj.md | 8 ++++++++ .../dsa--system-design@aqrK4e6B8LFvFimKoqCNF.md | 10 ++++++++++ .../content/from-x-to-fde@XjxnVjO0fR2XNzBUSzA4L.md | 7 +++++++ .../content/frontend-skills@CNTtsgHntKdMsM7FgrrB8.md | 8 ++++++++ .../content/introduction@PBtnaTE_5AMOa5mxbhoT2.md | 8 ++++++++ .../content/linux-skills@CruESa0Ir9fSbxyX3ny13.md | 9 +++++++++ .../requirements-gathering@s4Kooj99igkE02P-D-dAU.md | 6 +++--- .../roles--responsabilities@YNaf7swqsvYaXRK6uevdv.md | 7 +++++++ ...hnical-scoping--sequencing@KqQHfy1Z8w-v8p73QkvG5.md | 2 +- .../content/what-is-an-fde@414WIX6TuK2h1jEtzRG2H.md | 7 +++++++ 13 files changed, 85 insertions(+), 5 deletions(-) create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/ai-engineering-skills@tTTDizQfuACFUoAAsTCt1.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/backend-skills@kK16boEALRDQdRmFRphso.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/devops-skills@LRBwP7EQj4byox7yKdPAj.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/dsa--system-design@aqrK4e6B8LFvFimKoqCNF.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/from-x-to-fde@XjxnVjO0fR2XNzBUSzA4L.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/frontend-skills@CNTtsgHntKdMsM7FgrrB8.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/introduction@PBtnaTE_5AMOa5mxbhoT2.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/linux-skills@CruESa0Ir9fSbxyX3ny13.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/roles--responsabilities@YNaf7swqsvYaXRK6uevdv.md create mode 100644 src/data/roadmaps/forward-deployed-engineer/content/what-is-an-fde@414WIX6TuK2h1jEtzRG2H.md diff --git a/src/data/roadmaps/forward-deployed-engineer/content/ai-engineering-skills@tTTDizQfuACFUoAAsTCt1.md b/src/data/roadmaps/forward-deployed-engineer/content/ai-engineering-skills@tTTDizQfuACFUoAAsTCt1.md new file mode 100644 index 000000000..2873cabdb --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/ai-engineering-skills@tTTDizQfuACFUoAAsTCt1.md @@ -0,0 +1,8 @@ +AI Engineering + +AI engineering involves building software systems that use machine learning models and large language models (LLMs) as components. This includes selecting models, integrating them via APIs, engineering prompts, managing context, and deploying AI features in production. AI engineering is at the core of the job of FDEs. It's what turns an AI model into a product that runs reliably inside a company's infrastructure. + +Visit the following resources to learn more: + +- [@article@What Is an AI Engineer? (And How to Become One)](https://www.coursera.org/articles/ai-engineer) +- [@video@AI, Machine Learning, Deep Learning and Generative AI Explained](https://www.youtube.com/watch?v=qYNweeDHiyU) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/backend-skills@kK16boEALRDQdRmFRphso.md b/src/data/roadmaps/forward-deployed-engineer/content/backend-skills@kK16boEALRDQdRmFRphso.md new file mode 100644 index 000000000..34bb8cdb2 --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/backend-skills@kK16boEALRDQdRmFRphso.md @@ -0,0 +1,8 @@ +# Backend + +Backend development refers to the server-side logic of a web application, including handling requests, running business logic, interacting with databases, and returning responses. Backend systems are typically built with Python, Node.js, Java, or Go, connected to databases and external services. FDEs who can build solid backend systems can own the full delivery of a feature rather than handing off at the API boundary. + +Visit the following resources to learn more: + +- [@article@What is backend? A comprehensive intro to server-side development](https://alokai.com/blog/what-is-backend) +- [@video@How The Backend Works](https://www.youtube.com/watch?v=4r6WdaY3SOA) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/communication@iaNbLDFrEDYEKwpkGFWts.md b/src/data/roadmaps/forward-deployed-engineer/content/communication@iaNbLDFrEDYEKwpkGFWts.md index bfe63b584..474ef6356 100644 --- a/src/data/roadmaps/forward-deployed-engineer/content/communication@iaNbLDFrEDYEKwpkGFWts.md +++ b/src/data/roadmaps/forward-deployed-engineer/content/communication@iaNbLDFrEDYEKwpkGFWts.md @@ -1,3 +1,3 @@ # Communication - + If you cannot explain what AI can and cannot do to a non-technical VP, you cannot be an FDE. Communication in this role is about translating between two different worlds: the technical reality of what you are building and the business reality of what the customer needs to justify the investment. That means being able to speak about token costs and latency in the same conversation where you are explaining ROI to an executive. It also means knowing when to say AI is not the right answer. \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/devops-skills@LRBwP7EQj4byox7yKdPAj.md b/src/data/roadmaps/forward-deployed-engineer/content/devops-skills@LRBwP7EQj4byox7yKdPAj.md new file mode 100644 index 000000000..4c40e1bb4 --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/devops-skills@LRBwP7EQj4byox7yKdPAj.md @@ -0,0 +1,8 @@ +# DevOps Skills + +DevOps is the practice of automating and streamlining how software is built, tested, and deployed. A forward-deployed engineer who knows DevOps can own the full deployment lifecycle, from spinning up infrastructure to shipping a containerized agent into a client's cloud environment, without depending on another team to get there. + +Visit the following resources to learn more: + +- [@article@What Is DevOps? A Guide to the Basics](https://www.coursera.org/articles/what-is-devops) +- [@video@DevOps In 5 Minutes](https://www.youtube.com/watch?v=Xrgk023l4lI) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/dsa--system-design@aqrK4e6B8LFvFimKoqCNF.md b/src/data/roadmaps/forward-deployed-engineer/content/dsa--system-design@aqrK4e6B8LFvFimKoqCNF.md new file mode 100644 index 000000000..aba7de0d1 --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/dsa--system-design@aqrK4e6B8LFvFimKoqCNF.md @@ -0,0 +1,10 @@ +# DSA & System Design + +Data Structures & Algorithms is the study of how to organize and process data efficiently. System Design is the practice of architecting large-scale, reliable systems. Together, they give FDEs the tools to make the right trade-offs when it comes to choosing the right data structure for an agent's memory layer, designing APIs that won't break under enterprise load, or architecting a multi-agent pipeline that scales across an organization. + +Visit the following resources to learn more: + +- [@article@Data Structures and Algorithms (DSA) Tutorial](https://www.tutorialspoint.com/data_structures_algorithms/index.htm) +- [@article@AI System Design: A Complete Guide](https://www.systemdesignhandbook.com/guides/ai-system-design/) +- [@article@System Design: Complete Guide](https://swimm.io/learn/system-design/system-design-complete-guide-with-patterns-examples-and-techniques) +- [@video@What Are Data Structures?](https://www.youtube.com/watch?v=bum_19loj9A) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/from-x-to-fde@XjxnVjO0fR2XNzBUSzA4L.md b/src/data/roadmaps/forward-deployed-engineer/content/from-x-to-fde@XjxnVjO0fR2XNzBUSzA4L.md new file mode 100644 index 000000000..14f315f34 --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/from-x-to-fde@XjxnVjO0fR2XNzBUSzA4L.md @@ -0,0 +1,7 @@ +# From X to FDE + +Three backgrounds tend to transition well into the FDE role: software engineers, consultants, and product managers. Software engineers already have the technical foundation but often need to develop the ability to communicate AI tradeoffs to non-technical stakeholders and build a portfolio that shows they can own a full deployment, not just write code. Consultants and PMs can already translate data into business outcomes, which is half the job, but need to close the gap on engineering by building real agents, RAG pipelines, and eval frameworks from scratch. + +Visit the following resources to learn more: + +- [@article@The Definitive Guide to Forward Deployed Engineer Interviews in 2026](https://www.sundeepteki.org/advice/the-definitive-guide-to-forward-deployed-engineer-interviews-in-2026) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/frontend-skills@CNTtsgHntKdMsM7FgrrB8.md b/src/data/roadmaps/forward-deployed-engineer/content/frontend-skills@CNTtsgHntKdMsM7FgrrB8.md new file mode 100644 index 000000000..604fd9385 --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/frontend-skills@CNTtsgHntKdMsM7FgrrB8.md @@ -0,0 +1,8 @@ +# Frontend + +Frontend development refers to the part of web development concerned with what users see and interact with in a browser. It covers HTML for structure, CSS for styling, and JavaScript for interactivity. FDEs who can build functional frontends are more self-sufficient in customer engagements, able to deliver end-to-end demos and working prototypes without depending on a separate frontend team. + +Visit the following resources to learn more: + +- [@book@Frontend Development Handbook](https://github.com/FrontendMasters/front-end-handbook-2019/blob/master/exports/Front-end%20Developer%20Handbook%202019.pdf) +- [@video@Frontend web development - a complete overview](https://www.youtube.com/watch?v=WG5ikvJ2TKA) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/introduction@PBtnaTE_5AMOa5mxbhoT2.md b/src/data/roadmaps/forward-deployed-engineer/content/introduction@PBtnaTE_5AMOa5mxbhoT2.md new file mode 100644 index 000000000..1fa6f541b --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/introduction@PBtnaTE_5AMOa5mxbhoT2.md @@ -0,0 +1,8 @@ +# Introduction + +A Forward Deployed Engineer is a software engineer who works directly inside a customer's environment to build, deploy, and stabilize AI systems. The role originated at Palantir, where engineers called Deltas would embed with clients, sometimes on military bases, to ship code overnight based on feedback from the field that same day. That same idea is now at the center of how companies like OpenAI and Anthropic are bringing AI into large enterprises. The job requires technical depth, the ability to read an unfamiliar codebase quickly, and the communication skills to explain what AI can and cannot do to a non-technical decision maker. + +Visit the following resources to learn more: + +- [@article@orward deployed engineer is AI’s hottest job](https://thenewstack.io/forward-deployed-engineer-fde-openai-google/) +- [@article@Forward-deployed engineer: The complete guide](https://www.rocketlane.com/blogs/forward-deployed-engineer) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/linux-skills@CruESa0Ir9fSbxyX3ny13.md b/src/data/roadmaps/forward-deployed-engineer/content/linux-skills@CruESa0Ir9fSbxyX3ny13.md new file mode 100644 index 000000000..f0d706bff --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/linux-skills@CruESa0Ir9fSbxyX3ny13.md @@ -0,0 +1,9 @@ +# Linux + +Linux is an open-source operating system used widely in servers, cloud environments, and developer workstations. Most production software runs on Linux, so being comfortable navigating a Linux system, managing processes, reading logs, and configuring services is a practical necessity for anyone building and deploying in real customer environments. + +Visit the following resources to learn more: + +- [@course@Linux for Noobs](https://labex.io/courses/linux-for-noobs) +- [@article@Practice Linux Fundamentals](https://labex.io/linuxjourney) +- [@video@Linux Fundamentals](ttps://www.youtube.com/watch?v=kPylihJRG70) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/requirements-gathering@s4Kooj99igkE02P-D-dAU.md b/src/data/roadmaps/forward-deployed-engineer/content/requirements-gathering@s4Kooj99igkE02P-D-dAU.md index 011330bb7..04b7d4b17 100644 --- a/src/data/roadmaps/forward-deployed-engineer/content/requirements-gathering@s4Kooj99igkE02P-D-dAU.md +++ b/src/data/roadmaps/forward-deployed-engineer/content/requirements-gathering@s4Kooj99igkE02P-D-dAU.md @@ -1,9 +1,9 @@ # Requirements Gathering - + Project requirements come from observation as much as from conversation. You watch how teams actually work, not just how they describe their work, because those two things are often different. The goal is to surface the undocumented workflow, the data source people actually trust, and the edge cases that would break an agent in its first week of production. Written requirements are useful, but the real requirements live in the room with the people doing the work. Visit the following resources to learn more: +- [@course@Requirements Gathering in Business Analysis](https://www.coursera.org/learn/requirements-gathering-in-business-analysis) - [@article@Requirements Gathering in Software Engineering](https://www.jamasoftware.com/requirements-management-guide/requirements-gathering-and-management-processes/what-is-requirements-gathering/) -- [@video@Requirement Gathering Techniques For A Business Analyst](https://www.youtube.com/watch?v=8EBWxW5Cn1g) -- [@course@Requirements Gathering in Business Analysis](https://www.coursera.org/learn/requirements-gathering-in-business-analysis) \ No newline at end of file +- [@video@Requirement Gathering Techniques For A Business Analyst](https://www.youtube.com/watch?v=8EBWxW5Cn1g) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/roles--responsabilities@YNaf7swqsvYaXRK6uevdv.md b/src/data/roadmaps/forward-deployed-engineer/content/roles--responsabilities@YNaf7swqsvYaXRK6uevdv.md new file mode 100644 index 000000000..a006f54d1 --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/roles--responsabilities@YNaf7swqsvYaXRK6uevdv.md @@ -0,0 +1,7 @@ +# Roles & Responsibilities + +The FDE job has three phases: audit, evals, and deployment. In the audit phase, you embed with different teams inside the customer's organization, map their workflows, identify bottlenecks, and decide where AI can create real value and where it cannot. In the evals phase, you build systems to measure whether the AI is actually working, not just whether it produces an answer, but whether it reasons through problems the way a skilled human would. In the deployment phase, you ship the system into production, starting with the smallest possible unit of autonomy and layering on capabilities only after each step is proven to work. + +Visit the following resources to learn more: + +- [@article@Forward-deployed engineer: The complete guide](https://www.rocketlane.com/blogs/forward-deployed-engineer) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/technical-scoping--sequencing@KqQHfy1Z8w-v8p73QkvG5.md b/src/data/roadmaps/forward-deployed-engineer/content/technical-scoping--sequencing@KqQHfy1Z8w-v8p73QkvG5.md index ebd9b5475..80eac52f8 100644 --- a/src/data/roadmaps/forward-deployed-engineer/content/technical-scoping--sequencing@KqQHfy1Z8w-v8p73QkvG5.md +++ b/src/data/roadmaps/forward-deployed-engineer/content/technical-scoping--sequencing@KqQHfy1Z8w-v8p73QkvG5.md @@ -5,4 +5,4 @@ Technical scoping involves breaking a project into discrete tasks, estimating th Visit the following resources to learn more: - [@article@How to effectively scope your software projects](https://medium.com/free-code-camp/how-to-effectively-scope-your-software-projects-from-planning-to-execution-e96cbcac54b9) -- [@video@Project Scope Statement [IN 4 EASY STEPS]](https://www.youtube.com/watch?v=QDLk2QIuJkg) \ No newline at end of file +- [@video@Project Scope Statement \[IN 4 EASY STEPS\]](https://www.youtube.com/watch?v=QDLk2QIuJkg) \ No newline at end of file diff --git a/src/data/roadmaps/forward-deployed-engineer/content/what-is-an-fde@414WIX6TuK2h1jEtzRG2H.md b/src/data/roadmaps/forward-deployed-engineer/content/what-is-an-fde@414WIX6TuK2h1jEtzRG2H.md new file mode 100644 index 000000000..3672a384b --- /dev/null +++ b/src/data/roadmaps/forward-deployed-engineer/content/what-is-an-fde@414WIX6TuK2h1jEtzRG2H.md @@ -0,0 +1,7 @@ +# From X to FDE + +Three backgrounds tend to transition well into the FDE role: software engineers, consultants, and product managers. Software engineers already have the technical foundation but often need to develop the ability to communicate AI tradeoffs to non-technical stakeholders and build a portfolio that shows they can own a full deployment, not just write code. Consultants and PMs can already translate data into business outcomes, which is half the job, but need to close the gap on engineering by building real agents, RAG pipelines, and eval frameworks from scratch. + +Visit the following resources to learn more: + +- [@article@The Definitive Guide to Forward Deployed Engineer Interviews in 2026](https://www.sundeepteki.org/advice/the-definitive-guide-to-forward-deployed-engineer-interviews-in-2026) \ No newline at end of file