architecture

Recommend an approach to a CEO who needs a product decision. Explain what retrieval and fine-tuning each change, then connect that difference to freshness, reliability and cost.

A larger context window changes what fits in a request. Decide whether to use it by checking corpus size, freshness, permissions and cost per successful query, including cache misses.

A design trade-off with cost, accuracy and latency all pulling differently. The interviewer wants a measured comparison on real receipts and a hybrid that sends each image down the cheapest path that works.

There is no single best model, and the choice will change within a year. Principal answers design a selection process and an architecture that make the next choice cheap.

A small architectural component with outsized strategic value. The interviewer wants to hear what it does day to day and why it matters when a provider changes prices or goes down.

Every AI product depends on services it does not control. The interviewer wants a degradation plan by feature, written and tested before the outage starts.

Guardrails are often described as a box in a diagram. The interviewer wants specific checks, where each runs, what it costs in latency, and what happens when one fires.

Choose the least autonomy that does the job, explain exactly which step deserves a model, and know the one place in onboarding where an agent may genuinely earn its keep.

The compounding arithmetic every agent PM should be able to do in their head. Once you show 0.95 to the tenth power, the interviewer wants to know which of four levers you would pull first.

Multi-agent diagrams look sophisticated in a design review. The interviewer is checking whether you can name the specific conditions that justify them and the costs they add.

A platform decision with a three-year shadow. Hosted platforms ship faster today; owning the stack keeps options open. Principal answers decide which layers must stay portable and accept convenience everywhere else.

Two problems hide in one complaint: the agent is slow, and waiting for it feels worse than it needs to. Strong answers attack both, and question whether every task should make the user wait at all.