←back to thread

Ask HN: How to study for system design that doesn't include front end/back end?

38 points 3a2d29 | 1 comments | 13 Mar 25 23:32 UTC | HN request time: 0.21s | source

I got a system design interview where I was asked to build a pricer for a financial product, then expand it to multiple pricers that might share inputs.

This was not the typical system design interview where you have to deal with APIs / load balancers / latency / etc

I have studied that a lot, but what about these type of general interviews?

Show context
simonw ◴[14 Mar 25 00:24 UTC] No.43358532[source]▶
One general tip is to always ask (credible) clarifying questions. A lot of interviewers look out for this - they want to see you dissect the requirements a little bit, not just jump straight to solving the problem based on a bunch of assumptions you've made that might not be correct.
replies(1): >>43361345 #
1. nextts ◴[14 Mar 25 10:53 UTC] No.43361345[source]▶
This is big. Often will be on the senior plus rubric. "Did they ask clarifying questions?". Tick.

It also gives you constraints. Which are your friend.

I can't find it now (I tried but it was a year ago) but on YT there are some excellent example system designs where someone does it and then they talk about it. What was good. Why it was senior vs junior or senior vs principal.