←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.259s | 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
yapyap ◴[13 Mar 25 23:56 UTC] No.43358416[source]▶
That’s back end no? unless you have to make a GUI for it, then it’s front- and backend.
replies(1): >>43359435 #
1. briankelly ◴[14 Mar 25 03:52 UTC] No.43359435[source]▶
The difference is if you are asked about the 5 (or however you slice it) layers vs just 1 or 2 it leads to two kinds different kinds of discussions. The latter gets very specific.