I started being on-call a few months ago. For us it works like this:<p>- 1 week in 4 Monday 00:00 to Sunday 23:59, with a fixed pay adjustment (same fixed amount added to our salary every month, not a % increment).<p>- If you get a call, you&#x27;re on the clock and get paid regular over-time rate. Theoretically this only applies if you get called and are doing something for more than 30 minutes though.<p>- I know most of the on-call managers personally so don&#x27;t mind picking up the phone for a quick opinion for free, if it&#x27;s at a reasonable time.<p>- Online within an hour once we&#x27;ve picked up the phone.<p>- Senior on-call manager gets woken up by Ops first and then will decide which parts of the system are affected. After going through known issues and work arounds will then work out which part of the system needs to be looked at and makes the call to the on-call developer that is appropriate (ie. which team).<p>- Duty is primarily to diagnose and provide knowledge to the on-call manager to make a decision so service can come back up again.<p>- Don&#x27;t do code fixes (J2EE on my team, mix of Java and C++ on others) - we have far too much to go wrong for hacking around like that, but may do config changes and some scripting. The line can get a bit blurred.<p>- In our team we should raise a ticket&#x2F;Jira for every time we get a call so that it&#x27;s visible to everyone what happened and see where our pain points are.<p>- During office hours, Production issues are distributed in the team in the same way as bugs, according to domain knowledge and individual capacity.<p>- We tend not to get called out except for when we do installation in to Production. We have a fairly heavy weight process for releases - which we are working on.<p>- I am at least 4 levels of communication away from any customers, including 1st and 2nd line teams.<p>Edit: formatting