{
  "schema_version": "1.1",
  "id": "s8:https://www.youtube.com/watch?v=Byv311hdoHE",
  "slug": "the-dirty-secret-of-forward-deployed-engineering-natalie-meurer-sierra-17crz97",
  "url": "https://feed7.dev/p/the-dirty-secret-of-forward-deployed-engineering-natalie-meurer-sierra-17crz97",
  "title": "The Dirty Secret of Forward Deployed Engineering — Natalie Meurer, Sierra",
  "why_included": "Forward-deployed engineering is not one role but a stack of customer-accountable work. Coding agents now let those engineers carry field insight through to production changes.",
  "summary": "Palantir’s forward-deployed work expanded from on-site **DevOps**, through data integration and custom solutions, to customer enablement. Meurer argues that cheap code now lets customer-facing engineers build end-to-end rather than merely relay requests.",
  "practical_implication": "Builders should define deployed roles by the customer outcome they own, not by a fashionable title. Keep a short feedback path from real usage to product changes, and let coding agents reduce the handoff between discovery, prototyping, and production work.",
  "agent_context": "Palantir’s forward-deployed work expanded from on-site **DevOps**, through data integration and custom solutions, to customer enablement. Meurer argues that cheap code now lets customer-facing engineers build end-to-end rather than merely relay requests.\n\nBuilders should define deployed roles by the customer outcome they own, not by a fashionable title. Keep a short feedback path from real usage to product changes, and let coding agents reduce the handoff between discovery, prototyping, and production work.\n\nThe history is a practitioner’s account, not a universal organizational template. The further claim that most software pricing will become **outcome-based** is a forecast, and many products cannot cleanly attribute an outcome to one system.",
  "source": {
    "name": "AI Engineer",
    "url": "https://www.youtube.com/watch?v=Byv311hdoHE",
    "published_at": "2026-07-28T18:00:18.000Z"
  },
  "source_class": "video",
  "content_type": "Video",
  "layer": "industry",
  "domains": [
    "coding",
    "data"
  ],
  "topics": [
    "coding-agents",
    "enterprise",
    "adoption"
  ],
  "verification": {
    "status": "source_linked",
    "label": "Source Linked",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "The history is a practitioner’s account, not a universal organizational template. The further claim that most software pricing will become **outcome-based** is a forecast, and many products cannot cleanly attribute an outcome to one system."
  ],
  "connected_context": {
    "meaning": "This reframes forward-deployed engineering as ownership of customer outcomes rather than a fixed job title, and argues that coding agents compress the handoffs between discovery and production. It strengthens the case for customer-facing engineers as builders, but does not establish that this structure fits every product; the further move toward outcome-based pricing remains a forecast constrained by attribution problems.",
    "corpus_size": 262,
    "generated_at": "2026-07-29T10:05:45.020Z",
    "connections": [
      {
        "title": "Forward Deployed Engineering 101 — Kevin Bai, Anthropic, ex Palantir & Rippling Founding FDE",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=KwhgfwOSToQ",
        "feed7_url": "https://feed7.dev/p/forward-deployed-engineering-101-kevin-bai-anthropic-ex-palantir-ripplin-1rzcr0v",
        "reason": "Bai narrows Meurer’s broad organizational thesis by requiring deployed work to compose shared platform primitives rather than accumulate bespoke customer codebases."
      },
      {
        "title": "Forward Deployed Engineering at Cursor — Pauline Brunet",
        "source_name": "YouTube",
        "source_url": "https://www.youtube.com/watch?v=APqXGyCoGW4",
        "feed7_url": "https://feed7.dev/p/forward-deployed-engineering-at-cursor-pauline-brunet-1wkd3r1",
        "reason": "Cursor adds operating safeguards to end-to-end customer accountability: measurable use cases, customer ownership, explicit handoff, and avoidance of staff augmentation."
      },
      {
        "title": "How Forward Deployed Engineering is done at Cognition — Jia Wu",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=RVxym6mmIns",
        "feed7_url": "https://feed7.dev/p/how-forward-deployed-engineering-is-done-at-cognition-jia-wu-06h8ybj",
        "reason": "Cognition translates Meurer’s outcome-ownership principle into proposed deployment measures such as delivery timelines and accepted customer work, while retaining evidence limitations."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-07-28T18:00:18.000Z",
  "modified_at": "2026-07-28T18:00:18.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/the-dirty-secret-of-forward-deployed-engineering-natalie-meurer-sierra-17crz97",
    "json": "https://feed7.dev/p/the-dirty-secret-of-forward-deployed-engineering-natalie-meurer-sierra-17crz97.json",
    "markdown": "https://feed7.dev/p/the-dirty-secret-of-forward-deployed-engineering-natalie-meurer-sierra-17crz97.md"
  }
}