Here's how I was assessed for my job at Pivotal: 1. I did a simple tech screen (the RPI). 1 hour. My interviewer had a laptop and asked me questions about what to do next in the scenario. 2. Hey, come pair with this engineer on this real code on a real project on a real task. 3. How about lunch? 4. Hey, let's have you pair with this other engineer on real code on a real project on a real task. 5. Get offered a job on…
"Hey, come pair with this engineer on this real code on a real project on a real task." I don't understand how I could pair-program effectively on a code base that I'm seeing for the first time and don't know the first thing about. What would you expect me to be able to contribute?
Nobody expects you to magically know anything about code you've never seen before. That would be absurd.
The point is to get a sense of how you think and work as an engineer. We deliberately say that there are no "wrong" answers, that it's impossible to fuck up.
We want to know about the candidate. The decision is about hiring a person, not a list of codebases.
(Sorry for the slow reply, I was rate-limited.)