Fan-out looks like a speed decision and is actually a capacity decision. A sequential agent loop throttles itself — one request in flight, backpressure for free. The moment you dispatch fifty branches you have handed rate-limit management to the provider, and the provider manages it by refusing you. Three things to decide before you pick a library: how many run at once, what happens when one fails, and what you return when some succeed.
BM25 plus embeddings, then a cross-encoder over the top-k. The two stages buy different things and most teams cannot say which one they added. Hybrid search buys recall because lexical and vector retrieval fail on different queries; reranking buys precision because a cross-encoder reads the query and the document together. Here is what each one measurably adds, and how to tell when the reranker is buying you a rounding error.
Some AI-lab loops now include a round where you work with a model through an API in a notebook. It is not a prompt-writing contest. It tests whether you can call a model a thousand times safely, cheaply and measurably. The patterns that pass, with code.
Scaled dot-product attention fits in ten lines of NumPy. The interview is the follow-ups: why divide by the square root of d, how to make softmax stable, where the causal mask goes, what the KV cache saves, and why grouped-query attention exists. A complete walkthrough.
One problem, four levels, ninety minutes, and the requirements change every twenty. A full worked solution to the in-memory database problem family that candidates report from AI-lab assessments - and the three design choices in level one that decide whether you finish.
Fixed-size, semantic, and structure-aware chunking measured against real retrieval failures. The uncomfortable finding: your chunking choice barely moves whether the answer reaches the model, and hugely moves how much junk you pay for to get it there. Also, your chunk size is probably a library default nobody chose.
From an empty file to a server that Claude, Cursor and your own agent harness can all call. The code is short; the decisions that determine whether anyone can actually use it are the part worth slowing down for.
Agent Engine will host your agent without you writing a server, managing sessions, or provisioning anything. Getting there means understanding four things the documentation mentions in passing and that account for most failed first deploys.
The Agent Development Kit quickstart gets you a working agent in twenty lines. It also leaves out every decision that matters once the project is real — session state, tool ergonomics, and the deployment boundary that decides whether your agent runs at all.
Three mechanisms will force a model to return a schema, and teams pick between them by habit rather than by fit. They differ in guarantee strength, in latency, and in one under-discussed way: the strictest option can quietly make the content worse even as the format gets perfect.
In ordinary code an exception is a signal to a developer. In an agent, an uncaught exception kills the turn and throws away everything the model has figured out. The tool contract that makes agents recover instead of collapse is one rule long — and it changes how you write every tool.
Most agent failures that look like reasoning failures are tool-selection failures. The model picked the wrong function, or invented arguments, or did not realise a tool applied. Almost all of it is fixable in the schema — and the schema is prompt engineering, not API plumbing.
Every agent framework you will ever use is a wrapper around one while loop. Build that loop by hand once — with real tool dispatch, a stop condition, and a turn budget — and the frameworks stop being magic. This is the version you can debug at 2am.
Every agent demo dies the same death in production: it forgets. Context windows overflow, sessions end, processes crash. Designing agent memory — working context, episodic recall, durable checkpoints — is now a standard AI system design interview topic. Here is the architecture, layer by layer.
Model Context Protocol connects one agent to its tools. Agent2Agent connects agents to each other. Interviewers increasingly expect you to know which layer each one owns, what breaks without them, and how they compose in a real architecture. Here is the comparison nobody has written clearly.
MCP standardized how a single agent talks to tools and data. A2A standardizes how separate agents — possibly built on completely different frameworks — discover each other and delegate work. Here is what the protocol actually contains and why interviewers are starting to ask about it.
Plain LangChain chains run in a straight line. Real agents loop, branch, and retry. LangGraph models an agent as an explicit graph with shared state — here is how the core pieces fit together, with a minimal worked example.
LangChain gets a reputation for being over-abstracted, but the core ideas — chains, tools, memory, retrieval — are straightforward once you see them without the framework jargon. This is a free, from-scratch walkthrough of all four.