I specifically kept it vague for reasons of anonymity, as these types of statements have cost people their jobs in the past, and also due to the fact that what

I specifically kept it vague for reasons of anonymity, as these types of statements have cost people their jobs in the past, and also due to the fact that what I described was work habits of people I talk to across different engineering roles (software, hardware, infrastructure) in the company I work for. You can work less than 60 hours, but it will show in your output, as deadlines are aggressive and set tops down. Examples of the kind of thing someone is answering emails in the early morning for is bugs discovered in your code, a regression that's failing, or something found that's blocking another coworkers' progress (since they were working late into the night as well).