CodingChef

Also yes my boss likes me! He/she always mention the luck of having me around making the vision possible! And sometimes even complain with me about this other employee (to a point that there was a will to cut him/her loose if some issues weren't addressed asap).

Yes! Thanks for the link. I have the trust as I'm assigned crucial projects and I usually know company direction before many other people. I'm currently trusted with the most important project which makes this inequality I mentioned very odd.

Does anybody have a recommendation for a book on category theory?

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.

Your disappointment is absolutely legitimate. I feel like this term has then be abused a lot, in many write ups as well. I guess from me too. Thanks for pointing it out, I'll make sure to use a different approach in the future that can lead to a better conversation with the interviewee.

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!

That's great input thank you, I like your approach much better and it still provides freedom in the answer.

- what do you mean? - CRUD? - GET, POST, PUT, DELETE

(Question marks are part of the answers, now with the third answer I'm usually fairly happy to begin with and I go into other questions, but that should be the bare minimum).

I've been asked this question as well when interviewing for a frontend position and I just mentioned a few key points and they were very happy about it. But if you're applying for a backend position shouldn't you know more?

Thanks for your great input! Multiple times the only answer I got was "CRUD", without any explanation. Which from a certain perspective it relates to REST but from an experienced engineer is expected a little more, nothing specific just anything really.

It's not a personal definition I'm looking for, I'm pretty sure all of those experts would mention at least once "stateless". And to be honest I would be happy with that, I would just like to get any answer and if it makes sense I'd be ok with that. I'd like to get something reasonable I'm not asking for the Stars.

That is understandable and I'm not a back end Engineer either. But I had an interview with a back end Engineer with like six years of experience. And I really thought that a simple question like this would make them feel at ease because they would know it right away.

Why is that?