<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Datamarcos</title>
    <description>The latest articles on DEV Community by Datamarcos (@datamarcos).</description>
    <link>https://dev.to/datamarcos</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257024%2F6ccf0d84-5171-4899-ba8a-f83999a67a8e.png</url>
      <title>DEV Community: Datamarcos</title>
      <link>https://dev.to/datamarcos</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/datamarcos"/>
    <language>en</language>
    <item>
      <title>n8n vs LangGraph: Which Should You Use for AI Agents?</title>
      <dc:creator>Datamarcos</dc:creator>
      <pubDate>Sat, 21 Nov 2026 09:30:57 +0000</pubDate>
      <link>https://dev.to/datamarcos/n8n-vs-langgraph-which-should-you-use-for-ai-agents-2la1</link>
      <guid>https://dev.to/datamarcos/n8n-vs-langgraph-which-should-you-use-for-ai-agents-2la1</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.datamarcos.com/guides/n8n-vs-langgraph" rel="noopener noreferrer"&gt;Datamarcos Guides&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  n8n vs LangGraph: Which Should You Use for AI Agents?
&lt;/h1&gt;

&lt;p&gt;By &lt;strong&gt;Deepesh Mishra, Founder &amp;amp; CEO, Datamarcos&lt;/strong&gt; · Last reviewed 10 November 2026&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; Use &lt;strong&gt;n8n&lt;/strong&gt; when the hard part of your project is &lt;strong&gt;connecting systems&lt;/strong&gt;: triggers, SaaS apps, databases, retries and a visual run history that non-developers can follow. Use &lt;strong&gt;LangGraph&lt;/strong&gt; when the hard part is the &lt;strong&gt;agent's reasoning&lt;/strong&gt;: stateful loops, branching on model output, multi-agent hand-offs, long-running tasks and human approval mid-run, all in Python or TypeScript code. They are not really rivals. A common production pattern is n8n as the plumbing (trigger, data prep, delivery) calling a LangGraph agent over HTTP for the "think hard" step.&lt;/p&gt;

&lt;p&gt;New to the vocabulary? Start with &lt;a href="https://www.datamarcos.com/guides/what-is-agentic-ai" rel="noopener noreferrer"&gt;What is agentic AI?&lt;/a&gt;. Comparing code frameworks only? See &lt;a href="https://www.datamarcos.com/guides/langgraph-vs-crewai-vs-autogen" rel="noopener noreferrer"&gt;LangGraph vs CrewAI vs AutoGen&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each tool is
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;n8n&lt;/strong&gt; describes itself as a fair-code platform to build and deploy AI agents and workflows, combining a visual canvas with custom code, run self-hosted or in n8n's cloud (&lt;a href="https://github.com/n8n-io/n8n" rel="noopener noreferrer"&gt;n8n on GitHub&lt;/a&gt;). You build &lt;strong&gt;workflows&lt;/strong&gt; from &lt;strong&gt;nodes&lt;/strong&gt;: a trigger (webhook, schedule, app event), app nodes, code nodes (JavaScript or Python) and AI nodes such as the AI Agent with a model, memory and tools attached. Its docs cover connecting providers such as OpenAI, Anthropic and Google, adding tools and memory, and connecting agents to MCP servers (&lt;a href="https://docs.n8n.io/build/integrate-ai" rel="noopener noreferrer"&gt;n8n docs: Integrate AI&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;LangGraph&lt;/strong&gt; is "a low-level orchestration framework and runtime for long-running, stateful agents" (&lt;a href="https://docs.langchain.com/oss/python/langgraph/overview" rel="noopener noreferrer"&gt;LangGraph overview&lt;/a&gt;). You define your agent as a &lt;strong&gt;graph&lt;/strong&gt; in code: nodes are functions that read and update a shared &lt;strong&gt;state&lt;/strong&gt;, and edges (often conditional) decide what runs next. It focuses on durable execution, streaming, human-in-the-loop and memory, and does not prescribe prompts or agent architecture.&lt;/p&gt;

&lt;h2&gt;
  
  
  Side-by-side comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;n8n&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;LangGraph&lt;/strong&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Building style&lt;/td&gt;
&lt;td&gt;Visual canvas, with code nodes when needed&lt;/td&gt;
&lt;td&gt;Code-first (Python or TypeScript)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Core unit&lt;/td&gt;
&lt;td&gt;Workflow of nodes, started by a trigger&lt;/td&gt;
&lt;td&gt;Graph of nodes and edges over shared state&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Integrations&lt;/td&gt;
&lt;td&gt;Large built-in catalogue (the n8n README says 1,500+ integrations) plus HTTP and custom nodes&lt;/td&gt;
&lt;td&gt;You write tools as functions or use LangChain integrations&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Loops and branching&lt;/td&gt;
&lt;td&gt;IF/Switch nodes and sub-workflows; fine for simple agent logic&lt;/td&gt;
&lt;td&gt;Cycles and conditional edges are the core feature&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;State and long-running work&lt;/td&gt;
&lt;td&gt;Per-execution data; agent memory nodes&lt;/td&gt;
&lt;td&gt;Checkpointed state, durable execution, resume after failure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Human approval mid-run&lt;/td&gt;
&lt;td&gt;Possible with wait/approval steps&lt;/td&gt;
&lt;td&gt;Built-in interrupts to inspect and edit state&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Run history and debugging&lt;/td&gt;
&lt;td&gt;Built-in visual execution history per node&lt;/td&gt;
&lt;td&gt;Through tracing tools such as LangSmith or OpenTelemetry&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who maintains it&lt;/td&gt;
&lt;td&gt;Developers and ops or automation teams&lt;/td&gt;
&lt;td&gt;Developers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Licence&lt;/td&gt;
&lt;td&gt;Source-available ("fair-code", Sustainable Use License, plus an Enterprise License)&lt;/td&gt;
&lt;td&gt;MIT-licensed open-source library; paid hosted platform optional&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;A fair note on sources: n8n publishes its own &lt;a href="https://n8n.io/vs/langgraph/" rel="noopener noreferrer"&gt;n8n vs LangGraph&lt;/a&gt; comparison. It is useful for facts about n8n's features, but it is written by one of the two vendors, so we've used it only for n8n's side and checked LangGraph's claims against LangGraph's own docs.&lt;/p&gt;

&lt;h2&gt;
  
  
  When to choose n8n
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Your agent's value is mostly &lt;strong&gt;integration&lt;/strong&gt;: read a form, look up a CRM, call a model, update a sheet, post to a chat tool.&lt;/li&gt;
&lt;li&gt;You need &lt;strong&gt;triggers&lt;/strong&gt; out of the box: webhooks, schedules, app events.&lt;/li&gt;
&lt;li&gt;Non-developers must be able to &lt;strong&gt;see and fix&lt;/strong&gt; a failed run.&lt;/li&gt;
&lt;li&gt;You want to &lt;strong&gt;prototype in hours&lt;/strong&gt;, then decide what deserves real code.&lt;/li&gt;
&lt;li&gt;You want to self-host for data control and your use is internal. Check the Sustainable Use License terms if you plan to resell n8n-based services.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When to choose LangGraph
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The agent must &lt;strong&gt;loop&lt;/strong&gt;: plan, call tools, check its own output and retry.&lt;/li&gt;
&lt;li&gt;You need &lt;strong&gt;multi-agent&lt;/strong&gt; designs with explicit hand-offs.&lt;/li&gt;
&lt;li&gt;Runs are &lt;strong&gt;long&lt;/strong&gt; or must &lt;strong&gt;survive failures&lt;/strong&gt; and resume where they stopped.&lt;/li&gt;
&lt;li&gt;A human must &lt;strong&gt;approve or edit&lt;/strong&gt; the agent's state partway through.&lt;/li&gt;
&lt;li&gt;Your team wants agent logic in the &lt;strong&gt;codebase&lt;/strong&gt;, with unit tests, code review and CI like any other service.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Using both together
&lt;/h2&gt;

&lt;p&gt;You don't have to pick one. A widely used split:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;n8n&lt;/strong&gt; receives the event (webhook, schedule, new ticket), cleans and enriches the data.&lt;/li&gt;
&lt;li&gt;n8n calls a &lt;strong&gt;LangGraph agent&lt;/strong&gt; exposed as an HTTP endpoint and waits for a structured response.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;LangGraph&lt;/strong&gt; does the multi-step reasoning, with state, limits and human approval where needed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;n8n&lt;/strong&gt; routes the result to email, CRM, Slack or a database, and handles retries and alerts.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The seam is a clean HTTP API, so you can replace either side later. A sign it's time to move logic out of n8n: you are rebuilding state management with chains of IF and loop nodes, or your agent needs memory that persists between runs. A sign you over-engineered: a LangGraph service that only calls one model and writes one row.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Where MCP fits:&lt;/strong&gt; both sides can use the Model Context Protocol. n8n documents connecting agents to MCP servers, and a LangGraph agent can call tools exposed by MCP servers. If you build one MCP server for your company's data, both can use it. See our &lt;a href="https://www.datamarcos.com/guides/how-to-build-an-mcp-server" rel="noopener noreferrer"&gt;MCP server guide&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which should you learn first?
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Your background&lt;/th&gt;
&lt;th&gt;Start with&lt;/th&gt;
&lt;th&gt;Then&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;No coding yet, ops or business role&lt;/td&gt;
&lt;td&gt;n8n, to learn triggers, tools and the agent loop visually&lt;/td&gt;
&lt;td&gt;Basic Python, then rebuild one workflow step in code&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Developer (Python or TypeScript)&lt;/td&gt;
&lt;td&gt;Write one tool-calling loop by hand, then LangGraph&lt;/td&gt;
&lt;td&gt;n8n for integrations and quick internal tools&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data engineer&lt;/td&gt;
&lt;td&gt;LangGraph for agent logic&lt;/td&gt;
&lt;td&gt;n8n or your existing orchestrator for triggers and delivery&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Freelancer or agency building automations&lt;/td&gt;
&lt;td&gt;n8n for client delivery speed&lt;/td&gt;
&lt;td&gt;LangGraph for the cases n8n struggles with&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Whatever you start with, prove it with a project: see &lt;a href="https://www.datamarcos.com/guides/agentic-ai-projects-for-beginners" rel="noopener noreferrer"&gt;10 agentic AI projects for beginners&lt;/a&gt;. Projects 1 and 2 suit n8n; 8 to 10 suit LangGraph.&lt;/p&gt;

&lt;h2&gt;
  
  
  Common mistakes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Choosing a tool from a comparison table instead of from your bottleneck (integration vs reasoning)&lt;/li&gt;
&lt;li&gt;Building complex agent loops in a visual canvas until nobody can debug them&lt;/li&gt;
&lt;li&gt;Writing a code framework service for a simple "trigger, call model, save result" flow&lt;/li&gt;
&lt;li&gt;No step limits or budgets on agent loops in either tool&lt;/li&gt;
&lt;li&gt;Giving the agent write access to production systems during development&lt;/li&gt;
&lt;li&gt;Skipping evaluation: test both tools' outputs on a fixed set of real examples&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;The full guide, with an FAQ, is on &lt;a href="https://www.datamarcos.com/guides/n8n-vs-langgraph" rel="noopener noreferrer"&gt;Datamarcos Guides&lt;/a&gt;. More free guides on agentic AI and data engineering are on the &lt;a href="https://www.datamarcos.com/guides" rel="noopener noreferrer"&gt;Datamarcos guides hub&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources (fetched 10 Nov 2026, all HTTP 200)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;n8n GitHub README and license section: &lt;a href="https://github.com/n8n-io/n8n" rel="noopener noreferrer"&gt;https://github.com/n8n-io/n8n&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;n8n Docs, Integrate AI (incl. MCP servers): &lt;a href="https://docs.n8n.io/build/integrate-ai" rel="noopener noreferrer"&gt;https://docs.n8n.io/build/integrate-ai&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;n8n, "n8n vs LangGraph" (vendor comparison; used for n8n-side facts only): &lt;a href="https://n8n.io/vs/langgraph/" rel="noopener noreferrer"&gt;https://n8n.io/vs/langgraph/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;LangGraph overview: &lt;a href="https://docs.langchain.com/oss/python/langgraph/overview" rel="noopener noreferrer"&gt;https://docs.langchain.com/oss/python/langgraph/overview&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;LangGraph GitHub README and MIT LICENSE: &lt;a href="https://github.com/langchain-ai/langgraph" rel="noopener noreferrer"&gt;https://github.com/langchain-ai/langgraph&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>langgraph</category>
      <category>n8n</category>
      <category>agents</category>
    </item>
    <item>
      <title>RAG vs Fine-Tuning: When to Use Each (2026 Engineer's Guide)</title>
      <dc:creator>Datamarcos</dc:creator>
      <pubDate>Sat, 21 Nov 2026 09:25:19 +0000</pubDate>
      <link>https://dev.to/datamarcos/rag-vs-fine-tuning-when-to-use-each-2026-engineers-guide-ppb</link>
      <guid>https://dev.to/datamarcos/rag-vs-fine-tuning-when-to-use-each-2026-engineers-guide-ppb</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.datamarcos.com/guides/rag-vs-fine-tuning" rel="noopener noreferrer"&gt;Datamarcos Guides&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  RAG vs Fine-Tuning: When to Use Each
&lt;/h1&gt;

&lt;p&gt;By &lt;strong&gt;Deepesh Mishra, Founder &amp;amp; CEO, Datamarcos&lt;/strong&gt; · Last reviewed 29 October 2026&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; use &lt;strong&gt;RAG (retrieval-augmented generation)&lt;/strong&gt; when the model needs &lt;strong&gt;knowledge&lt;/strong&gt; it doesn't have, such as your policies, tickets or product data, especially when that knowledge changes or answers need citations. Use &lt;strong&gt;fine-tuning&lt;/strong&gt; when the model needs a &lt;strong&gt;behaviour&lt;/strong&gt; it doesn't do reliably, such as a fixed output format, a domain style or a narrow classification task. Many production systems combine good prompting, RAG for knowledge and, occasionally, a small fine-tune for behaviour.&lt;/p&gt;

&lt;p&gt;RAG was introduced in a 2020 research paper by Lewis and colleagues, which paired a language model with a retriever over a document index (&lt;a href="https://arxiv.org/abs/2005.11401" rel="noopener noreferrer"&gt;Lewis et al., 2020&lt;/a&gt;). Today it's the default pattern for company chatbots and copilots.&lt;/p&gt;

&lt;h2&gt;
  
  
  What each approach changes
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Prompt engineering&lt;/th&gt;
&lt;th&gt;RAG&lt;/th&gt;
&lt;th&gt;Fine-tuning&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Changes&lt;/td&gt;
&lt;td&gt;The instructions&lt;/td&gt;
&lt;td&gt;The context the model sees at answer time&lt;/td&gt;
&lt;td&gt;The model's weights&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Good for&lt;/td&gt;
&lt;td&gt;Format, tone, simple rules&lt;/td&gt;
&lt;td&gt;Private, fresh, citable knowledge&lt;/td&gt;
&lt;td&gt;Consistent behaviour, style, narrow tasks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Keeping it current&lt;/td&gt;
&lt;td&gt;Edit the prompt&lt;/td&gt;
&lt;td&gt;Re-index the documents&lt;/td&gt;
&lt;td&gt;Retrain&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Explainability&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;td&gt;High: you can show the sources&lt;/td&gt;
&lt;td&gt;Low&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Main risk&lt;/td&gt;
&lt;td&gt;Brittle prompts&lt;/td&gt;
&lt;td&gt;Bad retrieval leads to bad answers&lt;/td&gt;
&lt;td&gt;Cost, overfitting, stale knowledge&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Access control&lt;/td&gt;
&lt;td&gt;Not applicable&lt;/td&gt;
&lt;td&gt;Can filter results by user permissions&lt;/td&gt;
&lt;td&gt;Hard: knowledge is baked in&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Start with evaluation, then prompting
&lt;/h2&gt;

&lt;p&gt;Before choosing, build a small test set and measure. OpenAI's own &lt;a href="https://developers.openai.com/api/docs/guides/model-optimization" rel="noopener noreferrer"&gt;model optimization guide&lt;/a&gt; describes the loop as evals first, then prompt engineering, then fine-tuning if needed, and notes that prompting alone may be enough for many use cases.&lt;/p&gt;

&lt;p&gt;One practical note for 2026: as of 29 October 2026, that guide says OpenAI is winding down its fine-tuning platform and it's no longer open to new users. Fine-tuning is still possible with open-weight models and other providers, but check that the platform you plan to use still supports it.&lt;/p&gt;

&lt;h2&gt;
  
  
  When RAG is the right choice
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The answer depends on &lt;strong&gt;documents that change&lt;/strong&gt;, such as policies, catalogues or runbooks.&lt;/li&gt;
&lt;li&gt;Users need &lt;strong&gt;citations&lt;/strong&gt; or an audit trail.&lt;/li&gt;
&lt;li&gt;Different users may see &lt;strong&gt;different data&lt;/strong&gt; (role-based access).&lt;/li&gt;
&lt;li&gt;You want to start &lt;strong&gt;without training infrastructure&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When fine-tuning is the right choice
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;You need the same &lt;strong&gt;structure or style&lt;/strong&gt; every time, and prompting isn't reliable enough.&lt;/li&gt;
&lt;li&gt;The task is &lt;strong&gt;narrow and high-volume&lt;/strong&gt;, such as classification or extraction, where a smaller tuned model can be cheaper and faster.&lt;/li&gt;
&lt;li&gt;You have &lt;strong&gt;good labelled examples&lt;/strong&gt; and an evaluation set to prove the tuned model is better.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where RAG projects usually fail, and the fixes
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Chunking that breaks meaning.&lt;/strong&gt; Chunk on document structure (headings, sections) and add metadata.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keyword-blind retrieval.&lt;/strong&gt; Use &lt;strong&gt;hybrid search&lt;/strong&gt; (vector plus keyword) and a &lt;strong&gt;reranker&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Questions that need several hops.&lt;/strong&gt; Use query rewriting, multi-step retrieval or a &lt;strong&gt;knowledge graph&lt;/strong&gt; (GraphRAG).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tables and scanned PDFs.&lt;/strong&gt; Use layout-aware parsing. For numbers that live in databases, use text-to-SQL with guardrails.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No measurement.&lt;/strong&gt; Evaluate retrieval and answers (faithfulness, relevance) on a fixed test set with a tool such as &lt;a href="https://docs.ragas.io/" rel="noopener noreferrer"&gt;RAGAS&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security.&lt;/strong&gt; Retrieved text can carry hidden instructions, so add permission-aware retrieval, PII masking and prompt-injection defences. Prompt injection is the first item in the &lt;a href="https://genai.owasp.org/llm-top-10/" rel="noopener noreferrer"&gt;OWASP Top 10 for LLM Applications&lt;/a&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Much of this is data engineering: clean ingestion, metadata and freshness. If that side interests you, see the &lt;a href="https://www.datamarcos.com/programs/advance-data-engineering-genai" rel="noopener noreferrer"&gt;Advance Data Engineering with Applied GenAI &amp;amp; Agentic AI program&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  A decision checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Is the problem &lt;strong&gt;missing knowledge&lt;/strong&gt;? Use RAG.&lt;/li&gt;
&lt;li&gt;Is the problem &lt;strong&gt;inconsistent behaviour&lt;/strong&gt;? Improve the prompt first, then consider fine-tuning.&lt;/li&gt;
&lt;li&gt;Does the knowledge change often? Use RAG.&lt;/li&gt;
&lt;li&gt;Do users need to see sources? Use RAG.&lt;/li&gt;
&lt;li&gt;Do you have high-quality labelled examples, an evaluation set and a platform that supports tuning? Fine-tuning is an option.&lt;/li&gt;
&lt;li&gt;Still unsure? Build RAG first. It's cheaper to change and easier to debug.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Learn to build production RAG
&lt;/h2&gt;

&lt;p&gt;In the &lt;a href="https://www.datamarcos.com/programs/genai-agentic-ai-engineer" rel="noopener noreferrer"&gt;Generative AI &amp;amp; Agentic AI Engineer program&lt;/a&gt;, weeks 4–7 cover RAG systems:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;embeddings, vector databases and core RAG&lt;/li&gt;
&lt;li&gt;advanced RAG and evaluation&lt;/li&gt;
&lt;li&gt;knowledge graphs and GraphRAG&lt;/li&gt;
&lt;li&gt;multimodal AI and document intelligence&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Learners then build a Knowledge Copilot: a secure copilot with hybrid RAG, text-to-SQL and role-based access. Fine-tuning, small models and cost engineering come later, in week 15. It's a live 18-week program, and there's no placement guarantee.&lt;/p&gt;

&lt;p&gt;Prefer a shorter course? The &lt;a href="https://www.datamarcos.com/programs/applied-agentic-ai-certification" rel="noopener noreferrer"&gt;8-week Applied Agentic AI Certification&lt;/a&gt; covers production RAG in week 3. To compare options from other providers, see our &lt;a href="https://www.datamarcos.com/guides/generative-ai-courses-india-compared-2026" rel="noopener noreferrer"&gt;generative AI courses comparison&lt;/a&gt; or browse all &lt;a href="https://www.datamarcos.com/guides" rel="noopener noreferrer"&gt;guides&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Is RAG better than fine-tuning?&lt;/strong&gt;&lt;br&gt;
They solve different problems. RAG adds knowledge, and fine-tuning shapes behaviour. Most knowledge-heavy business apps start with RAG.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Can I use RAG and fine-tuning together?&lt;/strong&gt;&lt;br&gt;
Yes. For example, a fine-tuned model can follow a strict output format while RAG supplies the facts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Does RAG stop hallucinations?&lt;/strong&gt;&lt;br&gt;
It reduces them when retrieval is good and the prompt tells the model to answer only from the sources. It doesn't eliminate them, so evaluate answers and show citations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is GraphRAG?&lt;/strong&gt;&lt;br&gt;
GraphRAG uses a knowledge graph of entities and relationships alongside, or instead of, plain vector search. This helps with questions that connect several facts.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Do I need a vector database for RAG?&lt;/strong&gt;&lt;br&gt;
You need some kind of index. That can be a dedicated vector database, a vector extension in your existing database, or a platform's built-in search.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Is RAG or fine-tuning more useful to learn for AI jobs in India?&lt;/strong&gt;&lt;br&gt;
Both appear in GenAI engineering work. In our view RAG is the better first skill, because most company GenAI projects start with answering questions from company data. Learn RAG and evaluation well first, then learn when fine-tuning is worth it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Sources (accessed 29 October 2026)
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Lewis et al., "Retrieval-Augmented Generation for Knowledge-Intensive NLP Tasks" (2020): &lt;a href="https://arxiv.org/abs/2005.11401" rel="noopener noreferrer"&gt;https://arxiv.org/abs/2005.11401&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;OpenAI, Model optimization guide: &lt;a href="https://developers.openai.com/api/docs/guides/model-optimization" rel="noopener noreferrer"&gt;https://developers.openai.com/api/docs/guides/model-optimization&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;RAGAS documentation: &lt;a href="https://docs.ragas.io/" rel="noopener noreferrer"&gt;https://docs.ragas.io/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;OWASP Top 10 for LLM Applications: &lt;a href="https://genai.owasp.org/llm-top-10/" rel="noopener noreferrer"&gt;https://genai.owasp.org/llm-top-10/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Datamarcos, Generative AI &amp;amp; Agentic AI Engineer: &lt;a href="https://www.datamarcos.com/programs/genai-agentic-ai-engineer" rel="noopener noreferrer"&gt;https://www.datamarcos.com/programs/genai-agentic-ai-engineer&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>rag</category>
      <category>machinelearning</category>
    </item>
    <item>
      <title>What Is a Forward Deployed Engineer? A Practical Guide for Engineers in India</title>
      <dc:creator>Datamarcos</dc:creator>
      <pubDate>Sat, 21 Nov 2026 09:25:04 +0000</pubDate>
      <link>https://dev.to/datamarcos/what-is-a-forward-deployed-engineer-a-practical-guide-for-engineers-in-india-44dp</link>
      <guid>https://dev.to/datamarcos/what-is-a-forward-deployed-engineer-a-practical-guide-for-engineers-in-india-44dp</guid>
      <description>&lt;p&gt;&lt;em&gt;Originally published on &lt;a href="https://www.datamarcos.com/guides/what-is-a-forward-deployed-engineer" rel="noopener noreferrer"&gt;Datamarcos Guides&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  What Is a Forward Deployed Engineer? A Practical Guide for Engineers in India
&lt;/h1&gt;

&lt;p&gt;By &lt;strong&gt;Deepesh Mishra, Founder &amp;amp; CEO, Datamarcos&lt;/strong&gt; · Last reviewed 30 October 2026&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Short answer:&lt;/strong&gt; A forward deployed engineer (FDE) is a software engineer who works inside a customer's environment to turn a product, often an AI model or platform, into a working solution for that customer. The FDE talks to stakeholders, scopes the real problem, writes production code against the customer's data and systems, gets it through security review, and stays until people actually use it. It is part engineering and part consulting, and the FDE owns the outcome rather than just a ticket. Salesforce calls it one of today's hottest roles (&lt;a href="https://www.salesforce.com/ap/blog/forward-deployed-engineer/" rel="noopener noreferrer"&gt;Salesforce&lt;/a&gt;). (If you want to learn the role hands-on, see our &lt;a href="https://www.datamarcos.com/programs/forward-deployed-ai-engineer" rel="noopener noreferrer"&gt;Forward Deployed Engineer course&lt;/a&gt;.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the role exists
&lt;/h2&gt;

&lt;p&gt;Most enterprise software, and nearly all enterprise AI, fails in the last mile rather than in the demo. The model works in a notebook. Then it meets:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;documents in scanned PDFs, shared drives and ten-year-old SharePoint sites&lt;/li&gt;
&lt;li&gt;a legacy SQL or ERP system with no clean API&lt;/li&gt;
&lt;li&gt;a locked-down network, SSO and role-based access rules&lt;/li&gt;
&lt;li&gt;a security and compliance team that has to approve every data flow&lt;/li&gt;
&lt;li&gt;users who will drop the tool if it is wrong twice&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Product teams can't sit inside every customer, and pre-sales architects usually don't write and maintain production code. The FDE fills that gap. Palantir pioneered the role; until 2016 it had more FDEs than software engineers, according to &lt;a href="https://newsletter.pragmaticengineer.com/p/forward-deployed-engineers" rel="noopener noreferrer"&gt;The Pragmatic Engineer&lt;/a&gt;. AI companies and enterprise software vendors have since built FDE teams for the same reason: a model on its own doesn't change a business process.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a forward deployed engineer actually does
&lt;/h2&gt;

&lt;p&gt;A typical engagement runs through five stages. The names vary by company, but the work is recognisable:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Discover.&lt;/strong&gt; Sit with operations, IT and business owners. Find out what is actually painful, what data exists, and what "success" would mean in numbers the customer cares about.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scope.&lt;/strong&gt; Turn a vague request ("we want a GenAI copilot") into a concrete architecture, a statement of work, acceptance criteria and a list of risks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build.&lt;/strong&gt; Write the integration and application code: retrieval over the customer's documents, agents that call the customer's tools, connectors to their databases and ticketing systems.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Secure and deploy.&lt;/strong&gt; Get through security review: authentication, access control, PII handling, logging, evaluation, CI/CD and monitoring in the customer's cloud or VPC.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Own and hand over.&lt;/strong&gt; Drive adoption, measure whether it works, fix what users hit, document it, and train the customer's team to run it.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  A realistic day
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Time&lt;/th&gt;
&lt;th&gt;Work&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Morning&lt;/td&gt;
&lt;td&gt;Discovery call with an operations lead to understand why claims take three days to approve&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Midday&lt;/td&gt;
&lt;td&gt;Wire a hybrid search (keyword + vector) RAG pipeline to the policy documents&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Afternoon&lt;/td&gt;
&lt;td&gt;Debug an IAM permission that blocks the service from reading a storage bucket in the client VPC&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Evening&lt;/td&gt;
&lt;td&gt;Demo progress to the sponsor and update the value case&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;(Illustrative example, not a description of a specific employer.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Forward deployed engineer vs related roles
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Dimension&lt;/th&gt;
&lt;th&gt;Software engineer (product)&lt;/th&gt;
&lt;th&gt;AI / ML engineer&lt;/th&gt;
&lt;th&gt;Solutions architect&lt;/th&gt;
&lt;th&gt;Forward deployed engineer&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Main focus&lt;/td&gt;
&lt;td&gt;Features for many users&lt;/td&gt;
&lt;td&gt;Models, pipelines, model quality&lt;/td&gt;
&lt;td&gt;Designing a solution, often pre-sale&lt;/td&gt;
&lt;td&gt;One customer's problem, solved in production&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Customer contact&lt;/td&gt;
&lt;td&gt;Indirect&lt;/td&gt;
&lt;td&gt;Low&lt;/td&gt;
&lt;td&gt;High, mostly before the sale&lt;/td&gt;
&lt;td&gt;Embedded with the customer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Writes production code&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Yes, mostly model/ML code&lt;/td&gt;
&lt;td&gt;Rarely&lt;/td&gt;
&lt;td&gt;Yes, in the customer's environment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Owns the business result&lt;/td&gt;
&lt;td&gt;Shared with the product team&lt;/td&gt;
&lt;td&gt;Owns model quality&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Typical uncertainty&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;td&gt;Medium–high (research)&lt;/td&gt;
&lt;td&gt;Medium&lt;/td&gt;
&lt;td&gt;High: messy data, changing scope&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Three common confusions:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;FDE vs consultant.&lt;/strong&gt; A consultant can advise without shipping. An FDE is judged on running software.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FDE vs solutions engineer.&lt;/strong&gt; A solutions (sales) engineer mainly supports the sale with demos and proofs of concept. An FDE builds, deploys and supports the real system after the sale, and is judged on whether it works in production.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FDE vs DevOps/SRE.&lt;/strong&gt; FDEs do a lot of deployment work, but for one customer's solution, not as owners of a shared platform.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Skills a forward deployed engineer needs
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Engineering foundation&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Strong Python (or another backend language), APIs, testing, Git&lt;/li&gt;
&lt;li&gt;SQL and data modelling. Most FDE work starts with someone else's data&lt;/li&gt;
&lt;li&gt;Cloud basics on at least one of AWS, Azure or GCP: networking, identity (IAM), storage, containers&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Applied AI&lt;/strong&gt; (for AI-focused FDE roles)&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Retrieval-augmented generation: chunking, embeddings, hybrid search, re-ranking, citations&lt;/li&gt;
&lt;li&gt;Agents and tool use: function calling, orchestration frameworks such as LangGraph, and the Model Context Protocol (MCP) for connecting tools&lt;/li&gt;
&lt;li&gt;Evaluation: test sets, offline and online evals, tracing, regression checks&lt;/li&gt;
&lt;li&gt;Security and governance: prompt injection, data leakage, PII, access control, audit logs&lt;/li&gt;
&lt;li&gt;LLMOps: cost and latency budgets, monitoring, versioning prompts and models&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Customer-facing craft&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Running a discovery conversation and writing a one-page problem statement&lt;/li&gt;
&lt;li&gt;Scoping and saying no: acceptance criteria, change requests&lt;/li&gt;
&lt;li&gt;Explaining trade-offs to non-engineers, and demoing to executives&lt;/li&gt;
&lt;li&gt;Writing documentation and handover material someone else can follow&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Is the forward deployed engineer role relevant in India?
&lt;/h2&gt;

&lt;p&gt;Yes, and for structural reasons rather than hype. Indian engineers already do a large share of global enterprise implementation work through IT services firms, global capability centres (GCCs) and product companies with India engineering teams. Those organisations face the same last-mile problem with AI. Searches for FDE jobs, salaries and courses in India have grown sharply over the past year (Google Trends and autocomplete show this as a relative rise, not a volume). Titles vary: you will also see &lt;em&gt;AI solutions engineer&lt;/em&gt;, &lt;em&gt;applied AI engineer&lt;/em&gt;, &lt;em&gt;customer engineer&lt;/em&gt; or &lt;em&gt;deployment engineer&lt;/em&gt; for overlapping work.&lt;/p&gt;

&lt;p&gt;What this does &lt;strong&gt;not&lt;/strong&gt; mean: there is no guaranteed salary or fast track. FDE roles usually expect real engineering experience, because the customer is trusting you with production systems.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is a good fit
&lt;/h2&gt;

&lt;p&gt;You will probably enjoy FDE work if you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;have 2+ years as a backend, data, full-stack, QA-automation or cloud engineer and like seeing your code used&lt;/li&gt;
&lt;li&gt;are comfortable not knowing the answer on day one&lt;/li&gt;
&lt;li&gt;can explain technical decisions in plain language&lt;/li&gt;
&lt;li&gt;like variety (a different domain every engagement) more than deep specialisation in one codebase&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;It may not suit you if you want long uninterrupted coding time, or if you dislike travel or customer meetings.&lt;/p&gt;

&lt;h2&gt;
  
  
  A practical FDE roadmap
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Stage&lt;/th&gt;
&lt;th&gt;Focus&lt;/th&gt;
&lt;th&gt;Proof you can show&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1. Foundation (if needed)&lt;/td&gt;
&lt;td&gt;Python, SQL, APIs, Git, one cloud&lt;/td&gt;
&lt;td&gt;A small API deployed on the cloud with auth and tests&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2. Applied AI&lt;/td&gt;
&lt;td&gt;RAG, agents, evaluation&lt;/td&gt;
&lt;td&gt;A RAG app over messy real documents, with an eval set and a short write-up of failure cases&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3. Integration and security&lt;/td&gt;
&lt;td&gt;Connectors, SSO/RBAC, PII handling, MCP tools&lt;/td&gt;
&lt;td&gt;An agent that uses two real tools behind access control, with logs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4. Production&lt;/td&gt;
&lt;td&gt;CI/CD, observability, cost and latency&lt;/td&gt;
&lt;td&gt;A deployed system with dashboards and a runbook&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5. Customer craft&lt;/td&gt;
&lt;td&gt;Discovery, scoping, demos&lt;/td&gt;
&lt;td&gt;A one-page brief, an SOW-style scope and a recorded 5-minute demo for a non-technical audience&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Our &lt;a href="https://www.datamarcos.com/programs/forward-deployed-ai-engineer#curriculum" rel="noopener noreferrer"&gt;Forward Deployed AI Engineer program&lt;/a&gt; follows the same five stages across 22 weeks, with a client-style engagement in each phase.&lt;/p&gt;

&lt;p&gt;Portfolios that work for FDE interviews show &lt;strong&gt;decisions and trade-offs&lt;/strong&gt;, not just code. Include what broke, how you measured it, and what you would do differently.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to prepare for FDE interviews
&lt;/h2&gt;

&lt;p&gt;Expect a mix of:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;coding&lt;/strong&gt; (practical rather than puzzle-heavy at many companies)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;system design in a customer context&lt;/strong&gt; ("design a document assistant for a bank with strict data residency")&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;a decomposition or case exercise&lt;/strong&gt;: take a vague business problem and scope it live&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;behavioural questions&lt;/strong&gt; about ambiguity, pushback and ownership&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Practise explaining a project end to end: the problem, constraints, architecture, evaluation, security and what changed for users. For practice material, see our &lt;a href="https://www.datamarcos.com/resources/interview-prep" rel="noopener noreferrer"&gt;interview prep resources&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Read the rest on Datamarcos
&lt;/h2&gt;

&lt;p&gt;The full guide, including the FAQ and the full source list, is on &lt;a href="https://www.datamarcos.com/guides/what-is-a-forward-deployed-engineer" rel="noopener noreferrer"&gt;Datamarcos Guides&lt;/a&gt;. If you are preparing for interviews, the free &lt;a href="https://www.datamarcos.com/resources/interview-prep" rel="noopener noreferrer"&gt;interview prep page&lt;/a&gt; has practice questions.&lt;/p&gt;

</description>
      <category>career</category>
      <category>ai</category>
      <category>softwareengineering</category>
      <category>india</category>
    </item>
  </channel>
</rss>
