Ai Coding And Product Systems hard
Your assistant uses a classifier to route queries to a small or large model, which saves 60% of GPU spend. Analysis shows about 20% of hard queries are misrouted to the small model, which then gives confident wrong answers, and regenerate clicks on those threads have doubled. What should you do?
- A Send all traffic to the large model, since misrouting costs more in lost user trust than the GPU savings could justify at any scale.
- B Route on prompt length alone, since long prompts correlate with difficulty and length is free to compute before inference.
- C Bias the router toward the large model when uncertain and retrain it on regenerate and thumbs-down signals, accepting some cost.
- D Cascade every query: the small model answers and the large model verifies each response before display as a quality gate.
Answer: C. Bias the router toward the large model when uncertain and retrain it on regenerate and thumbs-down signals, accepting some cost.
Routing is a **cost versus quality dial**. Making uncertain cases fall back to the large model gives up a little savings to remove the worst failures, and implicit feedback improves the router over time. Verifying every query (D) adds latency and large-model cost to every request, which defeats routing. It makes sense only for high-stakes domains where every answer must be checked.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- Your workspace AI retrieves the top-k chunks from a shared vector index and passes them to the model with ACL metadata and a system prompt saying 'only use documents this user can access.' A user just received an answer quoting a private HR page they cannot open. What is the correct fix?
- Your support bot answers billing questions. One user has asked the same refund question three times, and retrieval confidence for that topic is low. What should the bot do next?
- Your AI review system receives a 4,000-line pull request spanning 60 files. Sending the whole diff in one prompt yields shallow, generic comments, and real bugs in files near the middle of the diff are missed. How should you structure the review?
- In your ChatGPT-style assistant, power users keep single threads running for weeks, reaching about 150K tokens. Cost per turn keeps climbing, latency is rising, and the model increasingly misses facts from early in the thread. What should you do?
- Your workspace AI filters retrieval using ACLs stored in the vector index, which is rebuilt nightly. An admin removes an employee from a confidential project page, but for the rest of the day the employee can still get AI answers drawn from it. What is the right fix?
- Free users consume 70% of your assistant's GPU hours but bring in about 5% of revenue through conversions. Leadership wants to keep the free tier useful enough to drive upgrades. Which policy fits?