FREE AI INTERVIEW QUESTIONS & ANSWERS
Prepare for AI engineer and Forward Deployed Engineer (FDE) interviews with free topic questions, matched source answers, foundation practice, and customer scenarios. All questions and answers are in English, with original source numbers preserved.
Explain the concept aloud, reveal the reference answer, and use the linked lab to try it yourself.
15 questions · Showing 1–10
For a client-side tool, the application receives the proposal, validates and authorizes it, executes the operation, and returns the result to the model or controller.
Watch for: Generated arguments are a proposal, not proof of permission.
Give the tool a specific purpose, clear argument names, types, required fields, and constraints. Define how failure is returned so the caller can react appropriately.
Watch for: A broad tool named do_anything makes both selection and permission checks harder.
At the execution boundary before side effects, even if upstream generation used a schema. Validate allowed values and resource scope, not just JSON syntax.
Watch for: A valid ID can still belong to a different user.
Only when the failure is plausibly temporary and the operation is safe to repeat or protected against duplicate effects. Apply attempt and time limits.
Watch for: A timeout does not prove that a remote write never happened.
Return the data required for the next decision, an explicit status, and useful bounded error information. Preserve evidence references when the result supports a factual claim.
Watch for: Dumping entire logs or credentials into the model context is unnecessary.
The next decision should use the observed result of the previous action and the remaining task state. The controller should not treat a proposed action as already completed.
Watch for: Planning text alone does not establish execution success.
Task acceptance, permanent failure, attempt exhaustion, elapsed-time limits, spending limits, and cancellation. Choose the appropriate conditions for the operation being performed.
Watch for: One universal iteration count cannot protect against every failure.
Classify it, check whether repetition is safe, and retry within bounded attempts and time. Respect service retry guidance and avoid synchronized retry bursts.
Watch for: A validation error generally needs corrected input rather than the same retry.
Record completed actions, evidence, unresolved work, and the reason for stopping. Make any external effects visible so the next attempt can resume safely.
Watch for: Calling the whole task failed can hide actions that already succeeded.
Track attempted actions and their outcomes, detect unproductive repetition, and require new information or escalation before repeating the same failed approach.
Watch for: Changing the wording of the same action is not necessarily progress.
