38 points 3a2d29 | 1 comments | 13 Mar 25 23:32 UTC | HN request time: 0.263s | 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?

1. rahimnathwani ◴[13 Mar 25 23:53 UTC] No.43358397[source]▶

>>43358293 (OP) #

Maybe 'Design of computer programs'? https://www.udacity.com/course/design-of-computer-programs--...

Or study some of Peter Norvig's code for solving poker hands, sudoku etc.?

It's not obvious how to build abstractions at the right level, or to change those abstractions as requirements change.

↑

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