<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vibe Engines — Forward Deployed Engineering</title>
    <link>https://vibeengines.com/topic/forward-deployed-engineering</link>
    <atom:link href="https://vibeengines.com/topic/forward-deployed-engineering/feed.xml" rel="self" type="application/rss+xml" />
    <description>The trending customer-facing engineering role: discover the problem on site, prototype fast, integrate with the customer’s systems, deploy in their environment, demo, harden, and hand off — everything for becoming a Forward Deployed Engineer.</description>
    <language>en</language>
    <lastBuildDate>Sat, 01 Aug 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Enterprise Identity for FDEs</title>
      <link>https://vibeengines.com/handbook/enterprise-identity-for-fdes</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/enterprise-identity-for-fdes</guid>
      <category>Handbook</category>
      <description>The layer that blocks more enterprise deals than model quality ever will. SAML vs OIDC and when the customer decides for you, SCIM deprovisioning (a PATCH setting active to false, not a DELETE), group-to-role mapping that survives a reorg, workload identity instead of a static key, and the five artefacts a security reviewer will ask you for.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Commercial Layer for FDEs</title>
      <link>https://vibeengines.com/handbook/commercial-layer-for-fdes</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/commercial-layer-for-fdes</guid>
      <category>Handbook</category>
      <description>The part nobody teaches: reading a SOW before you are bound by it, the six clauses that cause all the pain, four pricing models and what each does to your week, telling a customer need from a rep’s quota, the services-trap arithmetic, and the renewal that starts nine months early.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>MCP for FDEs</title>
      <link>https://vibeengines.com/handbook/mcp-for-fdes</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/mcp-for-fdes</guid>
      <category>Handbook</category>
      <description>Anthropic’s FDE job description names MCP servers as a deliverable. Designing a tool surface a model can actually use, wrapping a 2009 SOAP service and a stored procedure as tools, putting the code-to-word vocabulary in the server, and the four trust-boundary questions between customer data and a model that reads anything.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Air-Gapped &amp; Regulated Deployment</title>
      <link>https://vibeengines.com/handbook/air-gapped-and-regulated-deployment</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/air-gapped-and-regulated-deployment</guid>
      <category>Handbook</category>
      <description>Five things customers mean by “air-gapped”, FedRAMP and DoD impact levels explained for engineers, the eight-step path model weights take into a disconnected network, update cadences set by a change board rather than your CI, and why evals are the first thing that breaks when telemetry cannot leave.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>IaC for Customer Environments</title>
      <link>https://vibeengines.com/handbook/iac-for-customer-environments</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/iac-for-customer-environments</guid>
      <category>Handbook</category>
      <description>Terraform and Helm when the account, the cluster and the change process all belong to someone else: who holds state, the seven things a no-egress VPC breaks at runtime, referencing secrets you must not read, and the clean-room rebuild that is the only honest test of a handover.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Applied AI Engineer, Explained</title>
      <link>https://vibeengines.com/handbook/applied-ai-engineer</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/applied-ai-engineer</guid>
      <category>Handbook</category>
      <description>“Applied” does not mean applied research — it means the model meets a real customer’s systems and you are standing where that happens. The published 40/30/30 split, how the title differs from AI engineer and ML engineer, the five badge variants in the family, and the two questions that identify any of them.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE vs FDSE vs Deployment Strategist</title>
      <link>https://vibeengines.com/handbook/fde-vs-fdse-vs-deployment-strategist</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-vs-fdse-vs-deployment-strategist</guid>
      <category>Handbook</category>
      <description>Palantir split forward-deployed work into an engineering ladder and a strategy ladder; most companies copied the title and not the split, which is why one word now means two jobs. What each role owns, how the loops diverge, and the career mistake this comparison exists to prevent.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>AI Solutions Engineer</title>
      <link>https://vibeengines.com/handbook/ai-solutions-engineer</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/ai-solutions-engineer</guid>
      <category>Handbook</category>
      <description>The engineer on the other side of the signature. Roughly a third of FDE-family postings are pre-sales-shaped: what that means across the deal cycle, how OTE changes which customers you spend time on, why “how accurate is it?” must not be answered with a number, and the four questions to ask before accepting.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The FDE Canon</title>
      <link>https://vibeengines.com/handbook/the-fde-canon</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/the-fde-canon</guid>
      <category>Handbook</category>
      <description>Ten sources that actually explain the role — first-hand accounts, job descriptions read as documents, the commercial argument, and the market data — each with what to take from it and what it is silent about. Read in this order, and note honestly what is missing: almost nothing good exists on identity, security review, the commercial layer or evals.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Design an Enterprise Eval Pipeline</title>
      <link>https://vibeengines.com/systemdesign/enterprise-eval-pipeline-system-design</link>
      <guid isPermaLink="true">https://vibeengines.com/systemdesign/enterprise-eval-pipeline-system-design</guid>
      <category>System Design</category>
      <description>Turn “it should be accurate” into a gate that blocks a merge. Learn a stratified frozen golden set, the inter-expert agreement ceiling that sets a defensible target, an LLM judge reported with its calibration, a CI gate asserting per-case regressions rather than an average, drift monitoring that separates distribution shift from score decay, and the one business number the renewal actually turns on.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Design an Agent Harness (AI-Supervised Delivery)</title>
      <link>https://vibeengines.com/systemdesign/agent-harness-system-design</link>
      <guid isPermaLink="true">https://vibeengines.com/systemdesign/agent-harness-system-design</guid>
      <category>System Design</category>
      <description>The shift from writing feature code to writing the systems that write it. Learn task decomposition into machine-verifiable units, a narrow designed tool surface instead of shell access, per-task sandboxes that make failure cheap, a verification gate the agent cannot reach, a review queue routed by blast radius, repo-grounded context, and the ledger that makes agent work auditable.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Design Enterprise SSO &amp; Provisioning</title>
      <link>https://vibeengines.com/systemdesign/enterprise-sso-and-provisioning-system-design</link>
      <guid isPermaLink="true">https://vibeengines.com/systemdesign/enterprise-sso-and-provisioning-system-design</guid>
      <category>System Design</category>
      <description>The layer that blocks more enterprise deals than model quality. Learn multi-tenant SAML and OIDC federation, keying users on an immutable subject identifier, SCIM where deactivation arrives as a PATCH rather than a DELETE, group-to-role mapping that survives a reorg, revoking live sessions and API tokens inside the promised window, and the evidence a security reviewer asks for.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Security Review Gauntlet</title>
      <link>https://vibeengines.com/lab/security-review-gauntlet</link>
      <guid isPermaLink="true">https://vibeengines.com/lab/security-review-gauntlet</guid>
      <category>Lab</category>
      <description>The review that blocks more enterprise AI deployments than any technical problem, in three rounds. Answer a SIG/CAIQ-style questionnaire where a specific &lt;em&gt;no&lt;/em&gt; with a compensating control outscores a vague &lt;em&gt;yes&lt;/em&gt; — and a false yes ends the review. Survive a live CISO call with a trust meter that punishes bluffing exactly as the real one does. Then threat-model an LLM application, where the plausible mitigation is usually not the one that holds. Ends with a findings report: approved, approved with conditions, or blocked.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Stakeholder Politics Lab</title>
      <link>https://vibeengines.com/lab/stakeholder-politics-lab</link>
      <guid isPermaLink="true">https://vibeengines.com/lab/stakeholder-politics-lab</guid>
      <category>Lab</category>
      <description>Deployments die on org charts, not architecture. Six people at one customer, each identified by a single sentence — classify them as economic buyer, champion, end user, blocker or data gatekeeper, and expect the titles to mislead you at least twice. Then handle the three situations that actually end projects: the gatekeeper who never says no but never grants access, the team lead whose people you are automating, and the champion who resigns in month five — while a coalition meter tracks who is still with you.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Domain Ramp Sprint</title>
      <link>https://vibeengines.com/lab/domain-ramp-sprint</link>
      <guid isPermaLink="true">https://vibeengines.com/lab/domain-ramp-sprint</guid>
      <category>Lab</category>
      <description>The FDE meta-skill, drilled on three real verticals — insurance claims, hospital revenue cycle, or legal discovery. Learn the vocabulary that turns out to be codes (&lt;code&gt;status 7&lt;/code&gt;, &lt;code&gt;CO-45&lt;/code&gt;, TAR), reconstruct the workflow people actually follow rather than the one on the diagram, then pass expert gates including the one that asks which rule lives only in a practitioner's head. Scored on whether you could hold a conversation with them on Monday.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Deep Clone, Constraint by Constraint</title>
      <link>https://vibeengines.com/challenge/deep-clone-escalation</link>
      <guid isPermaLink="true">https://vibeengines.com/challenge/deep-clone-escalation</guid>
      <category>Challenge</category>
      <description>The incremental round on a problem where stage three genuinely breaks the obvious design: copy an object, then nested structures, then one containing a cycle, then one where two keys must still share the same clone. A visited set stops the crash and fails the last stage. Solve it in Python or TypeScript, with hidden tests.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Rate Limiter, Constraint by Constraint</title>
      <link>https://vibeengines.com/challenge/rate-limiter-escalation</link>
      <guid isPermaLink="true">https://vibeengines.com/challenge/rate-limiter-escalation</guid>
      <category>Challenge</category>
      <description>A third incremental round, where stage two invalidates stage one outright: a fixed-window counter becomes a sliding window, then per-key, then gains a burst allowance. Tests whether you can say “that counter has to go” calmly and refactor. Solve it in Python or TypeScript, with hidden tests.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Reconcile Two Systems That Disagree</title>
      <link>https://vibeengines.com/challenge/erp-crm-reconciliation</link>
      <guid isPermaLink="true">https://vibeengines.com/challenge/erp-crm-reconciliation</guid>
      <category>Challenge</category>
      <description>The customer is certain the ERP and the CRM agree; they have never checked. Build the reconciliation that produces a report someone can act on — normalised matching, per-field discrepancies, missing on each side, and duplicate keys reported rather than silently dropped. Solve it in Python or TypeScript, with hidden tests.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Harvest a Flaky Paginated API</title>
      <link>https://vibeengines.com/challenge/flaky-api-harvester</link>
      <guid isPermaLink="true">https://vibeengines.com/challenge/flaky-api-harvester</guid>
      <category>Challenge</category>
      <description>The vendor API is paginated, occasionally 500s, rate-limits without documenting it, and returns overlapping pages when the data moves under you. Collect everything, retry what deserves retrying, deduplicate, and return a partial result with the failures recorded rather than an exception. Solve it in Python or TypeScript, with hidden tests.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The 95% Number, Examined</title>
      <link>https://vibeengines.com/paper/mit-nanda-ai-pilots</link>
      <guid isPermaLink="true">https://vibeengines.com/paper/mit-nanda-ai-pilots</guid>
      <category>Paper</category>
      <description>The most-quoted statistic in enterprise AI, read carefully: roughly 95% of pilots reportedly produced no MEASURABLE profit-and-loss impact. Two words carry the sentence. &quot;Measurable&quot; means attributable financial effect — not accuracy, not satisfaction — and &quot;pilot&quot; means a bounded trial, which selects for projects that end before an accounting period closes. Three separate failures hide inside the one number: MEASUREMENT failure (it worked and no baseline exists, because nobody captured the before-picture in week one and it is unrecoverable afterwards), ATTRIBUTION failure (something improved and three other things changed the same quarter, so finance will not credit yours), and ACTUAL failure (the workflow was wrong or nobody adopted it). The first two are why the forward deployed role exists — both are solved by work before and after the model. Sourced, confidence-labelled (reported via press coverage, not a public methodology), and paired with the a16z argument it mirrors.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Trading Margin for Moat</title>
      <link>https://vibeengines.com/paper/a16z-trading-margin-for-moat</link>
      <guid isPermaLink="true">https://vibeengines.com/paper/a16z-trading-margin-for-moat</guid>
      <category>Paper</category>
      <description>Why a software company would deliberately hire expensive engineers to do customer work. The services-led-growth thesis: spend gross margin on deployment depth because the resulting integration is hard to displace and the outcome is provable — the margin hit is an acquisition cost for defensibility, not an inefficiency. The arithmetic that decides whether it holds, as a worked napkin example: an FDE at ~$300K loaded doing 3 deployments a year costs ~$100K per deployment, which is 67% of a $150K ACV and 17% of a $600K one — and REUSE is the only term that improves over time (0.6x, then 0.4x). The failure mode built into the thesis is paying the margin and not receiving the moat, which arrives one reasonable exception at a time. Diagnostic: does deployment N take measurably less time than N−1? Plus what the trade means for your career and the two questions to ask an employer.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>1,000 FDE Jobs, Analysed</title>
      <link>https://vibeengines.com/paper/bloomberry-1000-fde-jobs</link>
      <guid isPermaLink="true">https://vibeengines.com/paper/bloomberry-1000-fde-jobs</guid>
      <category>Paper</category>
      <description>Reading a thousand job postings beats reading a thousand opinions. One title covers at least THREE distinct jobs — builder (few customers, deep, milestone-driven), pre-sales (many customers, shallow, quarter-driven, often with quota), and internal/platform — and roughly a third of postings using the FDE title are the pre-sales shape, which the posting rarely makes explicit. A separate census counted 1,206 strict-definition postings across 669 companies at a ~$185K median posted base. What every posting asks for: strong general engineering, LLM app patterns, integration reality, deployment where you do not own the cloud, and increasingly MCP servers as deliverables — with EVALUATION the most-cited hard skill and the least taught anywhere. How to read a posting properly, the two questions that settle which species it is, and the honest caveat that posting counts measure demand signals rather than filled roles.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE Comp Explorer</title>
      <link>https://vibeengines.com/tools/fde-comp-explorer</link>
      <guid isPermaLink="true">https://vibeengines.com/tools/fde-comp-explorer</guid>
      <category>Tool</category>
      <description>Forward Deployed Engineer compensation, decomposed. Pick an employer tier (frontier lab, Palantir, AI infra, vertical startup, big tech, defence), a level and a market, and see the base/equity/bonus split rather than one headline number — plus the reported band, the confidence label on the underlying source, and the six questions that change what any offer actually means. A transparent multiplier model with its anchors and sources stated, not a scraped table.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Scoping Question Log</title>
      <link>https://vibeengines.com/tools/scoping-question-log</link>
      <guid isPermaLink="true">https://vibeengines.com/tools/scoping-question-log</guid>
      <category>Tool</category>
      <description>A drill for the skill every discovery call actually tests. Two underspecified customer asks, twelve candidate questions each, and a budget of six — spend them, see what the customer really says, and get each question scored on whether the answer changes what you build. Ends with a copyable scoping doc, a coverage map across the six axes, and the thing that was really going on that you either found or missed.</description>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What Is a Forward Deployed Engineer?</title>
      <link>https://vibeengines.com/handbook/what-is-a-forward-deployed-engineer</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/what-is-a-forward-deployed-engineer</guid>
      <category>Handbook</category>
      <description>The pillar definition, with sources: an FDE owns the full arc of a deployment inside the customer\u2019s environment. The three species of the role (builder / pre-sales-shaped / internal), why postings grew 729% in a year, who hires, what the bar really is, and whether the title survives its own hype.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE vs Every Adjacent Role</title>
      <link>https://vibeengines.com/handbook/fde-vs-other-roles</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-vs-other-roles</guid>
      <category>Handbook</category>
      <description>One master table placing the Forward Deployed Engineer against eleven adjacent roles \u2014 software engineer, AI engineer, solutions engineer, architect, consultant, PM, DevOps, data engineer, SRE, TAM, customer success \u2014 on environment, ownership and comp shape, then the four deep comparisons and a four-check test for reading any job ad.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE vs Software Engineer</title>
      <link>https://vibeengines.com/handbook/fde-vs-software-engineer</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-vs-software-engineer</guid>
      <category>Handbook</category>
      <description>Same code, different physics. The ownership asymmetry that rewrites everything, two calendars side by side, why FDE comp is higher but far wider, what transfers from product engineering and what has to be built new, and honest checklists for switching in either direction.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE vs AI Engineer</title>
      <link>https://vibeengines.com/handbook/fde-vs-ai-engineer</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-vs-ai-engineer</guid>
      <category>Handbook</category>
      <description>Identical toolbox \u2014 RAG, agents, tool schemas, evals \u2014 but the AI engineer\u2019s hard problem is the model and the FDE\u2019s is the organisation around it. Where Applied AI Engineer and Agent Engineer land, negotiated evals as the skill that separates them, and how comp, ceiling and exits differ.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE vs Solutions Engineer &amp; Architect</title>
      <link>https://vibeengines.com/handbook/fde-vs-solutions-engineer</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-vs-solutions-engineer</guid>
      <category>Handbook</category>
      <description>One question separates all three: after signature, who is accountable for what runs in production? Includes the 30-second test that reveals a relabelled pre-sales posting, one enterprise deal followed phase by phase, and the production-engineering gap to close if you are moving over from pre-sales.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE vs Consultant</title>
      <link>https://vibeengines.com/handbook/fde-vs-consultant</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-vs-consultant</guid>
      <category>Handbook</category>
      <description>Is forward deployed engineering just consulting with better branding? Three things genuinely separate them \u2014 running software, a product feedback loop, and equity \u2014 and each can quietly disappear. The services trap, four interview questions that detect it, and what FDEs should steal from consultants anyway.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Forward Deployed Engineer Salary, Explained</title>
      <link>https://vibeengines.com/handbook/forward-deployed-engineer-salary</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/forward-deployed-engineer-salary</guid>
      <category>Handbook</category>
      <description>Why the public numbers differ by seven times, reconciled: base versus total comp, six employer tiers from frontier labs to defense integrators, the level ladder and what earns each rung, six questions for reading an offer, and the equity structure that makes most of the package an estimate about the future.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to Become a Forward Deployed Engineer</title>
      <link>https://vibeengines.com/handbook/how-to-become-a-forward-deployed-engineer</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/how-to-become-a-forward-deployed-engineer</guid>
      <category>Handbook</category>
      <description>The concrete route in: the real bar (staff-level judgement, not SWE-lite), six skills in dependency order, the one portfolio artefact that beats everything else, a 12-week plan, what to do coming from support / consulting / no degree, and an honest verdict on paid FDE courses and certifications.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Is Forward Deployed Engineering Worth It?</title>
      <link>https://vibeengines.com/handbook/is-forward-deployed-engineering-worth-it</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/is-forward-deployed-engineering-worth-it</guid>
      <category>Handbook</category>
      <description>The honest version. Five named costs \u2014 coding atrophy, travel, accountability without control, the services trap, and a specific kind of burnout \u2014 each with the version of the job where it does not happen. Then the exits ranked by how naturally they follow, and eight questions that buy you out of the costs.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>A Day in the Life of an FDE</title>
      <link>https://vibeengines.com/handbook/fde-day-in-the-life</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-day-in-the-life</guid>
      <category>Handbook</category>
      <description>Hour by hour, built from the published first-hand accounts: a customer-site day, a remote build day, and a launch-week day \u2014 plus how the 40/30/30 split actually swings across discovery, prototype, hardening and handoff phases of a single deployment.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>FDE Interview Prep: The 9 Rounds</title>
      <link>https://vibeengines.com/handbook/fde-interview-prep</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-interview-prep</guid>
      <category>Handbook</category>
      <description>The complete Forward Deployed Engineer interview guide \u2014 decomposition, learning round, incremental coding, debugging/re-engineering, take-home + defence, client roleplay, values, customer-flavoured system design and behavioural ownership. What each scores, the five signals every company screens for, a four-week plan, and an interactive drill for every round.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Palantir FDSE Interview</title>
      <link>https://vibeengines.com/handbook/fde-interview-palantir</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-interview-palantir</guid>
      <category>Handbook</category>
      <description>The loop that every other company copied: the online assessment, the panel drawn from a pool of five round types, and the decomposition round minute by minute \u2014 what strong candidates do in the first five minutes versus what fails. Plus the FDSE / Deployment Strategist split and a two-week prep plan.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The OpenAI FDE Interview</title>
      <link>https://vibeengines.com/handbook/fde-interview-openai</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-interview-openai</guid>
      <category>Handbook</category>
      <description>How the reported OpenAI forward deployed engineer loop works: the multi-hour API take-home, the required video walkthrough where it is actually graded, and the case/empathy rounds that carry roughly half the evaluation \u2014 with six habits that win the take-home.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Anthropic Applied AI / FDE Interview</title>
      <link>https://vibeengines.com/handbook/fde-interview-anthropic</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-interview-anthropic</guid>
      <category>Handbook</category>
      <description>The most agent-shaped FDE role at a frontier lab: the escalating-constraint coding assessment, the deployment case where negotiated evals win it, and the values round that candidate reports call the highest-failure stage \u2014 plus exactly how to prepare for it.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Sierra Agent Engineer Interview</title>
      <link>https://vibeengines.com/handbook/fde-interview-sierra</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-interview-sierra</guid>
      <category>Handbook</category>
      <description>Live incremental coding, a support agent you must build without an agent framework, and a debugging onsite with planted bugs. Why the no-framework constraint is the cleanest signal-extraction device in any published FDE loop \u2014 and the six decisions frameworks hide from you.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Distyl AI Interview (AI Allowed)</title>
      <link>https://vibeengines.com/handbook/fde-interview-distyl</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-interview-distyl</guid>
      <category>Handbook</category>
      <description>One of the few companies that publishes its interview philosophy: use AI in the take-home, then defend everything it produced. The three anti-patterns they reject \u2014 Autopilot, Default and Demo \u2014 and a phase-by-phase split of what stays human when AI is permitted.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The FDE Take-Home Playbook</title>
      <link>https://vibeengines.com/handbook/fde-take-home-playbook</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/fde-take-home-playbook</guid>
      <category>Handbook</category>
      <description>Take-homes are the centre of gravity in modern FDE loops and they are graded on judgement, not volume. The five-phase method with time budgets, what graders actually weight, a deliberately ambiguous five-hour practice spec, a 30-point self-scoring rubric, and how to prepare the video defence.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Evals for Client Work</title>
      <link>https://vibeengines.com/handbook/evals-for-client-work</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/evals-for-client-work</guid>
      <category>Handbook</category>
      <description>The most-cited hard skill in frontier-lab FDE job descriptions and the least taught anywhere: turning \u201cit should be accurate\u201d into a gate. Measure inter-expert agreement before you promise a number, build a golden set that survives contact, calibrate an LLM judge against human grades, wire the CI gate (including the per-case regression check), and hand the whole thing over.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Proving Value &amp; ROI</title>
      <link>https://vibeengines.com/handbook/proving-value-and-roi</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/proving-value-and-roi</guid>
      <category>Handbook</category>
      <description>Roughly 95% of enterprise AI pilots showed no measurable P&amp;L impact \u2014 and \u201cmeasurable\u201d is doing the work in that sentence. Capture the baseline in week one, agree one number, instrument adoption and override rate, survive the three standard ROI objections, and run the 45-minute business review that decides the renewal.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Incidents, On-Call &amp; SLAs for FDEs</title>
      <link>https://vibeengines.com/handbook/incidents-oncall-and-slas</link>
      <guid isPermaLink="true">https://vibeengines.com/handbook/incidents-oncall-and-slas</guid>
      <category>Handbook</category>
      <description>Production in an environment you do not own: negotiating an SLA whose clock starts when you are paged (not when a user noticed), surviving a one-person rotation, running an incident when logs cannot leave their network, writing a post-mortem with the renewal decision-maker in the room, and engineering your way out of the rotation in four milestones.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Decomposition Round, Simulated</title>
      <link>https://vibeengines.com/lab/decomposition-round-simulator</link>
      <guid isPermaLink="true">https://vibeengines.com/lab/decomposition-round-simulator</guid>
      <category>Lab</category>
      <description>Don't read about the FDE decomposition round \u2014 sit it. Pick a case (taxi fleet, emergency response, fraud unification, marketplace) and get scored on the five clarifying questions you ask &lt;em&gt;before&lt;/em&gt; the propose button unlocks, then on which sub-problems you attack and in what order, then on the two things you explicitly refuse to build. Premature solutioning scores negative, exactly like the real round. Ends with an interviewer verdict and a band. The signature Palantir-style round, interactive nowhere else.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Client Roleplay Simulator</title>
      <link>https://vibeengines.com/lab/client-roleplay-simulator</link>
      <guid isPermaLink="true">https://vibeengines.com/lab/client-roleplay-simulator</guid>
      <category>Lab</category>
      <description>The four conversations that actually decide deployments, as branching dialogue: your demo breaks in front of their CTO, a stakeholder insists on the wrong feature, security will not release the data, and a manager whose team gets smaller keeps raising objections. Every reply moves a live trust meter and changes what they say next. Ends with a scored verdict against the four signals FDE interviewers screen for \u2014 the round every guide tells you to rehearse with a friend.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Learning Round, Simulated</title>
      <link>https://vibeengines.com/lab/learning-round-lab</link>
      <guid isPermaLink="true">https://vibeengines.com/lab/learning-round-lab</guid>
      <category>Lab</category>
      <description>Learn a library that does not exist. You get the internal docs for &lt;code&gt;flowpkg&lt;/code&gt; \u2014 a package installer with dependency stages, a barrier between them, ordered post-install hooks and idempotent installs \u2014 in three unlocking sections with comprehension gates. Two rules are deliberately buried, and the last question can only be answered by combining rules from different sections. Tests reading strategy, not recall, exactly like the real round.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Eval Builder: From Fuzzy Goal to CI Gate</title>
      <link>https://vibeengines.com/lab/eval-builder</link>
      <guid isPermaLink="true">https://vibeengines.com/lab/eval-builder</guid>
      <category>Lab</category>
      <description>A customer says the system \u201cshould be accurate\u201d. Turn that into something a contract can rest on, in four acts: pick metrics (two of the strongest are not accuracy at all), discover the real ceiling by measuring how often the two human experts agree with &lt;em&gt;each other&lt;/em&gt;, configure and calibrate an LLM judge, then set a CI gate and watch it catch a change that raises overall accuracy while more than doubling the expensive errors. The most-cited hard skill in FDE job descriptions, made playable.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Re-Engineer a Legacy ETL</title>
      <link>https://vibeengines.com/challenge/legacy-etl-repair</link>
      <guid isPermaLink="true">https://vibeengines.com/challenge/legacy-etl-repair</guid>
      <category>Challenge</category>
      <description>You inherit an aggregation nobody can explain and the totals are wrong. Three planted defects \u2014 an exclude-list where the spec wants an include-list, a dedupe key missing a field, and pre-seeded customers that should never appear. The FDE re-engineering round. Solve it in Python or TypeScript, with hidden tests.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Repair the Spread Traversal</title>
      <link>https://vibeengines.com/challenge/infection-spread-repair</link>
      <guid isPermaLink="true">https://vibeengines.com/challenge/infection-spread-repair</guid>
      <category>Challenge</category>
      <description>Inherited code computes how far something spreads through a contact graph, and the answers are wrong in a way that is invisible on small inputs. A one-way adjacency map, a frontier with no dedupe, and a seen-set updated one step too late. Solve it in Python or TypeScript, with hidden tests.</description>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
