| System design depth | Covers contracts, data flow, bottlenecks, and failure recovery clearly. | Describes architecture at a surface level without operational detail. |
| Data strategy | Chooses storage and caching patterns aligned to access patterns. | Picks technologies by preference rather than workload fit. |
| Reliability planning | Defines observability, retry patterns, and degradation strategy. | Assumes happy-path behavior without failure planning. |
| Communication quality | Explains technical tradeoffs in concise, decision-oriented language. | Uses jargon-heavy explanations with unclear conclusions. |