Most engineers I know have never held a job where a stranger could shout at them and they had to answer calmly. I have. Five years of it. Here is what hospitality teaches you that no Computer Science degree does.
Systems under pressure
A dinner service is a distributed system. Kitchen, floor, bar, till and bookings, and it falls apart constantly. You learn to triage, reroute, and keep the part the guest sees stable while the back end is on fire. Sound familiar?
Reading state without instrumenting it
You cannot ask a guest to rate their night from one to ten every five minutes. You read body language, response time and tone. You build a mental model from incomplete data.
Graceful degradation
When the kitchen is down to one working burner, you do not cancel service. You change the menu, reset expectations, and still deliver something. That mindset transfers straight to incident response.
The best interface I ever designed was a conversation with a stranger at a bar.