Hub · everything on one subject · 7 articles · 2 repos & apps
Forward-Deployed Engineering (FDE)
A forward-deployed engineer is the engineer who goes to where the work actually happens. Instead of shipping a demo and leaving, they sit inside the customer's world, find the real problem, build the agent into the customer's own systems, and stay until it works there.
In engineering terms: technical discovery against messy, real requirements; integration with the customer's data, permissions and infrastructure; evaluation and observability in production; and a feedback loop that turns each field problem into a reusable tool.
Most AI value is lost in the last mile, between a model that works in a notebook and a team that uses it every day. FDE is the discipline for that mile, and it is the role I have practiced: forward-deployed delivery on an OpenAI enterprise engagement, and the open-source toolkit below.
The role (3)
What a forward-deployed engineer does, and why the job is older than AI.
- AI's Last Mile Is a Person. It Always Was.
2026-07-17
Forward-deployed engineer listings are up 800% — and the job is 500 years old. The mental model: the frontier model is a magnificent ship, your business is a harbor, and ships don't sink in the open ocean — they sink in harbors, where the sandbars are local (hallucination on YOUR edge cases, latency against YOUR SLA, retrieval under YOUR compliance). Every day, captains of $200M vessels hand the wheel to a stranger who climbed a rope ladder: the harbor pilot — local knowledge embodied, trust concretized onto a person. Term by term: local charts → domain know-how as system design; a place on the bridge → a seat in engineering (not sales) with authority to change the platform; a license earned by passages (compulsory since 1604) → a portfolio of real agents, not prompt wrappers; paid on safe arrival → the outcome-based model. Three telescopes: 30 days (+800%, 57.3% agents in production), 30 years (Palantir FDEs; license → SaaS → outcome pricing; the field is the laboratory), 512 years (the 1513 mariners' petition against unregulated Thames pilots → Trinity House, 1514). Dogfooded: audited my own FDE practice repo against the talk's five theses and shipped the missing mechanism — an outcome contract as code (baseline → target → measured evidence → GO/NO-GO; claimed never passes; 21 tests, open source). The pilot's enemy is ego. Pay for the docking, not the map.
- The Fastest-Growing Job in AI Has No School — So I'm Building One That Learns From Its Own Mistakes
2026-06-26 · LinkedIn
Forward-Deployed Engineers bridge AI models and real-world operations by embedding with customers — turning local fixes into reusable product capabilities.
- The 83% Agent and the 24% Agent Are the Same Model
2026-07-17
Snowflake Summit 2026 shipped 26+ capabilities under one thesis — the agentic enterprise runs on governed context, not just compute — and one number: agents scored a reported 83% accuracy with an enterprise memory layer vs 24% without. Same model. The mental model a 12-year-old can run: a frontier model joining your company is the smartest hire in history, on day one, with no badge, no handbook, no supervisor — ask for Q3 revenue and you get four confident numbers, all real, all different. Mapped term by term to what actually shipped: badge → cryptographic agent identity + per-agent RBAC (GA); handbook → the enterprise context layer (the 24→83 lever); org chart → column-level lineage ("an answer without lineage is a rumor"); probation → evals + audit + human gates. Three telescopes: 30 days (the summit), 30 years (warehouse → knowledge graphs → feature stores: models churn, structure compounds), 500 years (Pacioli 1494 — banks ran agent-clerks under governed ledgers for centuries; trust was never a property of the person, it was a property of the ledger). Dogfooded: the article's own sources compiled into a 33-node provenance-required knowledge graph + 8 skills with honest notGoodAt edges, open in FDE-os. A model upgrade helps every company equally; a context layer helps only yours. Stop upgrading the model — start onboarding it.
Getting good at it (4)
Interviews, system design and learning a new field fast, each with the FDE-os toolkit doing part of the work.
- I Failed a Google System-Design Round. Here's the Architect's Loop I Built From It.
2026-07-11
Fifteen famous interview articles won't make you an architect — reading fifteen blueprints is like reading fifteen recipes and calling yourself a chef. One repeatable habit will: name the trade-off (CAP, out loud) before you draw the box. The architect's loop — Constrain, Estimate, Sketch, Stress, Evolve — a method you can run under pressure, plus the fifteen topics re-grouped by the decision each settles (data plane, front door, async backbone, and the two case studies where a uniform strategy breaks on the tail). Written after a Google FDE round I didn't pass, learn-by-teaching.
- Stop Studying for Interviews — Compile Them
2026-07-17
A job description is source code: parse it deterministically (word-boundary taxonomy, no rust-in-trust false positives), ground every extracted concept against Wikipedia/Wikidata/ESCO with a provenance URL (no source ⇒ flagged thin, never faked), link each requirement against your public repos like a linker resolving symbols — and let the errors write your prep plan. Opens with the first résumé in history (Leonardo, 1482: "I can dry up the moats" — moats dried at time of writing, ~0) and checks the method at three zoom levels: 30 days (agentic-AI postings +280% YoY, 34.3% name LangChain, 57.3% run agents in production), 30 years (work samples beat credentials; ATS robots have compiled YOU since the 1990s — run the compiler the other way), 300 years (the guild masterpiece: the artifact outlives the letter). Fully animated infographics; the compiler is open at github.com/wjlgatech/FDE-os. Cramming resets; compiling accrues.
- I Compiled 58 Snowflake Courses Into an Agent. It Failed Me First.
2026-08-03
Snowflake's own org ships a strong agentic toolchain — an MCP server, cocoplus (verbatim: "an Agentic Operating System for Snowflake Coco"), Cortex Code skills — and every one of them operates on the WAREHOUSE. None operates on the CURRICULUM, so no machine can answer "what should this person learn, and did they?" I compiled learn.snowflake.com into a provenance-pinned knowledge base (58 courses, 430.25h, 12 distinct exams from 19 pages, 94 records each carrying the URL and sha256 of the page it was parsed from) and built the missing layer on top: a pathfinder that orders a route using Snowflake's own published track order where it exists, and a readiness gate where claimed completions score zero — claim all 58 courses with no badge and coverage is 0.0, NO-GO, exit 2. The useful output is the four things it refuses to know: the role-to-course mapping does not exist upstream (0 of 12 role pages publish one), Specialty exam pricing is unpublished so the parser refuses to borrow the $175/$375 sitting next to it, one track publishes no sequence, and nobody's real competence is measurable from a catalogue at all. Then it failed my own work three times: the integrity gate caught an orphan competency on its first run (8/9), a duplicate-counting bug scored a well-prepared candidate 21% until alternatives collapsed it to 55%, and one line of HTML-escaping had been silently rendering eleven shipped knowledge viewers blank. Anchored on Miller's 1990 assessment pyramid and on four honest words Snowflake prints on its own exam page: "assumed but not tested." First principle: a system that cannot fail cannot certify.
- Learn Any Field 10× With AI — Wide and Deep, Without Fooling Yourself
A mental model a 12-year-old can run — Map (width) · Ladder (depth) · Gate (proof) — mapped term-by-term to the cognitive science (Gick & Holyoak, Chase & Simon, Roediger & Karpicke, Ericsson, Bjork). Defines 'better' as a verified result, not a warm feeling, and names the con artist in the lab coat: the illusion of competence.
Repos and live apps (2)
- FDE-os
An operating system for becoming, and staying, a forward-deployed engineer: a course validated against real job descriptions, a toolkit of skills for Claude, Codex and Hermes (one Claude Code plugin, an MCP server with eleven tools), and a community where field stories become field notes.
Open the live app → - FDE-os build journey
The self-updating record of how FDE-os was built, from graded, evidence-backed deliveries.