1. Role overview
The role connects the client relationship, the initial scope and the operation of the system after go-live.
The job is mostly translation: turning how a business actually works into a scope engineers can build, and turning engineering constraints into decisions a client can make.
You are the person who says what is not worth building, and who answers for it when something in production goes wrong.
2. Key Responsibilities
Run the scoping session, and keep it on the work rather than the technology
Turn the blueprint into a plan the client's own teams can follow
Hold the line on scope when one process turns out to be three
Bring security, audit and the system owners in before they have to be
Report honestly on what is running, what is not, and what it is costing
Stay on the account once the system is live, and find the next process
Bring the engineers into the room rather than speaking for them
3. Qualifications
You have delivered software or data work into a business that had to keep operating.
Comfortable discussing a system with engineers without needing to write the code.
You can turn a messy call into a written summary people act on.
Experience working directly with clients, including when the news is bad.
You can hold a plan together when the requirements change underneath it.
Experience of environments with real audit and approval requirements.
Comfortable saying no, and explaining why, when scope threatens the outcome.
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.
