CSE Roadmap

Common tier · about 4 hours · 12 parts

Part 7 of 12 · 2 min read

Answering framework-choice questions in an interview

How do you choose an agent framework?

"I start from the requirements the framework must meet and compare on capabilities that are stable: state and persistence, pause and resume, multi-agent control, tracing, provider portability and deployment. Brand comes last. I begin with a thin loop on the provider API if the task is small, and I put the framework behind my own interface so that it can be replaced." Follow-up: "Which would you pick for a long-running approval workflow?" One with a documented durable checkpoint store and a pause primitive, such as LangGraph's checkpointers with human-in-the-loop; I would verify the current docs and test a crash-and-resume before committing.

What does checkpointing give you, and what does it not?

"It lets a run resume from the last saved step, so fewer repeated model calls and more completed runs. In the example's simulation at 30 percent crashes per step, calls fell from 11.6 to 8.0 and completion rose from 67.5 to 94.5 percent. It does not make side effects exactly-once: a crash between the effect and the checkpoint repeats the step, so I add idempotency keys; with them duplicates went from 0.34 to 0 at 15 percent." Follow-up: "Why not just checkpoint after every effect?" Still a gap between the effect and the write; only an idempotent receiver closes it.

Handoff or agent-as-tool?

"Handoff transfers control, so the specialist talks to the user and sees the history; agent-as-tool keeps a manager in charge and passes a brief. Handoff is simpler for two agents; agent-as-tool avoids carrying a long history, and in my token model it was cheaper from three specialists up, 17,250 against 19,500 at five. The numbers depend on brief and summary sizes." Follow-up: "Which is easier to debug?" OpenAI's guide lists trace legibility as a reason to split at all; I would pick the one whose trace I can read.

Why not use a framework for everything?

"A framework hides the loop, and when an agent misbehaves I must know the exact prompts, tool results and stop reasons. It can also add a dependency that changes quickly. I use one when it provides something I would otherwise build and maintain, like durable state or tracing." Follow-up: "What do you lose by building directly?" Integrations, community patterns and, often, durable execution that is hard to get right.