@sahil0x01 Sorry for not being clear. I just wanted to check whether the videos follow a consistent flow or if the continuity gets disrupted by classroom questions and discussions.
If you learn Forward Deployed Engineering, you will never be unemployed again.
I’d do this.
Stage 1: Enterprise Identity & Access (The Gatekeeper)
- Learn: OAuth2, SAML, OIDC, SCIM provisioning, Row-Level Security (RLS) and multi-tenant data isolation.
- Practice: Build an auth bridge connecting your AI app to a simulated customer's Okta/Azure AD, ensuring User A can only query data their specific RBAC role permits.
- Why: No SSO and strict data isolation means no enterprise contract. Security review is the first gate.
Stage 2: Air-Gapped & VPC Deployments (The Environment)
- Learn: Kubernetes (K8s), Helm, Terraform, private container registries, air-gapped networking and egress filtering.
- Practice: Script a one-click Terraform/Helm deployment of your entire AI stack into a simulated customer VPC with zero egress to the public internet.
- Why: Banks, hospitals and governments don't let your AI talk to the public cloud. You must deploy in their basement.
Stage 3: Legacy Data Extraction & ETL (The Fuel)
- Learn: OCR, unstructured PDF parsing, mainframe DB connectors, Apache Airflow, dbt and data reconciliation.
- Practice: Build a pipeline that ingests 10 years of messy, scanned customer invoices and turns them into a clean, queryable hybrid (vector + relational) store.
- Why: Enterprise AI starves without clean data. The customer's data will always be a mess.
Stage 4: Secure RAG & Permission-Filtered Retrieval (The Brain)
- Learn: Hybrid search, document-level access control, citation grounding, metadata tagging and abstention logic.
- Practice: Build a RAG pipeline where the LLM dynamically filters out retrieved chunks that the specific user asking the question doesn't have clearance to see.
- Why: An AI that leaks HR salaries or M&A docs to a junior employee is an immediate breach of contract.
Stage 5: MCP & Legacy System Integration (The Hands)
- Learn: Model Context Protocol (MCP), SOAP/REST translation, web scraping, headless browsers and API rate-limit handling.
- Practice: Build an MCP server that lets an LLM safely query and write to the customer's 15-year-old on-prem SAP or Oracle instance without exposing raw credentials.
- Why: Agents are useless if they can't touch the customer's actual systems of record.
Stage 6: AI Guardrails & PII Redaction (The Shield)
- Learn: NER (Named Entity Recognition), deterministic regex filtering, LLM output validation, UUID masking, and audit logging.
- Practice: Build a middleware proxy that intercepts LLM inputs/outputs, masks SSNs and credit cards with UUIDs before they hit the model, and restores them post-generation.
- Why: Compliance teams will kill the deal if a single PII token hits an external frontier API.
Stage 7: Human-in-the-Loop (HITL) Workflows (The Trust)
- Learn: Temporal {dot} io, webhook routing, state machines, durable execution and UI approval gates.
- Practice: Build a workflow where the AI drafts a $50k purchase order, but physically pauses execution until a human manager clicks "Approve" in Slack or Teams.
- Why: Enterprises adopt AI only when humans remain legally accountable for the final action.
Stage 8: Edge & On-Prem Inference (The Silicon)
- Learn: vLLM, TensorRT-LLM, Ollama, GPU partitioning (MIG), and local quantized models (AWQ/GGUF).
- Practice: Deploy a quantized 8B model on a single customer-owned GPU node to handle highly sensitive triage locally without network latency.
- Why: Sometimes the data is too hot to move. You must bring the model to the data.
Stage 9: Observability & Customer Health (The Pulse)
- Learn: OpenTelemetry, Langfuse, custom Grafana dashboards, usage telemetry and cost-attribution.
- Practice: Build a "Customer Health" dashboard showing the exact cost-savings, time-saved and token-spend the AI has generated for their specific team this month.
- Why: If the customer doesn't see the ROI quantified, they will churn at renewal.
Stage 10: Evals on Customer Data (The Proof)
- Learn: Golden dataset creation, trajectory grading, shadow testing, and LLM-as-a-judge calibration.
- Practice: Take 100 real past customer support tickets, run them through your agent in shadow mode, and prove to the VP of Support that it resolved 80% accurately.
- Why: Generic benchmarks mean nothing to a buyer. You must prove the AI works on *their* messy data.
Stage 11: Technical Discovery & Scoping (The Translation)
- Learn: Stakeholder interviewing, architecture diagramming, SOW (Statement of Work) writing and expectation management.
- Practice: Translate a vague "we want AI for supply chain" executive request into a scoped, 4-week technical deployment plan with defined, measurable success metrics.
- Why: FDEs are the translators between revenue (Sales) and reality (Engineering).
Stage 12: The Handoff & Self-Serve Admin (The Scale)
- Learn: Technical writing, runbooks, admin portals, automated onboarding and chaos testing.
- Practice: Write a deployment runbook and build an admin UI so the customer's internal IT team can manage the AI stack, update prompts and view logs without calling you.
- Why: Your leverage is measured by how little the customer needs you for day-to-day operations.
AI labs build the engine. FDEs build the roads.
The modern Forward Deployed Engineer builds the secure, durable nervous system that connects frontier intelligence to legacy reality.
Bookmark and Repost!
LLM Knowledge Bases
Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So:
Data ingest:
I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them.
IDE:
I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides).
Q&A:
Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale.
Output:
Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base.
Linting:
I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into.
Extra tools:
I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries.
Further explorations:
As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows.
TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
The Ch08 Nb on distilling LLMs is now on GitHub: https://t.co/bPRyIU5BhH
Hard distillation that works with any LLM (minding the terms of service, of course).
Introducing the Synthetic Data Playbook: We generated over a 1T tokens in 90 experiments with 100k+ GPUh to figure out what makes good synthetic data and how to generate it at scale
https://t.co/iaHuodWVAa
I’m 54, a physicist, have spent decades using mathematics to study the universe, solve problems, and build things.
If your work touches numbers, now or in the future, and you want to learn math properly, this thread shows a from-the-ground-up math you’ll actually need:
NVIDIA is proud to partner with @MistralAI on something huge.
Their new frontier model family is tuned end-to-end for NVIDIA NVL72 and edge platforms, delivering up to 10x faster performance on Mistral Large 3.
Together, we’re helping build a world of distributed intelligence, from cloud to edge.
https://t.co/tttI9RB1sE
@AlexFinn Hey Alex, if LLMs are your main goal, I would recommend this roadmap I posted back in June. Also, my last tweet goes through the core LLM concepts that everyone should know, I suggest you take a look at it as well.
https://t.co/NKR8gZ7EAw
I’ve been working on something new:
📚 Build a Reasoning Model (From Scratch).
The first chapters just went live!
(The book will cover topics from inference-time scaling to reinforcement learning)
A recent distress call: a student has taken about ₹70L ($80K) debt at 12% to get a master's degree in a small college in the US.
The problem: the job scene in IT is bad, especially so for foreign students and payments on the loan are starting soon.
I don't know what we could do in this situation because we have not been hiring much as we transform ourselves for the AI era. That caution in hiring is also because we have a policy of not resorting to lay-offs.
I urge students and parents to be cautious in borrowing heavily to pursue degrees abroad. Borrowing heavily to pursue degrees in India is unwise too.
I strongly believe we should not trap young people in debt in the name of education. The only smart course is for prospective employers to fund training programs and for the industry to broadly accept such alternative credentials rather than ask for formal degrees.
The best investment we make as a company is in training and skill development. I hope companies do this widely so we don't strand young people in debt.