Not what I expected. Completely unrealistic to the real world. Great if you want to quote a text book, PMBOK or Scrum Guide. 1. I would never run a scrum planning meeting with out first and foremost having an in-depth meeting with my team members and Product Owner explain the scrum process and roles. This is not something will ever or should ever be done in the first sprint planning meeting. Just bad consulting and communication. 2. I have never had a client care about the different types or definitions of scope.... its more along the lines of here's what I need done now figure it out. Projects are fluid unlike the interview process. Maybe focus more on... "How do you handle the situation when 2 developers are at odds, but needed to pair program to complete a piece of important code?" "How do you handing the situation when you under estimated your story points and now you are mid-sprint and need to change things?" "Tell me about a time you had a CTO breathing down your next because you are already $2.5M in the whole and the vendor is not delivering their end of the contract?" I'm just saying.. its a little more then a textbook answer. I stopped the interview over halfway through because I was getting the impression by the questions I was being asked that I was going to be a very hands off PM and just going through the motion then actually making a difference. Maybe that not how it actually is to work for Toptal, but I may also operate in a non-traditional out of the box way that doesn't allow me to shine in "traditional interviews"