What is context engineering, and why does it matter for agents?
Agents and tools · Pro 1
Short answer
Context engineering is deciding what information goes into the model's limited context at each step: instructions, tool definitions, retrieved documents, memory and previous results. Agents run many steps, so context fills with tool output and history. Good practice keeps it small and relevant: compact or summarise old steps, load details only when needed, and store notes outside the context.
Deeper answer
Models get worse and costlier as context grows with irrelevant material, sometimes called context rot. Techniques: just-in-time retrieval instead of loading everything; summarising and clearing old tool results; giving sub-agents their own clean context; and structured note files the agent can read back.
It is the agent version of prompt engineering: less about wording, more about choosing which tokens earn their place.
What a strong answer covers
- Choosing what goes into the context at each step
- Context is limited and fills during agent runs
- Compaction or summarising old steps
- Load details just in time
- External notes or sub-agent contexts
Answer it out loud in the mock interview about 1.5 min
Follow-ups to expect
- How would you handle a tool that returns a 50-page document?
- What should stay in context for every step?
Common mistakes
- Loading every document up front
- Letting tool output pile up unchecked
Learn it
- What are common failure modes of agents, and how do you guard against them?
- What kinds of memory can an agent have, and how do you implement them?
- Your agent ran overnight and ran up a large API bill. What probably happened, and what do you change?
- How would you design a harness for an agent that has to work on one task for several hours?
- What is the difference between an agent and a workflow?
- What are computer-use or browser agents good for, and what are their risks?
- An agent completes a task correctly most of the time but sometimes goes badly wrong. How do you debug it?
- What makes a good tool for an agent?
- Design an agent that handles refund requests for an online store.
- You changed your agent's harness. How do you prove the change made it better?
- What are verification gates in an agent harness, and how would you add them to a coding agent?
- How does tool calling work?
- When should an AI agent ask a human for approval before acting?
- Explain state, nodes, edges and checkpoints in LangGraph.
- What are planning and reflection in agents, and when do they help?
- Two coding agents use the same model, but one solves far more of your tasks. Why could that be, and how would you find out?
- What is an agent harness, and what is harness engineering?
- What is the Model Context Protocol, and why does it matter?
- When is a multi-agent system worth it, and what are the risks?