Key takeaways
- Start with the process, its users and the problem that needs solving.
- Assess process understanding alongside tool and integration skills.
- Agree ownership, maintenance and exception handling before deciding the employment model.
A finance approval flow or HR onboarding process may look simple until a record is missing, an approver is away or a system changes. Hiring someone to automate it requires more than selecting a familiar platform. The brief should explain how the process works and who will own it afterwards.
Describe the process that needs attention
Choose a defined starting point: an invoice received, an approved hiring request or a new employee record. Map the steps, decisions, handovers and exceptions through to completion.
Microsoft’s Power Automate documentation, for example, shows how approval workflows can be created and tested. The business still needs to decide who approves, what happens after rejection and how delayed or failed steps are handled.
Look for three kinds of evidence
- Process understanding: the candidate can explain the current workflow and why particular steps should change.
- Implementation: they can work with the chosen platform, data connections and access permissions.
- Operation: they can test exceptions, document the workflow and make failures visible to the right person.
In an interview, ask candidates to walk through something they built. What happened when data was incomplete? How did someone take over manually? Who maintained it after handover? These questions reveal whether a useful demonstration became a dependable process.
Choose the reporting line and support model
The business team can own the process while IT provides standards, access and technical support. Make those responsibilities explicit. Giving a role to Operations or Finance does not remove the need to coordinate systems and data controls.
A defined implementation with a clear end point may suit project support. A changing portfolio of workflows may justify a permanent role. In both cases, agree documentation, training and maintenance before work starts.
For candidates, show the full improvement
Explain the original problem, the steps you changed and how users adopted the result. Where you have measured an improvement, include the method and period as well as the number. Experience automating part of your own team’s work can provide a useful example of these decisions.
To scope an appointment, discuss the process and expected outcome with iTalent. For a time-limited requirement, explore secondment arrangements.
Sources
Updated: 13 October 2026.
