Earlier quoted context omitted.
> Like, how good of a signal can companies really be getting if it's too different from real world systems? There are "layers" to the signal you can get from system design interviews: 1. Are they aware of "big concepts", indexing, sharding, queues, scheduling, etc. 2. Are they comfortable actually using and manipulating these abstractions in an academic sense? e.g. new college grads may have never used an index, but…
"walk through a zero downtime migration plan from before and after we add a feature." How does one approach this?
https://martinfowler.com/books/refactoringDatabases.html https://databaserefactoring.com/