[wslh]

Just based on your comment, I would have asked the candidate if he/she would be available outside 9-5 hours in case of an emergency, understanding that the organization will do as much as possible to stay 9-5. I have seen several employees not caring about that detail which can harm the organization.

[nrki]

Symptom of an organization that doesn't plan and instead of budgeting for 1.3x employees for outside hours support, budgets for ~0.9x and extracts the rest with "expectation".

[wslh]

What size of organization are you talking about? There is a huge spectrum between startups and established corporations. Also, organizations of all sizes have planning errors.

[nrki]

Well, this thread was about setting a boundary of 9-5...would people go to a startup expecting that?

So...definitely for larger orgs, where "emergency availability" would be a big red flag, unless one explicitly opted into a (compensated) on call rota.

I guess one can make an exception for very early career, but again this was about setting a 9-5 boundary

[theendisney4]

Im always surprised these things are not calculated into the salary. For a startup, if you can get a very competent dev willing to take a salary cut it seems worth considering. They would bring sanity to the crap one writes when awake for 30 hours+

[stavros]

"Sure, I'm available. How often do emergencies happen, and do you have a retro for every one afterwards?"

[oblio]

Nah, not retro. How/when did you implement the actions observed during retros? What was the average delay in terms of number of sprints?

[radlad]

Some roles don't require this.

[wslh]

Sure, obviously I was referring to roles where it could happen and/or include help others in your team when an emergency situation arises.