1. Role overview
You keep systems running after they go live: as the business shifts, as the exceptions change, and as the people who ran the old process move on.
We operate what we build, and this is the role that makes that true. When something breaks in production it is ours until it is fixed.
You also find the next process, because the systems that earn it extend department by department.
2. Key Responsibilities
Own the health of the live systems across the accounts you run
Watch for drift: rules that have stopped matching how the business works
Handle exceptions with the client's team, and feed them back into the system
Keep the approvals and the audit trail correct as the organisation changes
Run the review the client's leadership sees, with what is true in it
Bring engineers in early when something needs rebuilding rather than patching
Find the next process worth building, and scope it with the client
3. Qualifications
You have run software in production for a business that depended on it.
Comfortable with logs, dashboards, and the question of what actually happened.
Experience of holding a client relationship together through a failure.
You can tell the difference between a bug, a changed rule and a bad design.
Organised enough to run several live systems without dropping one.
You escalate early, and in writing.
Experience in an operations or delivery role inside a services business.
Willing to travel to a client when the work needs it.
4. The work
Understand the client's process before choosing the technology.
Build systems for real operational work.
Work with the people who know the process.
Learn from the behaviour of systems in production.
Choose tools to fit the client's platforms and controls.
Document decisions so other engineers can follow the work.
Connect engineering decisions to the work the system must carry.
Keep the client's people involved as the system evolves.
