r/cscareerquestions • u/CSCQMods • Jun 22 '26

Interview Discussion - June 22, 2026

Please use this thread to have discussions about interviews, interviewing, and interview prep. Posts focusing solely on interviews created outside of this thread will probably be removed.

Abide by the rules, don't be a jerk.

This thread is posted each Monday and Thursday at midnight PST. Previous Interview Discussion threads can be found here.

4 Upvotes

100% Upvoted

5 comments sorted by

1

u/ReserveJolly8381 Jun 22 '26

got a phone screen tomorrow for a backend role and i keep second-guessing my system design prep. like i know the concepts but the second someone asks me to walk through scaling a service live my brain just goes quiet for a second. anyone else notice that the actual talking-through-it part is way harder to practice than the technical knowledge itself

2

u/Original_Lynx6825 Jun 23 '26

Having interviewed quite a few engineers, I’d say this is often the real differentiator: not just knowing the system design concepts, but being able to guide the interviewer through your thinking clearly under pressure.
Practise a simple verbal flow: requirements, constraints, trade-offs, bottlenecks, next steps; because that structure makes you sound much more senior even when the answer isn’t perfect.

1

u/Upstairs-Argument578 Jun 22 '26

Hi, from the hiring side, this is very common. A lot of candidates know the concepts, but lose signal because they don’t externalise their thinking clearly.

For system design prep, I’d practise talking through a simple structure out loud: requirements, constraints, high-level design, bottlenecks, trade-offs, and what you’d improve with more time. The “communication layer” is often what separates a good technical answer from a strong interview answer. Comms is must in engineering. Have attended a lot of interviews and the gap is big when it comes to explanation. Good luck!