Let’s say it is 2 am Israel time on a Tuesday. You’ve got hundreds of thousands of teams across the globe that are working with your platform. Suddenly in a quiet database center in Virginia an incident occurs. As soon as this happens, a developer wakes up in his Tel Aviv apartment as an automated alarm notifies him that the server’s memory is filling too fast!
Bugs don’t consider the work hours of our development team. So an active developer must be appointed to be on-call — days, nights, weekends, and holidays. How can we approach this? Should we direct all problems to a dedicated DevOps team? Should we treat only the systemwide bugs or all bugs? Do we only allow the most experienced to handle the problem or also the new developers?
Eviathar Moussaffi, R&D team leader at monday.com shares our method of handling Dev-On-Call duty, the personal and professional challenges that arise with managing an array of developers in a fast-growing company and the opportunity of turning an intrusive duty into an ongoing team challenge.
