hardPalantirSierraMicrosoft

The customer's system of record is a legacy GUI/API they can't change. Build an agent on top, where do you put the brittleness?

The most FDE question in the bank: every real deployment hits an unchangeable legacy system. The answer is an architectural principle, concentrate brittleness in one owned layer, plus what to do when the GUI is the only API.

Updated Aug 2026 · Grounded in real Forward Deployed Engineer interview loops and written to a senior-engineer editorial bar.

20 answers per topic instead of 10, plus saved progress and bookmarks · no cardor unlock all 548 remaining answers · ₹2,000 / $25

Every answer, concept and course, every paper breakdown, all published video lessons, hands-on FDE Lab missions, Premium PDF guides and companion files, the full practice-test bank and work-sample downloads. Referral Premium excludes guide PDFs and their companion files.

6 months · One payment · No auto-renewal

Study alongside free video lessons.

Keep practising

Next in this trackTake a RAG POC from 50 docs in a notebook to 5M docs, 2k QPS, and a 99.9% SLAPremium Next in this trackA/B test a conversational agent when 'success' is fuzzy, resolution, CSAT, deflection without angerPremium Next in this trackSingle tool-loop, planner-executor, or multi-agent: how do you choose an agent architecture?Premium

DISCUSSION · 0

No comments yet — be the first to share your approach.

The customer's system of record is a legacy GUI/API they can't change. Build an agent on top, where do you put the brittleness?

Read the related research

Keep practising