Sources: Architecture grounded in HappyRobot's Technical Overview, AI Worker Capabilities page, and Carlos Becker Robles's article "Past, Present, and Future of the Forward Deployed Engineer at HappyRobot". Items marked CONFIRMED come directly from HappyRobot's own materials. Items marked EXAMPLE are illustrative.

HappyRobot Architecture β€” FDE at the Center

Two views of the same idea. The FDE View shows Carlos Becker's Venn diagram: the FDE sits where Product Capabilities, Customer Operations, and Business Outcomes overlap. The Architecture View shows the full technical stack with the FDE wrapping it as a cross-cutting role across the deployment lifecycle.
CARLOS BECKER ROBLES β€” "FDE AS THE BRIDGE BETWEEN PRODUCT AND REALITY" Click any circle to explore. The FDE sits where all three overlap. PRODUCT CAPABILITIES HappyRobot platform CUSTOMER OPERATIONS DHL, Ryder, etc. BUSINESS OUTCOMES Booked load Β· Resolved ticket Β· ROI FDE Forward Deployed Engineer FDE LIFECYCLE β€” CLICK ANY PHASE πŸ” Discovery πŸ—ΊοΈ Mapping πŸ”Œ Integration βš™οΈ Config & Prompt πŸ§ͺ Testing πŸš€ Deploy πŸ”„ Iterate
FDE LAYER πŸ” Discover πŸ—ΊοΈ Map πŸ”Œ Integrate βš™οΈ Config πŸ§ͺ Test πŸš€ Deploy πŸ‘οΈ Monitor πŸ”„ Iterate cross-cutting all layers CHANNELS πŸ“ž Phone SIP / WebRTC βœ‰οΈ Email SMTP / IMAP πŸ’¬ SMS / WhatsApp Messaging APIs 🌐 Web Chat WebRTC embed πŸ“„ Documents OCR / parsing πŸ–₯️ Portals / APIs Browser / REST RUNTIME EDGE β€” DUAL EDGE PATHS πŸ” SIP Gateway (Voice Edge) SIP-TLS + SRTP, BYO VoIP provider πŸ›‘οΈ WAF + LB (REST/Webhook Edge) TLS 1.3, validated traffic only 🎯 Tenant Routing & Sessions Per-tenant / per-call model selection AI WORKER RUNTIME β€” KUBERNETES, ADAPTER-BASED 🎚️ VAD In-house πŸŽ™οΈ ASR Adapter, fine-tuned ⏱️ End-of-Turn In-house 🧠 LLM Adapter, per-task πŸ”§ Tool Use API / transfer / code πŸ”Š TTS In-house πŸ•ΈοΈ Workflow Orchestration Multi-turn, multi-channel state 🧩 Shared Context & Memory Cross-session, entity-mapped 🀝 Human Handoff Smooth transfer w/ full context CUSTOMER SYSTEMS β€” NATIVE INTEGRATIONS πŸš› TMS / WMS Logistics systems 🏒 ERP / CRM SAP, etc. πŸ”Œ Internal APIs Proprietary DBs 🌐 Browser Agent Legacy portals πŸ“š Knowledge Docs / playbooks BUSINESS OUTCOMES 🎯 Booked load Β· Updated ETA Β· Resolved ticket Β· Scheduled appointment Β· Collected payment Β· Escalated exception Outcomes feed back into the Governance Layer below πŸ›‘οΈ GOVERNANCE β€” OBSERVABILITY Β· AI AUDITOR Β· COMPLIANCE (cross-cutting) Voice Experience Β· User Engagement Β· Agent Autonomy Β· Data Accuracy Β· Call Efficiency
FDE Layer (left)
Channels
Runtime Edge
AI Worker Runtime
Customer Systems
Business Outcomes
Governance (bottom)
🎯 You are looking at the FDE View: Carlos Becker Robles's framing of the Forward Deployed Engineer as the role that sits where Product Capabilities, Customer Operations, and Business Outcomes overlap.

Click any of the three Venn circles to explore. Click the FDE in the center to see the role itself. Click any lifecycle pill below to see what an FDE actually does in that phase.

Switch to Architecture View to see the FDE as a vertical band running across the technical stack.
Microsoft Privacy Statement