Question presented to candidate: "You will see ReAct mentioned in almost every agent framework. What is the ReAct pattern, what problem was it solving when it appeared, and how much of it is still relevant now that models have native tool calling and built-in reasoning?"
What a strong answer should cover:
- ReAct means Reason + Act: the model interleaves a written thought, an action (a tool call) and the observation the runtime returns, and repeats until it can answer
- The two failure modes it fixed: reasoning alone (chain-of-thought) invents facts it cannot check, and acting alone picks tools with no plan; interleaving grounds each thought in the latest observation
- Where it came from: Yao et al., "ReAct: Synergizing Reasoning and Acting in Language Models" (arXiv October 2022, ICLR 2023), with large gains on interactive tasks such as ALFWorld and WebShop
- How the original text format worked and broke: Thought / Action / Observation lines parsed with a regex, a stop sequence so the model cannot write its own observation, and format errors returned as observations
- What changed: native tool calling replaced the text parsing, and reasoning models do the thinking in their own reasoning tokens, but the loop shape, debuggable traces and observation-grounded steps remain the default
- Its limits: it is greedy and step-by-step, so long tasks may need an explicit plan, reflection or a multi-agent split
Code / implementation expected: Optional β the Thought / Action / Observation loop with a stop sequence, or the same loop with native tool calls.