YOUR SCENARIO
How would you approach this?
An internal assistant passes its pilot review. Your engagement ends next week, and the customer's platform team will own it. What must be in the handover for the system to remain useful?
This is an illustrative practice scenario. State any additional assumptions in your answer.
Make your case first.
Clarify the goal, identify the biggest uncertainty, outline an approach, and explain how you would test it. Spend about 10 minutes before opening the reference.
Your notes are not submitted or saved. Keep a copy before leaving this page.
Reveal reference approach Clarifying questions, decisions, and tradeoffs
Clarify before designing.
- Who owns document updates, application incidents, and model or prompt changes?
- Which operating commitments and escalation hours has the customer accepted?
One defensible approach
- 01
Transfer an operating contract
Document supported workflows, known limitations, permissions, versioned configuration, and what the customer accepted. Identify each ongoing task and a named team responsible for it, including data freshness and deletion.
- 02
Rehearse common failures
Ask the new operators to diagnose a failed ingestion, inspect a poor answer, and exercise a fallback in a test environment. Supply dashboards and a runbook organized around symptoms, evidence, and reversible recovery steps.
- 03
Make changes reviewable
Provide the evaluation set, its access rules, release checks, and rollback procedure. Explain how new failure examples enter the suite. Agree on how future work becomes reusable product improvements rather than an undocumented customer-specific patch.
Explain the tradeoff
Extensive documentation is expensive to maintain. Prioritize the actions the receiving team must perform and verify that the handover actually enables them.
Common mistakes
- Handing over only source code and API credentials.
- Reporting pilot success as proof of long-term reliability.
KEEP THE CONVERSATION GOING
Try the follow-ups.
- How do you handle an upstream model version change after you leave?
- Which customer-specific pieces would you generalize?
Review your own answer.
Tick the points you covered. This is a reflection checklist, not an automated score or a hiring prediction.
Check the underlying concepts.
The scenario and reference approach were written for SaveMyToken. These sources support the technical concepts; they do not report this question being asked by an employer.
Google SRE: Implementing SLOs ↗Google SRE: Canarying releases ↗