Identify the conditions under which the 'no framework' (raw SDK) pattern is the better choice, select all that apply · Zenaique

Attempt it

The 'no framework' pattern means using the raw provider SDK (the `openai` package, the `anthropic` package, the Vercel `ai` package's core primitives) and writing your own composition logic. It is not always wrong; in specific conditions it is the better choice. **Conditions where raw SDK wins (the correct answers):** - **Small surface.** One or two prompts with no composition. The framework would add tax without absorbing real work. - **Day-one provider feature.** When OpenAI ships a feature (caching, computer use) and you need it this week, the framework wrapper is 4-8 weeks behind; you write the raw call anyway. - **Tight latency.** Framework dispatch adds milliseconds; on a hot path with a sub-100ms budget, the overhead matters. - **Small team.** A two-engineer team can carry a hand-rolled composition layer in their heads; a framework's vocabulary is overhead they do not need. **Conditions where the framework wins (the wrong answers):** - **12-agent system with routing and HITL.** This is exactly the composition complexity a framework absorbs. Rebuilding LangGraph's state-machine and checkpointer from scratch would be months of work. - **Regulatory observability.** This is a reason to add OpenTelemetry, not a reason to drop the framework. The two concerns are independent; you can have a framework with OTel observability, or no framework with OTel observability.

**The pattern: match the framework decision to the shape of the work.** No-framework is a sharp pick in four scenarios, the wrong pick in two. **Where no-framework wins:** 1. **Single-prompt or two-prompt products.** Framework value is composition; without composition there is no value to extract. Raw SDK is faster to write, smaller to ship, easier to debug. 2. **Day-one provider features.** Wrapper lag (4-8 weeks) means urgent features get written as raw-SDK bypasses anyway. Better to start there than maintain both paths. 3. **Hard latency budgets.** Framework dispatch overhead is measurable. On a sub-100ms hot path (autocomplete, real-time scoring), the overhead can blow the budget. 4. **Small teams without need for a shared composition vocabulary.** A two-engineer team can carry a hand-rolled composition layer in their heads. **Where the framework wins:** - **12-agent system with tool-routing, supervisor logic, and HITL interrupts.** The textbook composition-complexity case. LangGraph's State + Node + Edge plus checkpointer absorb hundreds of lines of state-machine code. Rebuilding from scratch is months of work. - **Observability as a regulatory requirement.** Orthogonal to framework choice. The right response is to wire OpenTelemetry; you can do that with a framework or without one. Dropping the framework does not solve the observability problem; adding OTel does. **The senior insight.** The question is not 'frameworks good or bad?' It is 'does this problem need the composition primitives a framework provides?' Four options describe problems that do not; two describe problems that do.

Quick reference

TL;DR

Raw SDK wins on small surface, urgent provider features, tight latency, and small teams; loses on complex multi-agent systems; observability requirements are an independent axis.

Memory aid

Sign in for the mnemonic that makes this stick. See Pro pricing.

Easy to grasp

Picture choosing between a Swiss Army knife and a single sharp kitchen knife. The Swiss Army knife is great when you need 10 different tools because each one is right there and you do not have to carry 10 separate items. The kitchen knife is great when you only need to chop one thing, when you need the absolute sharpest edge, or when you want to be in and out fast. Neither is universally better; the right pick depends on the job. The raw SDK is the kitchen knife; the framework is the Swiss Army knife.

Key concepts

Detailed answer & concept explanation

~7 min read

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.

Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.

Sign in for 5 free unlocks/day or go Pro for unlimited. See Pro pricing.

Quick scan · 2–4 min

Everything important, quickly.

5 min: four conditions where raw SDK wins + textbook conditions where framework wins + observability as independent axis + per-surface decision-making + Vercel AI SDK as middle ground + migration path between raw and framework.

Real-world examples

Real products, models, and research that use this idea.

Cursor's autocomplete reportedly uses raw provider SDK for the latency-critical path; the framework would add measurable overhead.
Linear's simple AI features (single-prompt summarisation, classification) use raw SDK; their multi-step issue-triage uses LangGraph.
Klarna's customer-support agent uses LangChain plus LangGraph because the workflow has 10+ agents with routing and HITL.
Many early-stage YC AI startups ship the first prototype on raw SDK because the team is two engineers and the surface is one chain; they revisit framework choice at month six.
Vercel's own AI SDK is the closest to a thin by design framework, occupying middle ground between raw SDK and a full framework like LangChain.

Interviewer follow-ups

What an interviewer would ask next. Try answering before peeking at the approach.

QWalk through a no-framework pattern for a RAG pipeline.

Sign in or go Pro to see the approach for this follow-up.

QWhat is the migration path from no-framework to a framework if the product grows?

Sign in or go Pro to see the approach for this follow-up.

QWhere does the Vercel AI SDK sit on this axis?

Sign in or go Pro to see the approach for this follow-up.

Don't say this

Red flags and common mistakes that signal junior thinking. Click to expand.

Most common mistake

Reading 'observability is a regulatory requirement' as a vote for no-framework. The right answer is to wire OTel, which is a separate concern from framework choice.

Sign in or go Pro to see all red flags and common mistakes. See Pro pricing.

60-second cheat sheet

The night-before-the-interview bullets. Scan these on the way to the call.

Sign in for 5 unlocks/day or go Pro for unlimited revision sheets. See Pro pricing.

References

Primary sources. Skim if you want the original framing.