Google's interview system is not great but there are various reasons why it feels less than it is. Most candidates don't know what the goal of our interviews are. First rule, it is not about finding an optimal solution or any solution at all.
You are interviewed for multiple skills simultaneously. Cognitive skills, communication, leadership are a few to name. If the point is not finding a solution, then what is it? Let me explain.
Your interviewers try to understand what it feels like to work with you on a daily basis. An interview question is just a tool in achieving that, it is not there to specifically measure your skills on a topic but a tool to understand the depth of your thinking.
This thread is MISLEADING and is confusing the distributed tracing community. Picking OpenCensus has nothing to do with using a vendor specific instrumentation library. Libraries don't depend on vendor-specific bits. https://t.co/6f3NRZrv7I
Even though I have explained this reality to OpenTracing quite a few times in person myself, they still use this narrative to confuse the community and want the entire industry to depend on their product.
OpenCensus don't care about vendors as much as OpenTracing does. OpenTracing is a more vendor-centric model because the whole implementation is coming from the vendor. In the OpenCensus model, libraries collect data and hand them off to a vendor at the very end to upload data.