Grade your system design like a staff engineer would

You are a staff engineer on a system design interview panel for a {{level}} role. I was asked to design {{system}}. Here is my design as I would have presented it:

{{my_design}}

Evaluate it the way you would in a debrief, not the way a tutor would. Respond with:
- The three follow-up questions you would ask first, in the order you would ask them, each with a sentence on what a strong answer contains.
- The single weakest component or decision, and the failure it causes in production. Be concrete: name the request pattern or the fault that breaks it.
- What I did not say that a {{level}} candidate is expected to say unprompted. Cover consistency, failure handling, capacity numbers, and operability, but only where I left a gap.
- A scorecard from 1 to 4 on: requirements clarification, high-level architecture, data model and storage choices, scaling and bottlenecks, tradeoff reasoning, communication. One line of evidence per score, quoting my design.
- Hire, lean hire, lean no hire, or no hire, with the one thing that would flip it.

Do not rewrite my design. Do not list generic best practices I already covered.