Earlier quoted context omitted.
I see your point. My intention is mostly to spark a conversation but I'm guessing this approach might not be the best. What would you think is a decent question that allows enough freedom in the answer? Unfortunately there's seems to be a lot of confusion about what an answer to my question should be like, not only in this thread but on the web in general. It almost feels like the definition of REST or its idea has b…
I don't think asking about REST is a bad question and it's definitely a good inroads to conversation; you should just be aware of both the original work and the variety of different understandings so that you can make good use of that conversation and recognize that skilled candidates are likely to have differing ideas about REST.
No matter what, if you're an experienced back end Engineer shouldn't you be able to go over this question without too much trouble or hesitation? Shouldn't you have explored this topic before? Is this a flawed or wrong assumption?
Sorry for the long comment, I'm really appreciating you helping me making this more clear.