I work at scale that is similar to twitter, just different concerns. Billions and billions of events where the results are expected in seconds or less. This is

I work at scale that is similar to twitter, just different concerns. Billions and billions of events where the results are expected in seconds or less. This is a beautiful example of how to ace a design interview. While we prefer folks with experience at scale, we are happy to bring on candidates lacking that experience when they can break down a problem like op did. I recently hired a dev who did not know about not trusting the network and duplicate delivery of packets and who was running into these issues at her own work (but was not senior enough to be "allowed to work on it"). However, she did break down our similar interview question. Even though she did not "ace" it, we can see her potential. Hired.