I've worked with someone in the past who insisted on everything in her job responsibilities be written down and spelled out exactly with no 'and other duties' listed. She used that for all sorts of fun work-avoidance tricks

- Walking out of the office in the middle of a server-down crisis because it wasn't her night to be on call and she'd already worked her 8 hours. The rest of the team worked til 4am.

- Noticing but doing absolutely nothing about a failed job one night when on call because said job ran on a server that was not in her list of monitored servers, Never mind that the job in question wrote some files out that a critical job on one of her monitored servers needed later in the night. Net result DBA team manager gets call from angry business user at 5am

- Refusing to assist with a project when she was the only team member who wasn't overloaded with work because it wasn't part of her duties.

There's no place in the DBA/Dev world for those kind of shenanigans. Declining work because it's way out of your area of expertise is one thing. Declining just because it's not listed in black and white on a piece of paper, sorry, no.