https://www.youngju.dev/blog 천천히 올바르게. AI Researcher & DevOps Engineer Youngju's blog. GPU/CUDA, LLM, MLOps, Kubernetes AI workloads, and data engineering — plus mindset essays on confidence, routines, health, and sport psychology. ko fjvbn2003@gmail.com (Youngju Kim) fjvbn2003@gmail.com (Youngju Kim) Wed, 12 Aug 2026 00:00:00 GMT https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production.en https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production.en A large share of PoCs that earn applause at the demo die quietly anyway — not for lack of technology, but because there were no success criteria, the security review started last, no champion existed, or the gap between the PoC environment and production surfaced too late. In a Forward Deployed Engineer (FDE) job, the stretch from PoC to production is decided by operational design more than engineering. This post covers the one-page success criteria document agreed before the start, the security review and data boundary defined in week one, the debt list hiding inside PoC code, and the handover document that keeps the system running after you leave — with document examples. All examples are constructed. Part 6 of the FDE Complete Guide series. Wed, 12 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) careerfdeforward-deployed-engineerpocproduction https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production.ja https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production.ja デモで拍手をもらったPoCのかなりの部分は、そのまま静かに死にます。技術が足りないからではなく、成功基準がなかったから、セキュリティレビューを最後に始めたから、チャンピオンがいなかったから、PoC環境と本番環境の差に気づくのが遅かったからです。Forward Deployed Engineer（FDE）の仕事の中で、PoCを本番に運ぶ区間は技術より運営設計が勝負どころです。開始前に合意する成功基準の文書、最初の週に始めるセキュリティレビューとデータ境界の定義、PoCコードが隠している負債のリスト、そして自分が去った後も回り続けるようにする引き継ぎ文書まで、文書例と共に整理しました。例はすべて構成した例です。FDE完全ガイドシリーズの第6回です。 Wed, 12 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) careerfdeforward-deployed-engineerpocproduction https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production 데모에서 박수를 받은 PoC의 상당수는 그대로 죽습니다. 기술이 부족해서가 아니라 성공 기준이 없어서, 보안 검토를 마지막에 시작해서, 챔피언이 없어서, PoC 환경과 프로덕션 환경의 격차를 늦게 발견해서입니다. Forward Deployed Engineer(FDE)의 일에서 PoC를 프로덕션으로 옮기는 구간은 기술보다 운영 설계가 승부처입니다. 시작 전에 합의하는 성공 기준 문서, 첫 주에 시작하는 보안 검토와 데이터 경계 정의, PoC 코드가 숨기고 있는 부채 목록, 그리고 떠난 뒤에도 굴러가게 만드는 인수인계 문서까지, 문서 예시와 함께 정리했습니다. 예시는 모두 구성한 예시입니다. FDE 완전 가이드 시리즈의 6편입니다. Wed, 12 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) careerfdeforward-deployed-engineerpocproduction https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production.zh https://www.youngju.dev/blog/career/2026-08-12-fde-poc-to-production.zh 在演示会上赢得掌声的 PoC，相当一部分还是会悄无声息地死掉。不是技术不行，而是因为没有成功标准、安全评审留到了最后、没有内部支持者、PoC 环境与生产环境的落差发现得太晚。在 Forward Deployed Engineer（FDE）的工作里，从 PoC 走到生产的这一段，胜负手是运营设计而非技术。本文整理了开工前与客户共同敲定的一页成功标准文档、第一周就启动的安全评审与数据边界定义、PoC 代码里藏着的负债清单，以及让系统在你离开之后继续运转的交接文档，均附文档示例。示例皆为构造的示例。这是 FDE 完全指南系列的第 6 篇。 Wed, 12 Aug 2026 00:00:00 GMT fjvbn2003@gmail.com (Youngju Kim) careerfdeforward-deployed-engineerpocproduction