Before hiring for a repetitive role, map the workflow. Most teams are one integration away from removing the job entirely.
The instinct when a process breaks under load is to add a person. Sometimes that is right. More often the process itself is the problem, and adding a person locks the broken shape in place permanently.
Map the workflow first: every step, every handover, every place someone copies data from one tool into another. Score each step by hours consumed and error risk. The top three usually account for most of the pain.
Automate those three, monitor them, and only then decide what a human should be doing. The role you hire for afterwards is usually a more interesting one.
Automation is not about removing people. It is about removing the parts of the work that never deserved a person in the first place.