System design interviews. Do you actually list out sql types
For example, do you write each column’s data type? Like int, long, datetime etc. And do you actually calculate how many bytes you need for each column?
Types not necessarily, bytes yes (especially when solving problems like url shortening, hashing)
Ok literally all 3 responses have been different lol
did you get job from FB ?
Yes and no
Summary: Maybe
Better summary: it depends. The URL shortener and hashing examples are instances where you would probably want to do that. So might be a distributed web crawler, or an app that tracks historical prices of items on Amazon. Where might you not care? When you know the whole data set is small enough that you don’t have to, or there is an obvious way of storing the data so that you know one database instance will be enough. (Turns our that storing every product id on Amazon actually falls into this category, too, but you might need to think a little to realize that.)
All of the system design interviews I have done haven't needed to go that deep.
If you're asked to be this specific, it means your interview is not about system design at all, irrespective of the interviewer understanding this.
sql tables does not sound like “system design”
A general sense of the types, their size, the approximate size of a row and approximate overall data size is easy to do and will definitely impress your interviewer. See https://www.practicecodinginterview.com/blog/2018/8/18/the-system-design-interview
No, dont need that. Hardly ever need full schema