▲ | nlawalker 5 days ago | ||||||||||||||||
> I want you to start with these answers then we can layer on complexity if you’ve solved the problem and there’s time left to go into navel gazing mode. Do you tell people this explicitly? If so, good on you; if not, please start! I think one of the biggest problems with interviews these days is misaligned expectations, particularly interviewees coming in assuming that what's desired is immediate evidence that they're so experienced in solving FAANG-scale problems that it's their default mode. | |||||||||||||||||
▲ | dondraper36 5 days ago | parent | next [-] | ||||||||||||||||
I believe even at FAANG-like companies, only a lucky minority is involved at that level of scale. Most developers just use the available infrastructure and tools without working on the creation of S3 or BigTable. | |||||||||||||||||
| |||||||||||||||||
▲ | Swizec 5 days ago | parent | prev | next [-] | ||||||||||||||||
> Do you tell people this explicitly? Yes and no. I give them rough scale numbers to design for. Part of the interview is knowing why I’m telling you this. | |||||||||||||||||
| |||||||||||||||||
▲ | renewiltord 5 days ago | parent | prev [-] | ||||||||||||||||
At the level where this matters, the skill to figure it out from context is important. You aren’t the guy converting spec to code. You’re the spec maker. | |||||||||||||||||
|