[CodingChef]

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 been re formulated over the years from the original thesis work. Thanks again for your input!

[dragonwriter]

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.

[CodingChef]

I agree with you but my concern is coming from the fact that a lot of people don't have an opinion or idea about it. I understand that there could be different visions, especially different from mine. I'm ok with any opinion in Regards of REST but I guess what I'm trying to understand from this thread is if a backend engineer should have a minimal formulated idea about REST ( which can align with any of the visions we can find with a simple web search), or if it doesn't matter at all. Is it fair to ask this question and expect some sort of vision about REST from an experienced engineer, or should I try to make a more specific question to avoid this confusion altogether?

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.