Strong Engineers, On-Call Expectations Blur Work–Life Boundaries - Staff Software Engineer Jack Henry & Associates Employee Review

The primary challenge is not the technology or the people, but the lack of clear boundaries between working hours and personal time. The company’s incident management and on-call practices have created a culture where employee availability effectively extends beyond normal working hours. Engineers are expected to remain reachable at all times during rotations, and alerting tools are highly interruptive — often overriding normal device settings. In practice, this blurs boundaries between personal time and work, making true disconnect time difficult. On-call responsibility often feels less like a defined rotation and more like continuous background availability. Disruptions regularly occur during nights, weekends, or personal time, making consistent rest difficult to maintain. Over time, this results in fragmented sleep and accumulated fatigue rather than isolated periods of operational effort. There is also a recurring issue of responsibility without authority. Engineers are frequently paged for systems they did not design, lack historical context for, or do not have sufficient staffing or decision-making power to properly remediate. This leads to repeated incident response and reactive firefighting instead of sustainable reliability improvements. Most engineers understand that supporting production systems is part of the role. The difficulty comes from the absence of predictable recovery time and clearly protected off-hours space. The concern is less about occasional emergencies and more about ongoing interruption that accumulates over months and impacts long-term sustainability.