The latest articles on DEV Community by Saloni Tehariya (@saloni_tehariya_350b45c25). https://dev.to/saloni_tehariya_350b45c25 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4243954%2F2be8f0e0-e584-4c09-96b5-c5028f062ea8.png https://dev.to/saloni_tehariya_350b45c25 en Saloni Tehariya Sat, 14 Nov 2026 06:42:15 +0000 https://dev.to/saloni_tehariya_350b45c25/5-things-interviewers-listen-for-in-a-system-design-answer-that-most-candidates-skip-1ei5 https://dev.to/saloni_tehariya_350b45c25/5-things-interviewers-listen-for-in-a-system-design-answer-that-most-candidates-skip-1ei5 <p>Most system design rejections aren't about picking the wrong database. They're about how the answer is built. After reviewing a lot of practice answers, the same five gaps keep coming up.</p> <h2> 1. Jumping to components before constraints </h2> <p>"I'd use Kafka" in minute one tells the interviewer you're pattern-matching. Spend the first 3–5 minutes on users, read/write ratio, latency targets and scale. Say the numbers out loud.</p> <h2> 2. Listing tech without trade-offs </h2> <p>Redis, sharding, a queue: fine, but why? For each choice, name one thing you gain and one thing you give up. For example, sharding by user ID spreads load but makes cross-user queries expensive.</p> <h2> 3. No failure story </h2> <p>Ask yourself what happens when this node dies, this queue backs up, or this cache goes cold. One sentence per component is enough to signal seniority.</p> <h2> 4. Hedging language </h2> <p>"I think", "probably" and "it depends" with nothing after them read as low ownership. Replace them with: "I'd choose X because Y; if Z changes, I'd switch to W."</p> <h2> 5. No summary </h2> <p>End by walking the request path once, end to end, and naming the biggest risk. It shows structure and gives the interviewer an easy place to probe.</p> <h2> How to practice this </h2> <p>Record yourself answering one prompt ("design a URL shortener") out loud for 30 minutes. Replay it and tick off each of the five points. Do the same prompt again a few days later and compare.</p> <p>If you want structured feedback instead of self-review, I work on <a href="https://gignix.com/?utm_source=devto&amp;utm_medium=referral&amp;utm_campaign=backlinks" rel="noopener noreferrer">Gignix</a>, which runs AI mock interviews for coding, system design and behavioral rounds and gives a report on structure, depth and delivery. You can try one without signing up. But the recording method alone will get you most of the way.</p> <p>What's the gap you keep catching in your own answers?</p> career interview systemdesign beginners